# Presentation: 262544

## Extending the Implementation of  PREMIS to Geospatial Resources in the Stanford Digital Repository: An Exploration 

- Extending the Implementation of  PREMIS to Geospatial Resources in the Stanford Digital Repository: An Exploration
- By Nancy J. Hoebelheinrich
- Metadata Coordinator
- Digital Library Systems & Services
- PREMIS Tutorial San Diego, CA 11 Feb 2008

- Stanford Digital Repository

- Implementing the PREMIS Data Dictionary at Stanford

## To Be Discussed

- Context for SDR (Stanford Digital Repository)
- What PREMIS data elements are being used currently
- How & why
- PREMIS & Geospatial Resources  - a fit?

- Implementing the PREMIS Data Dictionary at Stanford

## SDR Context

- Bit Level Preservation environment
- Designed to facilitate an automated production environment for digitization & receipt of digital materials
- Use of a “target manifest” (TM)
- = core metadata, structure & file inventory  expressed as METS document
- = SIP w/o content files

- Implementing the PREMIS Data Dictionary at Stanford

## Scenario 1:  David Rumsey Historical Maps Collection

- Comprised of historical maps digitized as Single, Still image TIFFs
- METS Records for
- Rumsey Deposit Agreement
- Rumsey “Collection Level” & Auxiliary Files
- Each Item

- Implementing the PREMIS Data Dictionary at Stanford

## METS Documents for Rumsey Collection 

- Individual Map

- Collection Level / Auxiliary Files

- Deposit Agreement

- Relationships among METS Docs

- Implementing the PREMIS Data Dictionary at Stanford

## PREMIS Records contained w/in METS Documents

- PREMIS _*OBJECT*_
- PREMIS _*RIGHTS*_
- PREMIS _*EVENTS*_

- Aspects of digital provenance
- Succinct link to full rights statement
- Important lifecycle events

- Implementing the PREMIS Data Dictionary at Stanford

**Notes:**
Digital Provenance: Documentation of processes in a Digital Object’s life cycle. Digital
Provenance typically describes Agents responsible for the custody and stewardship of Digital
Objects, key Events that occur over the course of the Digital Object’s life cycle, and other
information associated with the Digital Object’s creation, management, and preservation.

## Use of PREMIS Object Data Elements

- Used in each METS Document referencing files
- Item, Agreement, “Collection Level” & Auxiliary Files
- Located in the METS <amdSec><techMD> section
- Automatic insertion by Ingest code to retain important provenance info for each file:
- Original file name from data provider
- Original checksum
- Original file size
- Some information redundant, but prefer to retain in case METS sections need to be pulled out separately for action
- _[Rumsey](file:///24687.xml)__[ Item TM](file:///24687.xml)_    _[Rumsey](file:///PREMIS_object2008_02.rtf)__[ ](file:///PREMIS_object2008_02.rtf)__[PREMIS_Object](file:///PREMIS_object2008_02.rtf)__[ excerpt](file:///PREMIS_object2008_02.rtf)_

- Implementing the PREMIS Data Dictionary at Stanford

## Use of PREMIS Rights data elements 

- Rumsey Deposit Agreement TM
- Represents the ingested *draft *Agreement with its own TM
- Placeholder for:
- XML or other REL instance of full agreement ***or ***
- Use of METSRights once final agreement template is vetted & agreed upon by University Counsel

- Implementing the PREMIS Data Dictionary at Stanford

## Use of PREMIS Rights data elements 

***How****?*
-  <amdSec><rightsMD>
- <mdWrap><xmlData>
- _[Agreement TM](file:///RumseyAgreementDraftV07_4PREMIS_tutorial.xml)_
- _[Rumsey](file:///Rumsey_PREMIS_Rightsexcerpt.rtf)__[ Rights Excerpt](file:///Rumsey_PREMIS_Rightsexcerpt.rtf)_

***Why****?*
- Succinct summary of key information for quick access from METS Document itself
- Locator for more complete expression of terms, conditions;

- Implementing the PREMIS Data Dictionary at Stanford

## Use of PREMIS Event Data Elements

- Event 1:
- Transform of descriptive MD from MS Access db => XML => MODS
- Inserted into mets <amdSec><digiprovMD>
- _[Rumsey](file:///SimpleFileEx_TM_final.xml)__[ ](file:///SimpleFileEx_TM_final.xml)__[SimpleFile](file:///SimpleFileEx_TM_final.xml)__[ TM](file:///SimpleFileEx_TM_final.xml)_
- _[Rumsey](file:///Rumsey_PREMIS_EventExcerpt.rtf)__[ Event Excerpt](file:///Rumsey_PREMIS_EventExcerpt.rtf)_

- Why this event?
- In case of questions from outside data provider
- Retain singular scripts & transform mechanisms
- Test practicability of recording such events in production environment

- Implementing the PREMIS Data Dictionary at Stanford

## Scenario 2:  Geospatial Files & PREMIS – is it a fit?

- Shapefiles
- Digital Raster Graphics (DRG) files
- Digital Ortho Quarter Quads (DOQQs)

- Factors:
- Existence of extant  domain specific MD, e.g., FGDC for descriptive and technical MD
- Number of layers of the resource, e.g., representation & file?
- Point in resource lifecycle wishing to document

- Implementing the PREMIS Data Dictionary at Stanford

## Use of PREMIS Object Data Elements – Scenario 2:  GIS Dataset

- Domain specific needs for  Object:
- Context, especially for semantic underpinnings, e.g., Abstract, description of purpose, intended use of data
- No place for this in PREMIS(?)
- Perhaps <object><relationship> <relatedObjectIdentification> for an explanatory website?
- Environment
- HW/ SW info pertinent at time of data creation (?)
- “Significant properties”
- Data Quality – describing completeness, logical consistency, attribute accuracy
- Data Trustworthiness – data creator / provider reliable? = “authentic”
- Data Provenance – processes & sources for dataset = “understandable”
- Better understanding of what’s contained in a “format registry” - & their existence!

- Implementing the PREMIS Data Dictionary at Stanford

**Notes:**
Example of importance of intended use of data:  
 Context:  Example:  Street network of same metropolitan area.   First dataset is official street centerline file used by emergency services to locate addresses.  The 2nd,  very similar dataset is used for a tourist map so that aspects of the road network including topography, angles & geometry of the road network is more important than the actual street addresses.  If the explanation for the intended uses of this data doesn’t exist inherently in the dataset, would be important to record in metadata so as not to misinterpret the data.  Is a place in FGDC for this; but if that info doesn’t exist, might there be a place in PREMIS?  

Environment & significant properties:  
  Important to know about the events, parameters & source data which influenced or impacted the creation of the data set prior to its ingestion into the archive.  GIS data sets may have gone through many processes, and sources prior and during creation;  knowing something about those processes and sources would be important in order to fully understand the data that you’re getting.  Important to be able to establish the trustworthiness & quality of the data prior to relying upon it.  Can do with Object entity via “environment”, “significant properties” and “relationship/relatedObjectIdentification”, but

## Use of PREMIS Event Data Elements

- Event :
- Would prefer the option to describe process of data creation
- Merge c:\temp\states1;c:\temp \states2; c:\temp\USA
-  (includes process = “merge” and data sources

- Why this event?
- Important to describe processes during different phases of lifecycle, even prior to ingestion
- Not to be able to do so – problemmatic for geospatial resources
- Advantage – can describe events once in repository, unlike FGDC

- Implementing the PREMIS Data Dictionary at Stanford

## Issues & Challenges

- Getting domain specific MD would help!
- If not, getting important prez info from data creators   -- uh huh -- uh huh!!
- How to determine what is truly necessary for dataset use?
- Is this level of documentation still bit preservation?
- Getting buy-in from domains, e.g., geospatial

- Implementing the PREMIS Data Dictionary at Stanford

## Questions? / comments?

- Nancy J. Hoebelheinrich
- nhoebel@stanford.edu

- Implementing the PREMIS Data Dictionary at Stanford