Content Comparison

Driving Principles for the CSH Repository

1. The data model should provide a model of the physical form of the CSH documents.
2. The data model should capture all the relationships among the documents.
3. The metadata profile should be designed to appropriately represent the objects.
4. The repository should implement access policies and access features for tailoring multiple access profiles.
5. The repository should facilitate a well documented work-flow for implementing access policies and archival.

Design Features

The CSH Repository should have the following features, as driven by the principles stated above.

Navigation Features:

...

This is an evolving list of use cases and design features that are supported by the various data models. In the future, this page may be split into record-specific use cases and design features.

Use cases

Navigate and view the stored records (assumption: Access to the dark archive is restricted to hospital and/or Library of Virginia staff, who have full access privileges, pending the development of graduated access roles)

Design features

Representation:

1. Create hierarchies of collections and objects to represent the original intellectual organization of CSH records.
2. Order items (objects or collections) in order to represent the original intellectual organization of CSH records.
3. Integrate multiple representations of a scan within an object. These include: digital master, access copies, thumbnails, transcriptions, aggregated scans (such as a PDF file that includes multiple pages in a register)
4. Represent associated files at appropriate levels. For example, a PDF file representing multiple scans may be associated with a parent object, while images of each of the scans will be associated with child objects. 
5. Attach metadata with collections and objects at each level. 

Access/retrieval:

1. List collections (board meeting registers, patient reports, financial records, photosphotographs, etc.,
2. Listing of individual pages from above mentioned registers, reports, and records,
3. Ability to navigate to the previous, or next register, or report file, or records register,
4. Ability to navigate to the previous or next page within a register or report file or records register,
5. Ability to navigate to PDF versions of whole registers, report files, or records,
6. Ability to navigate to the digital masters, derived versions, or thumbnails of individual images (as well as whole document PDFs) as per access privileges

Metadata presentation:

The following metadata information needs to be presented to users (based on their access privileges):

1. Descriptive and technical metadata related to individual files
2. Descriptive and technical metadata related to collections (registers, patient reports, etc.))
3. List items (objects or collections) within a collection
4. View metadata associated with items
5. List files associated with items
6. Retrieve a file associated with an object

Navigation:

1. Locate the the first item in a list (for example, pages in a register or registers in a collection)
2. Locate the last item in a list
3. Browse to the previous or next item in a list 

Access policies:

The repository needs to control the access to the materials by implementing various levels of access. For example, a class of users may only be allowed to access low-resolution versions of the scans while some others (like CSH administration) may be allowed access to the digital masters.