Difference between revisions of "ESciDoc Item Container Version History"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(71 intermediate revisions by 4 users not shown)
Line 1: Line 1:
<accesscontrol>Vlad</accesscontrol>
[[Category:LZA]]
 
''In progress''
= 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.''
==Premis Event Entity==
''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: <code>eventIdentifier</code>, <code>eventType</code>, and <code>eventDateTime</code>.''
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===
# [[#eventIdentifier|eventIdentifier]] (M, NR)
## [[#eventIdentifierType|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===
# 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===
* Complete schema in one file instead of separate files.
* Added elements:
** eventOutcomeDetailNote (O, NR)
** eventOutcomeDetailExtension (O, NR)
** linkingObjectRole (O, R)


=== eventType ===
See [[ESciDoc_Version_History_Event_Type]].


=Links=
=Links=
*[http://www.loc.gov/standards/premis/v2/ PREMIS V2], [http://www.loc.gov/standards/premis/v2/premis-v2-0.xsd XSD], [http://www.loc.gov/standards/premis/v2/premis-v2-namespace.html HTML], Data Dictionary [http://www.loc.gov/standards/premis/v2/premis-dd-2-0.pdf PDF]
*PREMIS all [http://www.loc.gov/standards/premis/schemas.html schemas]
*JIRA ticket [http://zim01.gwdg.de:8080/browse/AS-765 AS-765]
*[http://www.loc.gov/standards/premis/v2/ PREMIS v2.0]: Data Dictionary [http://www.loc.gov/standards/premis/v2/premis-dd-2-0.pdf PDF], [http://www.loc.gov/standards/premis/v2/premis-v2-namespace.html HTML]
*PREMIS v2.0 [http://www.loc.gov/standards/premis/v2/premis-dd-Hierarchical-Listing-2-0.html Hierarchical Listing of Semantic Units], see Event.
*PREMIS v1.0 => v2.0 [http://www.loc.gov/standards/premis/changes.html changes]
*JIRA tickets: http://zim01.gwdg.de:8080/browse/AS-765 and https://www.escidoc.org/jira/browse/INFR-606
*[http://www.escidoc.org/JSPWiki/en/ObjectManager Object Manager]
*[http://www.escidoc.org/JSPWiki/en/ObjectManager Object Manager]
**API Documentation [http://www.escidoc.org/documentation/Soap_api_doc_OM_Container.pdf Container Handler], [http://www.escidoc.org/documentation/Soap_api_doc_OM_Item.pdf Item Handler]
**API Documentation [http://www.escidoc.org/documentation/Soap_api_doc_OM_Container.pdf Container Handler], [http://www.escidoc.org/documentation/Soap_api_doc_OM_Item.pdf Item Handler]
Line 20: Line 83:
=Examples=
=Examples=
*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]
*item version-history, dev-coreservice, [http://dev-coreservice.mpdl.mpg.de:8080/ir/container/escidoc:29777/resources/version-history escidoc:29777]
** Not Found [[User:Frank|Frank]] 13:19, 8 March 2010 (UTC)
*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)
 
 
[[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]

  1. eventIdentifier (M, NR)
    1. eventIdentifierType (M, NR)
    2. eventIdentifierValue (M, NR)
  2. eventType (M, NR)
  3. eventDateTime (M, NR)
  4. eventDetail (O, NR)
  5. eventOutcomeInformation (O, R)
    1. eventOutcome (O, NR)
    2. eventOutcomeDetail (O, R)
  6. linkingAgentIdentifier (O, R)
    1. linkingAgentIdentifierType (M, NR)
    2. linkingAgentIdentifierValue (M, NR)
    3. linkingAgentRole (O, R)
    4. linkingAgentXmlID (O, A)
  7. linkingObjectIdentifier (O, R)
    1. linkingObjectIdentifierType (M, NR)
    2. linkingObjectIdentifierValue (M, NR)
    3. linkingObjectXmlID (O, A)
  8. xmlID (M, A)

V2.0[edit]

  1. eventIdentifier (M, NR)
    1. eventIdentifierType (M, NR)
    2. eventIdentifierValue (M, NR)
  2. eventType (M, NR)
  3. eventDateTime (M, NR)
  4. eventDetail (O, NR)
  5. eventOutcomeInformation (O, R)
    1. eventOutcome (O, NR)
    2. eventOutcomeDetail (O, R)
      1. eventOutcomeDetailNote (O, NR)
      2. eventOutcomeDetailExtension (O, NR)
  6. linkingAgentIdentifier (O, R)
    1. linkingAgentIdentifierType (M, NR)
    2. linkingAgentIdentifierValue (M, NR)
    3. linkingAgentRole (O, R)
    4. LinkAgentXmlID (O, A)
  7. linkingObjectIdentifier (O, R)
    1. linkingObjectIdentifierType (M, NR)
    2. linkingObjectIdentifierValue (M, NR)
    3. linkingObjectRole (O, R)
    4. LinkObjectXmlID (O, A)
  8. 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]

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)

Preservation Metadata: Implementation Strategies

Error Management and Project Management Software

Application Programming Interface

Coordinated Universal Time

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=ESciDoc_Item_Container_Version_History&oldid=58110"