Data Model Changes IEs and Environments The PREMIS

Data Model Changes IEs and Environments

The PREMIS Data Model Slide by S. Peyrard identifier Intellectual Entity rs ie ntif Rights rs it fie n ide n tifie rs ide Agent Object ide ntif ier s Event ide n r e i f ti s

Intellectual Entities § A set of content that is considered a single intellectual unit for purposes of management and description § For example, a particular book, map, photograph, or database. § An Intellectual Entity can include other Intellectual Entities; for example, a Web site can include a Web page; a Web page can include an image. § An Intellectual Entity may have one or more digital representations. PREMIS Data Model Changes Intellectual Entity Representation File Bitstream

Intellectual Entities Implementation § Capture descriptive metadata. § Assumed to be held in a container metadata schema. § PREMIS Objects link to it. § Can capture versioning information and metadata update events for intellectual. Entities, such as articles and issues. § Can represent a collection, FRBR work, FRBR expression, fonds, series, files (in the archival sense) PREMIS Data Model Changes

Represent a collection, FRBR work, FRBR expression, fonds, series, files … in order to § capture descriptive metadata § to have business requirements associated with them or to be referenced in business requirements (such as significant characteristics, risk definitions, guidelines for preservation actions, etc. ) § structural and derivative relationships § rights and preservation rights information § events and agents Ø This can only partially be accommodated by container metadata systems and their associated descriptive or administrative metadata. Ø Core preservation metadata (provenance aspects) PREMIS Data Model Changes

Treat Intellectual. Entity as Object Type § Data model more compact § Simplify the dictionary - drop linking. Intellectual. Identifier § Data dictionary more self-contained § Directly attach events, rights, indirectly attach agents to intellectual entities PREMIS Data Model Changes

Environments Rights rs ifie t n ide ers i f i nt e d i Object incl. Intellectual Entity ide ntif iers Agent s ifie Environment rs t r fi ie Event PREMIS Data Model Changes n e d i

Environment § Software § Hardware § A user behaviour study § A format § “Other representation information” § A document § A policy document § A manual § Documentation § A cheat sheet PREMIS Data Model Changes

High-level Requirements § A high-level data model § A standardized way of treating environments § Sharable and exchangeable § Modularised environment descriptions (aggregates) (as a network) § Re-usable environment description (across different Objects) § Re-usable environment description (across repositories and registries) PREMIS Data Model Changes

Requirements PREMIS Data Model Changes

Example: Object Entity q Main types of information v identifier v technical object characteristics v creation information v software and hardware environment v digital signatures v relationships to other objects v links to other types of entity PREMIS Data Model Changes

PREMIS – Environment Metadata 1. 5. 5 creating. Application 1. 5. 5. 1 creating. Application. Name 1. 5. 5. 2 creating. Application. Version 1. 5. 5. 3 date. Created. By. Application 1. 5. 5. 4 creating. Application. Extension PREMIS Data Model Changes

Gap Analysis q OAIS focus on Object: v Creating Applications are Environments v Life-cycle view treating Environments uniformly PREMIS Data Model Changes

Semantic Unit: Environment q What is needed to render or use an object v Operating system v Application software v Computing resources PREMIS Data Model Changes

PREMIS – Environment Metadata 1. 8. 5 software 1. 8 environment 1. 8. 1 environment. Characteristic 1. 8. 5. 1 sw. Name 1. 8. 2 environment. Purpose 1. 8. 3 environment. Note 1. 8. 4 dependency 1. 8. 4. 1 dependency. Name 1. 8. 4. 2 dependency. Identifier 1. 8. 4. 2. 1 dependency. Identifier. Type 1. 8. 4. 2. 2 dependency. Identifier. Value 1. 8. 5. 2 sw. Version 1. 8. 5. 3 sw. Type 1. 8. 5. 4 sw. Other. Information 1. 8. 5. 5 sw. Dependency 1. 8. 6 hardware 1. 8. 6. 1 hw. Name 1. 8. 6. 2 hw. Type 1. 8. 6. 3 hw. Other. Information 1. 8. 7 environment. Extension PREMIS Data Model Changes

Environment Example: PDF File environment. Characteristic = known to software/sw. Name = work Adobe Acrobat Reader environment. Purpose = render software/sw. Version = 6. 1 software/sw. Type = renderer software/sw. Dependency = Windows NT hardware/hw. Name = Intel Pentium II hardware/hw. Type = processor dependency/dependency. Name= Mathematica 5. 2 True Type math fonts software/sw. Name = Windows NT software/sw. Version = 5. 0 software/sw. Type = operating. System PREMIS Data Model Changes

Gap Analysis I - Subordinate to Object q Environments can be too complex to handle in an Object repository. q Solution too redundant (verbose, cumbersome to manage evolution) Rarely specific to a single Object. q Unable to describe stand-alone Environments independent of Objects Repositories and registries need to speak the same language q Unable to decouple Object or Agent descriptions from environment related information (to version and maintain environments separately) q Cause: Environment Subordinate to Object Ø Solution: Environment as first class entity PREMIS Data Model Changes

Gap Analysis II § Unable to express all but the first type of relationship 3 rs e i f ti 1 n ide Object Rights ide nti i identifiers Environment 2 4 7 rs fie i t den ide nti 6 fie r s 5 Agent fier rs s Event PREMIS Data Model Changes ide fie i t n

Relationships 1. 2. 3. 4. 5. 6. 7. Object to environment - specify computational context environment to Object - documentation, specifications, surrogates environment to environment -inclusion, dependency, derivation, other environment is an Object – preserved software source code environment to Agent - role of an Agent environment to Event - environment specific Events (provenance) environment to Rights. Statement - software license, policy “Object”: here a traditional repository Object PREMIS Data Model Changes

Gap Analysis III § Refer to external registries: only for file formats § Versions: only for software § Software dependencies: maximally 2 levels § Cannot document the nature of dependencies § Software or hardware used as an Agent cannot be identified PREMIS Data Model Changes

Requirements Describe tangible and intangible items Capture designation information (name and version) Capture the function of an environment (type and use) Capture relationships with a variety of relationship types: whole/part, replacement, dependency § Representations and Files -> Representations and Files § Environment -> supporting documentation § Object -> environment description in an external registry § § § Not: business policies, preservation plans, business or research process descriptions and workflows referencing entities PREMIS Data Model Changes

Solution t n e id s fier Rights i ide nti fie rs Object Agent Environ ment ide nti fier rs s Event fie i t n ide PREMIS Data Model Changes

t n e id s fier Rights i ide nti fie rs Agent Environment Object ide nti fier rs s Event fie i t n ide PREMIS Data Model Changes

Intellectual Entity Software operating system Ubuntu 32 -bit, version 12. 10 structural relationship represents The ISO image is described as a file with technical characteristics. I also want to record that this file captures Ubuntu version 12. 10 File size: 726970368 format name: application/xiso 9660 -image PREMIS Data Model Changes

Example Description of the Ubuntu Version 12. 10 operating system and reference to its installation manual object. Identifier. Type: ARK object. Identifier. Value: ark: /9999/b 1 object. Category: intellectual entity object. Function object. Type: software object. Sub. Type: operating system object. Designation object. Name: Ubuntu object. Version: 12. 10 object. Other. Information: 32 -bit version object. Note: maintenance deadline: 2014 -04 object. Designation object. Name: Ubuntu object. Version: Quantal Quetzal relationship. Type: documentation relationship. Sub. Type: is documented in relationship. Purpose: install relationship. Characteristic: known to work related. Object. Identification related. Object. Identifier. Type: URL related. Object. Identifier. Value: https: //wiki. ubuntu. com/Quantal. Quetzal/ Technical. Overview Object: <Documentation>

Example I am preserving the Ubuntu operating system as an ISO image. I can identify two levels of description (the File and the abstract Intellectual Entity) and link them with a PREMIS relationship. 05 Sept 2013 26 object. Identifier. Type: ARK object. Identifier. Value: ark: /9999/b 1 object. Category: intellectual entity object. Function object. Type: software object. Sub. Type: operating system Ubuntu 32 -bit, version 12. 10 relationship. Type: structural, relationship. Sub. Type: represents object. Identifier. Type: ARK object. Identifier. Value: ark: /9999/c 1 object. Category: file object. Characteristics composition. Level: 0 size: 726970368 format. Designation format name: application/x-iso 9660 -image PREMIS Data Model Changes

Example object. Category: intellectual entity object. Function object. Type: software object. Sub. Type: operating system object. Designation object. Name: Windows XP Professional object. Version: Service Pack 3 object. Registry. Name: PRONOM object. Registry. Key: x-sfw/8 object. Registry. Role: generalization object. Registry. Name: IIPC Database object. Registry. Key: http: //gator 1355. hostgator. com/~iipc/pwg/software. php? id=1006 object. Registry. Role: identity object. Registry. Name: UDFR object. Registry. Key: http: //udfr. org/udfr/u 1 r 2415 object. Registry. Role: generalization This ISO image contains Windows XP Pro, SP 3. I have 3 descriptions of Windows XP outside the registry. 3 different registry entries Windows XP Professional

I am preserving a Word file, thus want to link to available information in external registries without duplicating it. I use a simple link to an external entry relationship. Type: dependency relationship. Sub. Type: requires relationship. Purpose: render relationship. Characteristic: recommended related. Object. Identification related. Object. Identifier. Type: PUID related. Object. Identifier. Value: x-sfw/1 object. Category: file size: 12348 format. Designation format. Name: application/msword format. Version: 97 -2003 x-sfw/1 Description of Word 97 -2003 in PRONOM PREMIS Data Model Changes

object. Category: intellectual entity environment. Function. Type : software environment. Function. Level: 1 environment. Function. Type : software application environment. Function. Level: 2 Adobe Dreamweaver CS 4 object. Category: intellectual entity environment. Function. Type : software environment. Function. Level: 1 environment. Function. Type : software application environment. Function. Level: 2 Name: Blue. Griffon 1. 6 relationship. Type: dependency sub. Type: requires relationship. Purpose: edit relationship. Characteristic: known to work relationship. Type: dependency sub. Type: requires relationship. Purpose: create object. Category: file size: 12348 format. Designation format. Name: text/html relationship. Type: dependency sub. Type: requires relationship. Purpose: render relationship. Characteristic: known to work Firefox 10. 0 can be used as a rendering application for a lot of different files The same Environment (Blue. Griffon 1. 6) can be used to create AND render objects object. Category: intellectual entity environment. Function. Type: software environment. Function. Level: 1 environment. Function. Type : software application environment. Function. Level: 2 Firefox 10. 0 relationship. Type: dependency sub. Type: requires relationship. Purpose: render relationship. Characteristic: known to wor relationship. Type: dependency sub. Type: requires relationship. Purpose: create object. Category: file size: 12348 format. Designation format. Name: text/html

Questions? PREMIS Data Model Changes