Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

Time-Based Media Preservation Repository Use Cases:

...

Include Page
Indiana University Use Case - Ingest of large audio and video files

...

Title (goal)

Indiana University Use Case - Ingest of large audio and video files

...

  1. Output from time-based media digitization workflow is uploaded out-of-band to HPSS-based HSM system via PFTP, GridFTP, or Globus Online:
  • Master (as large as 100-200GB), mezzanine, and derivative video files in .mov, .mxf, and/or .mp4 wrappers
  • Master and derivative audio files in Broadcast WAV (.bwf) and .mp4
  • Technical, process history, and descriptive metadata in XML files
  • File checksums (MD5)

2. Fedora projects over content and metadata stored in HPSS and on filesystem in order to manage fixity and mediate access.

Dissemination of large audio/video files

Title (goal)
 Access to / dissemination of large audio/video files
Primary Actor Collection manager/curator
Scope 
Level 
Story

Collection manager finds identifier for audio/video object for which he/she wants to download master or mezzanine file (managed in Fedora via projection onto HPSS) and makes request for file through locally-developed web application, having authenticated via CAS. Application and/or Fedora are able to authorize download of file based on user's identity, user/group permissions on object, and role/group membership information obtained via LDAP from Active Directory. File (may be as large as 200GB) is downloaded from HPSS to user-designated location.

Example of authorization: Master files from Lilly Library collections may be downloaded by users who have the role of Lilly Library staff. This role is determined based on the user's membership in a LillyStaff group in Active Directory.

more to come...

Fedora Triplestore Use Cases:

Easy traversal against the triplestore

Title (goal)
Easy traversal against the triplestore
Primary Actor 
Scope 
Level 
Story

a. bottom up: Given an object, list all the parents of all levels

b. top down: For a collection, we would like to know hierarchical structure of the object, even the relationship stored on its children. would like to know how many children of the object and how many grandchildren for each of its children...

c. statistical information for the objects with particular datastream on repository level: for example, we need to know how many items have a PDF file for a particular collection.

A great many example queries that have proved useful in the past are documented here.

Support Flexible data model change

...

Title (goal)

...

Include Page
Indiana University Use Case - Dissemination of large audio-video files
Indiana University Use Case - Dissemination of large audio-video files

Fedora Triplestore Use Cases:

Include Page
Indiana University Use Case - Easy traversal against the triplestore
Indiana University Use Case - Easy traversal against the triplestore
Include Page
Indiana University Use Case - Support Flexible data model change
Indiana University Use Case - Support Flexible data model change

...