Differences between revisions 28 and 29
Revision 28 as of 2005-05-15 17:51:35
Size: 1895
Comment:
Revision 29 as of 2009-09-20 23:27:51
Size: 1909
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
 1. Extensible metadata per asset version in order to reflect things like workflow as discussed here:[[BR]][http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3c1072877417.4649.62.camel@gideon.rkunet.org%3e]  1. Extensible metadata per asset version in order to reflect things like workflow as discussed here:<<BR>>[[http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3c1072877417.4649.62.camel@gideon.rkunet.org%3e]]
Line 22: Line 22:
 1. Implement [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI interface for metadata harvesting].  1. Implement [[http://www.openarchives.org/OAI/openarchivesprotocol.html|OAI interface for metadata harvesting]].
Line 30: Line 30:
 * [http://marc.theaimsgroup.com/?t=107022316500003&r=1&w=2 "Converging the repository concept" - Thread in Cocoon-Dev]  * [[http://marc.theaimsgroup.com/?t=107022316500003&r=1&w=2|"Converging the repository concept" - Thread in Cocoon-Dev]]
Line 32: Line 32:
 * [http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3cbqnbaf$ah0$1@sea.gmane.org%3e "Repository Requirements" - Thread in Lenya-Dev]
 * [http://jcrep-jsr.day.com/content/playground/en.html JCR Playground]
 * [http://www.openarchives.org/ OAI - Open Archives Initiative]
 * [http://www.openarchives.org/OAI/openarchivesprotocol.html OAI protocol for metadata harvesting]
 * [[http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3cbqnbaf$ah0$1@sea.gmane.org%3e|"Repository Requirements" - Thread in Lenya-Dev]]
 * [[http://jcrep-jsr.day.com/content/playground/en.html|JCR Playground]]
 * [[http://www.openarchives.org/|OAI - Open Archives Initiative]]
 * [[http://www.openarchives.org/OAI/openarchivesprotocol.html|OAI protocol for metadata harvesting]]

1.) High priority

  1. open/save document
  2. Create collection of documents
  3. Open and save collections of assets
  4. Simple versioning
  5. Extensible metadata per asset version in order to reflect things like workflow as discussed here:
    http://mail-archives.apache.org/mod_mbox/lenya-dev/200312.mbox/%3c1072877417.4649.62.camel@gideon.rkunet.org%3e

  6. Simple metdata queries in order to fullfill 1.5.)
  7. Moving of single assets and collections in the repository (without breaking contracts). The moving of assets could be implemented via metadata see 1.5.). This requirement serves as basis to implement staging of assets.
  8. If access control is a concern of the Repository I propose it to be reflected in the rep. API, because otherwise Lenya has to deal with it. This is an important decision.

2.) MediumPriority

  1. Locking of assets. This is essential for concurrent actions on assets.
  2. Simple transactions

3.) LowPriority

  1. Complex metadata queries
  2. Observation - add listeners to specific events in the repository based on both the type of event and on the location in the repository.
  3. Implement OAI interface for metadata harvesting.

OpenIssues

RelatedLinks

ProposalRepositoryRequirements (last edited 2009-09-20 23:27:51 by localhost)