Difference between revisions of "ESciDoc Item Container Version History"
m (→Links) |
m (→Concepts) |
||
| Line 2: | Line 2: | ||
= Concepts = | = Concepts = | ||
See http://www.escidoc.org/JSPWiki/en/ObjectManager | See Item, Container Specs&APIs [http://www.escidoc.org/JSPWiki/en/ObjectManager here] | ||
==Container Handler== | ==Container Handler== | ||
''Containers offer the concept of aggregation, i.e. they can contain other (simple and complex) objects. Each container includes a structural map, which manages references to all members of the aggregation. Containers are versionable. They can be associated with a persistent identifier. Containers have a built-in basic object lifecycle. The status of a Container within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.'' | ''Containers offer the concept of aggregation, i.e. they can contain other (simple and complex) objects. Each container includes a structural map, which manages references to all members of the aggregation. Containers are versionable. They can be associated with a persistent identifier. Containers have a built-in basic object lifecycle. The status of a Container within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.'' | ||
==Item Handler== | ==Item Handler== | ||
''Items are objects representing the actual content of the repository. An item is a simple or complex object like an article, a report or a translation. Items are versionable. They can be associated with a persistent identifier. Items have a built-in basic object lifecycle. The status of an Item within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.'' | ''Items are objects representing the actual content of the repository. An item is a simple or complex object like an article, a report or a translation. Items are versionable. They can be associated with a persistent identifier. Items have a built-in basic object lifecycle. The status of an Item within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.'' | ||
=Links= | =Links= | ||
Revision as of 15:31, 11 May 2009
This is a protected page.
Concepts[edit]
See Item, Container Specs&APIs here
Container Handler[edit]
Containers offer the concept of aggregation, i.e. they can contain other (simple and complex) objects. Each container includes a structural map, which manages references to all members of the aggregation. Containers are versionable. They can be associated with a persistent identifier. Containers have a built-in basic object lifecycle. The status of a Container within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.
Item Handler[edit]
Items are objects representing the actual content of the repository. An item is a simple or complex object like an article, a report or a translation. Items are versionable. They can be associated with a persistent identifier. Items have a built-in basic object lifecycle. The status of an Item within its object lifecycle influences which actions are applicable and which user privileges are to be evaluated.
Links[edit]
- PREMIS V2: Data Dictionary PDF, Schema XSD, HTML
- JIRA ticket AS-765
- Object Manager
- API Documentation Container Handler, Item Handler
- Schemas: Container, Item
- TOC Container
- Version History XSD
Examples[edit]
- container version-history, dev-coreservice, escidoc:29780
- item version-history, dev-coreservice, escidoc:29777