Difference between revisions of "ESciDoc Item Container Version History"
Josef Nassl (talk | contribs) |
m (→Examples) |
||
(6 intermediate revisions by one other user not shown) | |||
Line 1: | Line 1: | ||
[[Category:LZA]] | |||
''In progress'' | ''In progress'' | ||
= Concepts = | = Concepts = | ||
Line 83: | Line 84: | ||
*container version-history, dev-coreservice, [http://dev-coreservice.mpdl.mpg.de:8080/ir/container/escidoc:29780/resources/version-history escidoc:29780] | *container version-history, dev-coreservice, [http://dev-coreservice.mpdl.mpg.de:8080/ir/container/escidoc:29780/resources/version-history escidoc:29780] | ||
** Not Found [[User:Frank|Frank]] 13:19, 8 March 2010 (UTC) | ** Not Found [[User:Frank|Frank]] 13:19, 8 March 2010 (UTC) | ||
*item version-history, dev-coreservice, [http:// | *item version-history, dev-coreservice, [http://coreservice.mpdl.mpg.de/ir/item/escidoc:66603/resources/version-history escidoc:66603] | ||
** Not Found (neither as container nor as item) [[User:Frank|Frank]] 13:19, 8 March 2010 (UTC) | ** Not Found (neither as container nor as item) [[User:Frank|Frank]] 13:19, 8 March 2010 (UTC) | ||
[[Category:ESciDoc]] | [[Category:ESciDoc|Item Container Version History]] |
Latest revision as of 09:39, 7 January 2011
In progress
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.
Premis Event Entity[edit]
The Event entity aggregates information about an action that involves one or more Object entities. Metadata about an Event would normally be recorded and stored separately from the digital object.
Whether or not a preservation repository records an Event depends upon the importance of the event. Actions that modify objects should always be recorded. Other actions such as copying an object for backup purposes may be recorded in system logs or an audit trail but not necessarily in an Event entity. Mandatory semantic units are: eventIdentifier
, eventType
, and eventDateTime
.
This is a hierarchical listing of the semantic units included in the Data Dictionary. The information in parentheses following each semantic unit indicates whether the element is Mandatory (M) or Optional (O), followed by whether it is Repeatable (R), Not repeatable (NR) or Attribute (A).
V1.0[edit]
- eventIdentifier (M, NR)
- eventIdentifierType (M, NR)
- eventIdentifierValue (M, NR)
- eventType (M, NR)
- eventDateTime (M, NR)
- eventDetail (O, NR)
- eventOutcomeInformation (O, R)
- eventOutcome (O, NR)
- eventOutcomeDetail (O, R)
- linkingAgentIdentifier (O, R)
- linkingAgentIdentifierType (M, NR)
- linkingAgentIdentifierValue (M, NR)
- linkingAgentRole (O, R)
- linkingAgentXmlID (O, A)
- linkingObjectIdentifier (O, R)
- linkingObjectIdentifierType (M, NR)
- linkingObjectIdentifierValue (M, NR)
- linkingObjectXmlID (O, A)
- xmlID (M, A)
V2.0[edit]
- eventIdentifier (M, NR)
- eventIdentifierType (M, NR)
- eventIdentifierValue (M, NR)
- eventType (M, NR)
- eventDateTime (M, NR)
- eventDetail (O, NR)
- eventOutcomeInformation (O, R)
- eventOutcome (O, NR)
- eventOutcomeDetail (O, R)
- eventOutcomeDetailNote (O, NR)
- eventOutcomeDetailExtension (O, NR)
- linkingAgentIdentifier (O, R)
- linkingAgentIdentifierType (M, NR)
- linkingAgentIdentifierValue (M, NR)
- linkingAgentRole (O, R)
- LinkAgentXmlID (O, A)
- linkingObjectIdentifier (O, R)
- linkingObjectIdentifierType (M, NR)
- linkingObjectIdentifierValue (M, NR)
- linkingObjectRole (O, R)
- LinkObjectXmlID (O, A)
- xmlID (M, A)
Changes v1.0=>v2.0[edit]
- Complete schema in one file instead of separate files.
- Added elements:
- eventOutcomeDetailNote (O, NR)
- eventOutcomeDetailExtension (O, NR)
- linkingObjectRole (O, R)
eventType[edit]
See ESciDoc_Version_History_Event_Type.
Links[edit]
- PREMIS all schemas
- PREMIS v2.0: Data Dictionary PDF, HTML
- PREMIS v2.0 Hierarchical Listing of Semantic Units, see Event.
- PREMIS v1.0 => v2.0 changes
- JIRA tickets: http://zim01.gwdg.de:8080/browse/AS-765 and https://www.escidoc.org/jira/browse/INFR-606
- 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
- Not Found Frank 13:19, 8 March 2010 (UTC)
- item version-history, dev-coreservice, escidoc:66603
- Not Found (neither as container nor as item) Frank 13:19, 8 March 2010 (UTC)