PREMIS (Preservation Metadata, Data Dictionary Maintenance Activity)
Official Web Site  

PREMIS Implementation Registry

The Portal to Texas History

Activity Name: The Portal to Texas History
Organization: University of North Texas Libraries
Organization Type: Library
Content Type: Audio - yes
Cartographic Material - yes
Datasets - yes
Images - yes
Text-based Materials - yes
Video - yes
Websites - yes
Origin of Content (digitized, born digital,
or both):
Digitized and born digital
Description: The Portal to Texas History is a digital gateway to Texas history materials belonging to a growing number of partners that include museums, libraries, historical societies, government agencies, and colleges throughout Texas. Because of partners' contributions, the Portal has over two million digital images consisting of many types of materials such as photographs, maps, books, letters, manuscripts, artifacts, works of art and newspapers, dating from the early eighteenth century to the present. The Portal team at the University of North Texas provides strong leadership by supporting collaborative efforts with its partners, while pursuing the goals of accessibility, best practices and preservation of historical materials. The Portal's mission is to provide free online access to Texas history materials that can be used by educators, researchers and the public at large. The National Endowment for the Humanities has named the Portal to Texas History as one on the best online sources for education in the humanities.
Start Date: 2002-01-01
Stakeholder/Audience We make the majority of our content freely available to global users via the Internet.
Implementation Details:
What repository workflows or functions does your PREMIS Metadata support? We make use of PREMIS to record metadata about files stored in our digital content storage system. We also maintain a PREMIS event tracker for logging events in the lifcycle of our digital objects.
What PREMIS data module entities are represented in your implementation? We use Object, Agent and Event entities.
How is preservation metadata stored in your repository? We store object metadata in a METS wrapper using the PREMIS XML format. For PREMIS Events, we store them in a relational database, with a front-end to provide XML output on demand.
What ancillary resources and tools do you use to support your PREMIS implementation? Controlled Vocabularies We make use of a locally created controlled vocabulary for our PREMIS Events, notably in eventType and eventOutcome fields. These are available via our Vocabularies system at Tools We make use of JHOVE and File for extracting technical information from files ingested into the system. Extension Schemas The PREMIS Object entities are embedded within METS records. Registries
Is your preservation metadata created internally, imported from external sources, or both? We create the metadata internally from the source objects themselves.
Is your preservation metadata used only internally or is it shared with external organizations? It is currently used only internally. If it is shared externally, what exchange format is used? If we would need to share our PREMIS Object records, it would be in the form of METS records with embedded PREMIS.
Example File Name: 39_UNT_premis_event.xml
Description of Example Files and/or Additional Example Files: 39_UNT_premis_object.xml