ESciDoc Version History Event Type

Premis Event Type in eSciDoc Version History
The eSciDoc infrastructure maintains a version history for every versioned resource. The version history consists of version elements containing premis:event elements for every operation pertaining to the respective version.

premis:eventType is a mandatory element inside a premis:event. The value of premis:eventType should follow a controlled vocabular. For now, the following event type values are used in eSciDoc infrastructure.


 * create
 * update
 * submitted
 * in-revision
 * released
 * assignObjectPid
 * assignVersionPid

On eSciDoc Committer Meeting at 23.2.2010 it was agreed to create PURLs to specify event types.

The following event types will be defined (for Item, Container, Context, Content Model, Organizational Unit):

http://purl.org/escidoc/infrastructure/event-type/add-members http://purl.org/escidoc/infrastructure/event-type/add-tocs http://purl.org/escidoc/infrastructure/event-type/assign-content-pid http://purl.org/escidoc/infrastructure/event-type/assign-object-pid http://purl.org/escidoc/infrastructure/event-type/assign-version-pid http://purl.org/escidoc/infrastructure/event-type/close http://purl.org/escidoc/infrastructure/event-type/create http://purl.org/escidoc/infrastructure/event-type/create-component http://purl.org/escidoc/infrastructure/event-type/create-container (create container and add as member to a container) http://purl.org/escidoc/infrastructure/event-type/create-item (create item and add as member to a container) http://purl.org/escidoc/infrastructure/event-type/create-md-record http://purl.org/escidoc/infrastructure/event-type/delete (!?) http://purl.org/escidoc/infrastructure/event-type/ingest http://purl.org/escidoc/infrastructure/event-type/lock http://purl.org/escidoc/infrastructure/event-type/move-to-context http://purl.org/escidoc/infrastructure/event-type/open http://purl.org/escidoc/infrastructure/event-type/release http://purl.org/escidoc/infrastructure/event-type/remove-members http://purl.org/escidoc/infrastructure/event-type/revise http://purl.org/escidoc/infrastructure/event-type/submit http://purl.org/escidoc/infrastructure/event-type/unlock http://purl.org/escidoc/infrastructure/event-type/update http://purl.org/escidoc/infrastructure/event-type/update-admin-descriptor http://purl.org/escidoc/infrastructure/event-type/update-component http://purl.org/escidoc/infrastructure/event-type/update-md-record http://purl.org/escidoc/infrastructure/event-type/update-parents http://purl.org/escidoc/infrastructure/event-type/withdraw

Premis Specification of premis:eventType
The Premis Data Dictionary (in http://www.loc.gov/standards/premis/v2/premis-2-0.pdf) says about the eventType element:

Definition
A categorization of the nature of the event.

Rationale
Categorizing events will aid the preservation repository in machine processing of event information, particularly in reporting.

Data constraint
Value should be taken from a controlled vocabulary.

Examples
E77 [a code used within a repository for a particular event type] Ingest

Repeatability
Not repeatable

Obligation
Mandatory

Usage notes
Each repository should define its own controlled vocabulary of eventType values. A suggested starter list for consideration (see also the Glossary for more detailed definitions):

capture = the process whereby a repository actively obtains an object

compression = the process of coding data to save storage space or transmission time

creation = the act of creating a new object

deaccession = the process of removing an object from the inventory of a repository

decompression = the process of reversing the effects of compression

decryption = the process of converting encrypted data to plaintext

deletion = the process of removing an object from repository storage

digital signature validation = the process of determining that a decrypted digital signature matches an expected value

dissemination = the process of retrieving an object from repository storage and making it available to users

fixity check = the process of verifying that an object has not been changed in a given period

ingestion = the process of adding objects to a preservation repository message digest

calculation = the process by which a message digest (“hash”) is created

migration = a transformation of an object creating a version in a more contemporary format