This section will be used to propose demonstrators and to continue the process coming out of Evanston towards our goal of launching at least 3 demonstrators by the end of 2011. Please add your comments below, and feel free to generate new categories. Thank you.
- Demonstrators will be developed to tell a clear story of scholarly value
- Demonstrators will be scheduled to follow the technical development time frame rather than direct or influence the technical development time frame
- Within this parameter we will try to release 3 demonstrators before the end of 2011
- As much as possible, demonstrators will illustrate a full user experience - "end to end"
- Communications efforts will proactively inform our audiences that a demonstrator has been released
Demonstrator Development Process
- The Communications team will confer with the development teams to define and refine the potential demonstrator ideas listed below
- Refined demonstrator ideas will be presented to the PEG for review, feedback and go/no go decision
- Communications team will develop demonstrator timeline proposal to be confirmed with development team
- Communications lead (with communications team support) will work with development team to craft stories and obtain screengrabs and other relevant content
Demonstrator Ideas for Consideration
Please see Quinn's page on demonstrators.
Note that the following ideas are not mutually exclusive and can be "mixed and matched" in several ways. Communications and technical development teams will work together to identify the most powerful and feasible combinations.
- Currently the WS is working "end to end", maybe add Morphadorner
- Morphadorner exposed as RESTful webservices on the BSP
- Run Morphadorner on the text
- Wrapped Philologic calls talking to the platform could become a "pipeline demonstrator" with Work Spaces also
- Connect parts of the project together that are currently separated, e.g. Philologic and Perseus
- Zotero into Hathi and bringing materials back - showcases the CI adapter
- Perhaps run Zotero against more than one collection - good for our story to the libraries
- It would be great to get all the demonstrators to work against more than one collection
- Woodchipper integrated with input streams for WoodChipper's data loading routines
- Demonstrate the ability to create (e.g., using stand-alone tools or tools wrapped in Meandre/SEASR) and store (within Bamboo) document derivatives (e.g., morph-adorned text or entities extracted from a text) for a set of texts (e.g., TCP-ECCO). Implement exemplar services that leverage such derivatives to dynamically create graphs and other visualizations for subsets of collection. From within Work Space allow users to bring derivatives into user's work space, call on services that use derivatives, make their own visualizations, .... Like the texts themselves these derivatives would be subject to curation including correction, improvement, versioning, ....
- Parallel demonstration involving building block derivatives resulting from analysis of collections in aggregate, e.g., topic modeling (supporting tag clouds and other forms of visualization), concept mapping, etc.
- Demonstrate login of one (logical) Bamboo Person via institutional and social media IdPs, where the Bamboo Person's access to a protected resource is permitted irrespective of login method. This will demonstrate progress in implementing the Bamboo Ecosystem IAM infrastructure. Based on current work plan delivery goals, this demonstration should be achievable by October via a fairly primitive, PoC screencast. Demonstration of 'self-service' assertion and proof of linkage between multiple accounts will also be of interest, but will not be ready to show until early 2012.
- Demonstrate using the Workspace Book interface to view a latin, greek or arabic text. Extract a section of text in TEI and submit it to the Bamboo Morphology Service for analysis.
- Demonstrate using one or more of the Workspace Book interface, a Philologic service, or the CI Hub to find a text citation. Retrieve the TEI XML for the citation and submit it to the Bamboo Syntactic Annotation Service to retrieve templates for annotating syntax (via dependency trees) of the sentences in the citation. Submit the annotation templates to the Alpheios Treebank Editor for annotating.
- Demonstrate extracting a line from Homer or Aeschylus from Perseus (either via the Workspaces Book interface, Perseus CI Connector, or Philologic), sending the TEI XML to the Morphology Service to get an automated parse of the morphology, requesting the syntactic annotations of the same line from the Annotation Service and using the Annotate Service results to disambiguate the parse alternatives produced by the Morphology Service. Use the Cache Service to store intermediate results.
- Demonstrate (a) rolling out a platform-mediated service in a commonly-used (non-Work Space) environment, and (b) working with affiliates, by creating a very basic Drupal module that can display Philologic results (connection proxied through the platform). Data set for demonstrator will be Laura Mandell's Poetess Archive.
- Demonstrate a curatorial function, for example the ability in WS to display page image from volume side-by-side with page transcript (both retrieved via CMIS), then highlight gap or unclear elements on page, then deposit an annotation of proposed correction properly attributed to scholar reading and accessible to another scholar (representing 'editor').