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

PREMIS Implementation Registry

Carolina Digital Repository

Activity Name: Carolina Digital Repository
Organization: University of North Carolina at Chapel Hill, University Library
Organization Type: Library
Content Type: Audio - yes
Cartographic Material
Datasets
Images - yes
Other
Text-based Materials - yes
Video - yes
Websites
Origin of Content (digitized, born digital,
or both):
Digitized and born digital
Description: The Carolina Digital Repository (CDR) is being designed as repository for material in electronic formats produced by members of the University of North Carolina at Chapel Hill community. Its chief purpose is to provide for the long-term preservation of such materials. By preservation we mean the ability to ingest the material, index and search it, replicate it, and keep it safe from alteration. The project is recording and/or mapping to PREMIS elements as the repository with a preservation focus is built.
Start Date: 2008-01-01
Stakeholder/Audience Varies by collection. Some collections are targeted toward a specialized audience and in some cases access is restricted to a designated community. Other collections are geared to the general public as well as research and instruction on the UNC campus.
Website: http://www.lib.unc.edu/cdr/
Notes: https://cdr.lib.unc.edu/index.jsp http://www.lib.unc.edu/blogs/cdr/ We are using PREMIS to an extent that goes beyond "planning stages" but our implementation is still a work in progress and we intend to develop beyond what we are doing now.
Implementation Details:
What repository workflows or functions does your PREMIS Metadata support? Object information generated from FITS is used for generating thumbnails and access formats. Authentication via checksums (process compares against iRODS catalog using data also recorded in PREMIS). Building preservation reports, including events report a vailable to end-user.
What PREMIS data module entities are represented in your implementation? Object, Agent, and Event
How is preservation metadata stored in your repository? PREMIS XML for Object, Agent and Event entities. FOXML and the iRODS catalog provide additional semantic elements for on-demand PREMIS reports.
What ancillary resources and tools do you use to support your PREMIS implementation? Locally developed Java web apps plus Fedora Commons, iRODS data grid, Solr search engine and the Duke Data Accessioner Controlled Vocabularies id.loc.gov Tools Curatoršs Workbench FITS, which includes JHOVE, Exiftool, National Library of New Zealand Metadata Extractor, DROID, FFIdent, and File Utility. Extension Schemas FITS reporting schema Registries Included in FITS
Is your preservation metadata created internally, imported from external sources, or both? Both
Is your preservation metadata used only internally or is it shared with external organizations? Shared -- PREMIS events for each object in the repository may be downloaded in PREMIS XML via the user interface.
Example File Name: 33_UNC_eventmd.xml
Description of Example Files and/or Additional Example Files: 39_UNT_premis_object.xml