1. PREMIS Rathachai Chawuthai rathachai.chawuthai@live.com Information Management CSIM / AIT

2. Preservation Metadata PREMIS Overview Data Dictionary Conventions PREMIS Data Model The Data Dictionary PREMIS In use

4. Metadata that supports activities intended to ensure the long-term usability of a digital resource Example – Store securely……… Nobody change ……… It needs metadata about Checksum – Can be read……… DVD, CD, Floppy Disk?, 5” Disk?, … – Can render……… Word 6?, Word 2003, Word 2010 …. ……… It needs metadata about app & version – Look originally……… Support changing source, how to render ……… Support authenticity by digital provenance What?

6. PREservation Metadata: Implementation Strategies Sponsor by Library of Congress (LOC) People usually refer to “PREMIS” as “Data Dictionary” Represent in XML format What?

7. Set of Semantic Unit Metadata for digital object – Can read from media – Can render – Store securely – Keep track of changing format Metadata Scope – Format-spec e.g. audio, video, image, … – Implementation-specHow to access it (by app) – Descriptive metadataData properties; like, MARC, DC – Detailed info(For media or hardware) – Agents infoe.g. people, org, or software – Right infoe.g. license, permission PREMIS Data Dictionary

8. Small core at the heart of preservation metadata

9. Support managing repository system – Long-term preservation – Repository migration (to another) Scope – Repository Design – Repository Evaluation – Exchange of archived info pkg among repositories Software view – Use PREMIS as a guideline for what info should be recorded Be used

10. Support Data preservation by having – Inhibitors Password, encryption, … in order to access digital objects – Digital Provenance Application, version, environment, … in order to render digital objects Record change of object format e.g..DOC .PDF – Significant Properties (If important) Object’s characteristics e.g. font, formatting, color, …., etc Look and feel – Right Copyright status, License term Using PRMIS if you have to

12. Metadata – Likes; database schema Semantic Unit – Properties of entities (More structure than metadata) Semantic Unit

13. Software = “Windows|XP|OperationSystem” Software - swName = “Windows” - swVersion = “XP” - swType = “OperatingSystem” Container

14. New in PREMIS 2.0 Contains externally defined semantic units Allows to extend PREMIS with semantic units which are more granular, non-core or out of scope of the PREMIS data dictionary Data in the container may replace, refine or be additional to the appropriate PREMIS semantic unit One schema per extension; if more schemas are needed, the extension element needs to be repeated Extension Container (General)

16. Entities

17. May called “Bibliographic Entities” A set of content that is considered a single intellectual unit for purposes of management and description – E.g. book, map, photograph, or database Intellectual Entities

18. To be stored and managed in the preservation repository E.g. – Intellectual Entity : “Thailand Map” – Object Entity: Image file 3 Kinds of object – File A computer file, likes a PDF or JPEG – Representation Set of files that work together E.g. web page including, html, image, css, javascript – Bitstream A part of file E.g. a frame image in video file Object Entities

19. Data Dictionary includes: – a unique identifier for the object (type and value), – fixity information such as a checksum (message digest) and the algorithm used to derive it, – the size of the object, – the format of the object, which can be specified directly or by linking to a format registry, – the original name of the object, – information about its creation, – information about inhibitors, – information about its significant properties, – information about its environment OS  MacOS, Browser  Safari – where and on what medium it is stored, – digital signature information, – relationships with other objects and other types of entities. Object Entities

20. Action that effect object in the repository – E.g. changing an object Data Dictionary includes: – a unique identifier for the event (type and value), – the type of event (creation, ingestion, migration, etc.), – the date and time the event occurred, – a detailed description of the event, – a coded outcome of the event, (Result of event; success | fail | …) – a more detailed description of the outcome, – agents involved in the event and their roles, – objects involved in the event and their roles. Events

21. Actor, e.g. person, organization, or software Metadata standard, e.g. FOAF, vCARD, eduPerson, … Data Dictionary includes: – a unique identifier for the agent (type and value), – the agent's name, – designation of the type of agent (person, organization, software). Note: Agent can has many roles – Up to Event entities or Rights entities Agents

22. Information about Rights and Permissions that are directly relevant to preserving objects in repository Assertion of Rights – To provide actionable info to preservation repository system Data Dictionary includes: – a unique identifier for the rights statement (type and value), – whether the basis for claiming the right is copyright, license or statute, – more detailed information about the copyright status, license terms, or statute, as applicable, – the action(s) that the rights statement allows, – any restrictions on the action(s), – the term of grant, or time period in which the statement applies, – the object(s) to which the statement applies, – agents involved in the rights statement and their roles. Rights

24. Example

27. Correct type – Integer – Datetime Correct constraint – R: Repeatable – NR: Non-Repeatable Support all mandatory value – if export to another repository – M : Mandatory – O: Optional Requirement