Any File to PREMIS

PREMIS in METS Project, Part 4 (Optional)

Overview

Deliverable: An application to describe any single file in PREMIS-compatible terms.

Input: A single file in any format. Supported input methods are those outlined for Validation.

Output: An XML file conforming to the PREMIS schema. (This could subsequently be run through the PREMIS-to-PREMIS-in-METS converter.)

Parameters

The following information can be supplied at run-time:
- file identifier type and file identifier value (required)
- intellectual entity identifier type and intellectual entity identifier value (optional)

Mapping

Will use DROID for format identification and JHOVE for validation and extraction of technical metadata.

PREMIS elements that will be supplied are:

objectIdentifier

objectIdentifierType: from parameter file identifier type

objectIdentifierValue: from parameter file identifier value

objectCategory: constant “file”

objectCharacteristics

compositionLevel: program will try to figure out from file type and other clues

messageDigestAlgorithm: “MD5” or “SHA-1” from JHOVE

messageDigest: calculated checksum from JHOVE

messageDigestOriginator: constant name of program

size: from JHOVE

formatName: from DROID (or JHOVE if the format is supported by JHOVE), with same resolution for multiples as DAITSS 2.0

formatVersion: from DROID (or JHOVE if the format is supported by JHOVE), with same resolution for multiples as DAITSS 2.0

formatRegistryName: constant “PRONOM”

formatRegistryKey: from DROID (or the corresponding PRONOM ID for format information returned by JHOVE), with same resolution for multiples as DAITSS 2.0

formatRegistryRole: constant “identification”

creatingApplicationName: from the applicable technical metadata returned from JHOVE (note: this is format dependent)

creatingApplicationVersion: from the applicable technical metadata returned from JHOVE (note: this is format dependent)

dateCreatedByApplication: from the applicable technical metadata returned from JHOVE (note: this is format dependent)
inhibitors: provide if applicable technical metadata is returned from

JHOVE (note: this is format dependent). For example, the PDF technical metadata will return encryption information if the PDF is password protected.

inhibitors provide if applicable technical metadata is returned from
JHOVE (note: this is format dependent). For example, the PDF technical metadata will return encryption information if the PDF is password protected.

inhibitorType: see inhibitors note

inhibitorTarget: “User Access:” + information from JHOVE

objectCharacteristicsExtension: provided if JHOVE returns detailed technical metadata

originalName: filename of file

signature: provided only if file is signed

linkingIntellectualEntityIdentifier

linkingIntellectualEntityIdentifierType: from parameter intellectual entity identifier type if provided

linkingIntellectualEntityIdentifierValue: from parameter intellectual entity identifer value if provided