This wiki space contains archival documentation of Project Bamboo, April 2008 - March 2013.
Here's a generic scenario a researcher may go through. Each of the stages in this process may occur inside or outside the Bamboo Services Platform. The implications for CI are very different depending on where the activity takes place. [P. Gorman, 2010-11-09]
If the Bamboo platform incorporates resource discovery, an interoperable external collection must provide support either for metasearching (e.g., by supporting SRU/SRW) or metadata harvesting (e.g. OAI-PMH). It is assumed, however, that some amount of discovery will take place outside the Bamboo platform.
A citation must include a resolvable, unique identifier. If an object has multiple disseminations, a scholar should have the opportunity to select a specific dissemination (the one most suitable for the purpose at hand), or retrieve links to all available disseminations. It is not immediately clear how those choices might labeled or encoded in the metadata.
If Bamboo services need to operate on a locally-stored copy of an object from an external collection, the service platform will need to ingest the object, preserving links back to the source object in an audit trail. Again, provision should be made for ingesting one of a number of possible disseminations of an object (e.g. plain text/PDF/TEI; raw scan/cropped image). Upon ingest, the Bamboo platform will create a new "Bamboo Content Object", including descriptive and possibly technical metadata, a locally-scoped identifier, and provenance metadata (e.g., Bamboo Person, dates, unique ID of source object). In the simplest case, the scholar will simply upload one or more datastreams from a local hard drive, in which case he or she may have to supply some basic descriptive metadata.
In either case, a link back to the source object should be maintained, but the specific relationship will differ depending on the nature of the new object. While the new object may be created on the Bamboo platform, it should be possible to push the object into a longer-term repository external to Bamboo. The new objects will become new "Bamboo Content Objects", with their own unique locally-scoped identifier, descriptive and technical metadata, etc.