Difference between revisions of "ESciDoc Item Container Version History"
Jump to navigation
Jump to search
m |
m |
||
| Line 6: | Line 6: | ||
== Links == | == Links == | ||
*JIRA ticket [http://zim01.gwdg.de:8080/browse/AS-765 AS-765] | *JIRA ticket [http://zim01.gwdg.de:8080/browse/AS-765 AS-765] | ||
* API Documentation Container Handler [http://www.escidoc.org/documentation/Soap_api_doc_OM_Container.pdf here] | |||
Revision as of 13:40, 11 May 2009
This is a protected page.
Concept[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. See http://www.escidoc.org/JSPWiki/en/ObjectManager