Home

PiM

Step 1: Validation

Business Logic

Given a PiM document via an input method

1. Basic XML/Schema validation
   1. check for well-formed document, if errors then return specifics
   2. validate against XML Schema, if errors then return specifics
2. Best Practice / METS Profile validation
   1. validate against Schematron schemas
   2. return minimally a list of errors in output methods outlined below
   3. Optional/Experimental: suggestions for each error; profile/BP citations

Input Methods

1. given a HTTP URI of a PiM document, validate it.
2. upload a PiM document file via a html form
3. input a PiM document directly via a html form
4. Web Service based
   1. via POST
   2. via GET with a URI of a PiM document passes as a query parameter.
   3. investigate what w3 validator does.

Output Formats

1. html
2. plain text
3. xml
4. json

(all but html will be directly useful to the web service, indirectly ajax interfaces can use the rest)

Step 2: PREMIS → PiM

Given a valid PREMIS document convert it to a PiM document via the BP/METS Profile.

Input & Output

supported input methods are those outlined TODO above. Output will be PREMIS XML. For Browser viewing a PREMIS XML → HTML style sheet will be referenced.

Step 3: PiM → PREMIS

Given a valid PiM document destruct it according to its profile.

Profile 1: METS Buckets

Assemble all PREMIS elements from each respective METS administrative meta data sections into a valid standalone PREMIS document (using a PREMIS container). Representation assembly below

Profile 2: PREMIS Container

Extract the PREMIS container from the METS digiprovMD as a valid standalone PREMIS document (using a PREMIS container). Representation assembly below.

Representation Assembly

The BP recommends that METS structure maps be used for structural representations. Any preexisting PREMIS representations will be included in the compiled PREMIS document but an option will be provided to select any existing METS structure map for conversion to a PREMIS representation. HTML based interfaces will have a HTML form based option to choose the structure maps once uploaded; web service base interface will accept a query parameter denoting the ordinal position of the METS structure map in the document.

Input & Output

supported input methods are those outlined TODO above. Output will be PREMIS XML. For Browser viewing a PREMIS XML → HTML style sheet will be referenced.

Step 4: ??? File → PREMIS

Given a file (image for now) run it through JHOVE and then transform the JHOVE output to PREMIS. Priscilla

Step 5: PROFIT!