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

PREMIS Implementation Registry

Scholars Portal Project

Activity Name: Scholars Portal Project
Organization: Ontario Council of University Libraries
Organization Type: Consortium
Content Type: Audio
Cartographic Material
Datasets
Images
Other
Text-based Materials
Video
Websites
Origin of Content (digitized, born digital,
or both):
Digitized and born digital
Description: Consortium representing the 21 university library systems in Ontario. The Scholars Portal department provides shared IT services to the members, including things like SFX, research support software (e.g. Refworks), and maintenance of shared digital collections.
Start Date: 2010-09-01
Stakeholder/Audience The 21 member institutions of OCUL are our primary audience (or Designated Community, in TRAC parlance).
Website: http://www.scholarsportal.info
Notes:  
Implementation Details:
What repository workflows or functions does your PREMIS Metadata support? Content management - monitoring the nature of our collection with regard to file formats, migration strategies, etc. Integrity checking - contains the fixity information for all files in a given object.
What PREMIS data module entities are represented in your implementation? Object, Event
How is preservation metadata stored in your repository? XML in a NoSQL database.
What ancillary resources and tools do you use to support your PREMIS implementation? We use FITS to do most of our file description including format and checksums. So, we use JHOVE, DROID, and all the other stuff that it uses. Extension Schemas, Registries, File formats are stored as a reference to PRONOM.
Is your preservation metadata created internally, imported from external sources, or both? Internally, primarily through FITS
Is your preservation metadata used only internally or is it shared with external organizations? Internally
Example File Name:  
Description of Example Files and/or Additional Example Files: