This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
This use case was developed by Bruce Barton, in consultation with Bridget Almas, Steve Masover, and Travis Brown.
Improve the quality of holdings in the Perseus Collection by allowing a scholar to retrieve an object through the Bamboo CI HUB, edit the object, and then return the object to the Perseus Collection through the Bamboo CI HUB.
Scholars use common desktop tools to emend and annotate the object. They may also use morphological analysis tools to decorate the object with part-of-speech (POS) or other markup. Annotations may include assertions about the relationship between an object and other objects.
Perseus will accept and store curated versions of an object, annotations to a curated object and curation logs that describe what changes were made to the object along with who made the changes, when they were made, and so on.
The Perseus Collection repository does not lock or check out an object to the scholar when the object is retrieved from the Perseus Collection repository. Other scholars may have simultaneously retrieved, curated, and returned revisions of the same object to the Collection. We include the version of the object originally retrieved when we transmit the curated object to the Perseus Collection repository so that the repository can reconcile versions and manage change conflicts.
We assume that the work of preparing improved versions of texts for Perseus is a loosely collaborative affair. As scholars curate objects, they seek the advice of colleagues or advisors; they reach points in their work at which they solicit wider review and comment.
Each step in the following representative workflow marks an action initiated by a user
We will support version control in the local Fedora object store.
We also postulate here that the Git source code repository will be used as a means of marshaling objects to the desktop and facilitating collaborative work on the objects along the lines of Son of Suda Online (SoSOL). We retain CMIS/Fedora for compound/complex object modeling of the sort implied by the Bamboo Text Object. We speculate that version tagging in Git will provide a suitable point or hook for triggering updates to Fedora. In effect, we are distinguishing between a working store (Git) where components of objects, i.e. TEI XML documents or images, are organized and conveniently placed for desktop access, and a publication store (CMIS/Fedora), where object versions are modeled as Bamboo Text Objects and stably addressable.
Objects and annotations are stored and exposed for querying. As we noted in step 11 above, the local object store provides a means of storing stable targets for annotations and references. Policies around the duration of an object's storage in the local object and around the level of access to it by scholars or the public are driven by the local needs of the work groups using the instance of TextShop and the resources made available to them through their sponsoring institutions. Bamboo does not control these policies.
We are postulating that this is accomplished through the transmission of a content package.
Let's imagine that the repository receiving a content package, which contains an improved version of a text, enforces AuthN and manages AuthZ by user. Then, if the Perseus Collection were to join the Bamboo Trust Federation, it could be in principle possible to allow the Perseus Collection to verify directly the identity of the user on behalf of whom the content package is being deposited and enforce whatever local policies it may have vis-à-vis that user. Perhaps some users enjoy a higher level of trust as curators with the practical consequence that their submissions receive a different level of scrutiny by the Perseus curators.
In what senses is this a narrow use case? And how does being narrow in these senses reduce scope?
Because much of the subject specific work has been accomplished and because tool integration is very lightweight, we can focus on the infrastructure for scholarly data management. We don't have to undertake an expensive and time-consuming tool integration before scholars can be productive.
To apply the work we've done to other use cases, we add client tools where needed. These may be annotation, editing, or analytical tools. Having bridged the gap between the Bamboo Ecosystem and the desktop, it may be that little or no change is required to broaden the application of the Bamboo capabilities to another area of study beyond deploying suitable facilitating transformations to prepare data for consumption by the new client tools.
We are breaking new ground with content packaging for revised object transmission. It may well be that other repositories will find that using the packaging we develop for Perseus is the path of least resistance.