NJVid – A Statewide Video Network Based on RUcore and Fedora

Rutgers Community RepositoryRUCORE

1

NJVid – A Statewide Video Network Based on RUcore and

Fedora

The Third International Conference on Open Repositories

Southampton, UKApril 1 - 4, 2008

Ronald C. Jantz, Grace Agnew, Isaiah BeardRutgers University Libraries


2

Topics for Discussion

A Statewide Video Network – An IMLS Grant Funded Project based on RUcore and Fedora

Architecture and Use Scenarios

NJVid Technical Challenges


3

NJVid – A Statewide Video Network

A digital video network supporting over 600 New Jersey institutions (academic, K12, & cultural heritage)

Three types of video collections• Video Commons – publicly available videos• Commercial videos available through educational

consortia• Lectures on demand – customized annotations of videos

Technical platforms based on RUcore and Fedora

NJVid Concept Architecture(Based on RUcore)

DigitalObject

Repository(Fedora)

Workflow Management

System

User Input(metadata)

4

Fedora Repository Service

Collection & Preservation Services

NJVid Commons

Partner PortalsNew Jersey Institutions

ObjectXML

Digital Video MasterMatrox Axio Encoder

Video

Object Ingest


5

Large Files - the Video Digital Object

Video Object

Repository ID

Metadata

Behaviors(Disseminators)

Data streams

MOV1 – QT stream

XML1 – transcript (opt)

ARCH1- Archival master(external datastream)

FLV1- download

SMAP1 – StrMap (TOC)

Descriptive

Technical

Source

Rights

Digital Prov.

XACML policy (external)


6

Architectural Challenges

Managing Large Video Files – Ingest, Presentation, and Preservation

Annotation of Videos for Lectures on Demand

Authentication and Authorization


7

NJVid Storage & Server Architecture

FedoraRepository

(Digital Objects)

Archival Masters

Streaming Server (Darwin)

Partner/Custom Portals

Fedora and MiddlewareHost Server

• Stream QuickTime• Download Flash

Local Storage/repos (NFS)

Backend Storage Server

Video Stream

• External Storage• Checksum validation


8

End User Scenarios

General Public Access to NJVid Commons

Instructor Annotation for Lectures on Demand

Student Access to Licensed Videos


9

Annotations of Videos

The basic concept is to allow an instructor tocustomize any video by selecting time segments

to beplayed as part of a course offering. Additional descriptive metadata and access permissions

can also be applied.


10

Annotating a Video

Instructor Annotation• Instructor logs in to special “annotation” portal and is

authenticated as “instructor” from ABC institution• Instructor selects and previews video to determine time segments

to be used for instruction• Instructor creates annotation object and references video to be

used• A structure map with appropriate time segments of the source

video is created• Additional access restrictions may be applied

Student Access• Logs in as “student” from institution ABC• Student selects “course 101” on Faculty portal and plays video• Disseminator/action script plays video according to time segments

in structure map


11

Annotation Portal Scenario

Institution: ABCAstronomy 101Review of Theories

Structure Map The Universe: 5’ to 11 ‘ Big Bang Theory: 20’ to 45’ Other Theories: 65’ to70’ URI – pts to video stream

Access RestrictionsAnnotation Screen Facsimile

Repository ID

Metadata

Behaviors(disseminator)

Data streams

SMAP1 – StrMap (TOC)

Annotation Object

Original VideoObject

QuickTime

Flash

XACML Policy

CollectionA

CollectionB

NJDH(Grant

Project)

V2

A1

SubCollection

B1

NJVid

CollectionC

V1

SubCollection

B2

FacultyCollection

V2

NJVid and RUCore – Two Fedoras and Distributed Collections

Solid line – explicit membershipDashed line – dynamic membership

Circles – collection objectsRectangles – content objects

12

V1 V3

isAnnotationOf

RUcore


13

Statewide Sharing of Multi-site Collection Content

Concept – Allow a collection manager to subscribe to any collection on a remote RUcore/Fedora site

Assumption – Each site reuses the RUcore data model and architecture

Indexing and Search Architecture• A common indexing service layer supporting all sites• Centralized indexes• Local control of collections thru RUcore collection

management services


14

Authentication and Authorization

Flexible access control based on Shibboleth framework

NJVid will need to support the full range of institutions • Participating institutions will need to provide LDAP directory information• Must establish agreement on shared attributes across institutions: person,

department, role

Architecture• One backend RUcore/Fedora repository supporting multiple

GUIs• Many front-end partner portals• Authentication – evaluating alternatives including DRAMA• Authorization using XACML policies


15

Further Development Challenges

Storage Architecture• Archival Storage and “Managed External”• Large file local ingest• Redundancy and dark archive

Preservation Framework

Installation of RUcore/Fedora at other institutions• More formal software development methodology• Release/support processes for multiple locations


16

RUcore Open Source Software

AREA Software/Tool/Technology

Applications PHP/MySql (by RUL) Journals Open Journal System (PKP) Search Engine Amberfish Workflow Management PHP/MySql (by RUL) Management Services PHP/PERL/MySql (by RUL) Handles/persistent IDs CNRI Handle server Video Streaming Server Darwin (Apple) Digital library framework Fedora OS/Webserver Linux-Solaris/Apache


17

Video Specifications

• Video source – analog and digital camcorder

• Archival master is uncompressed AVI

• Streaming protocol is QuickTime H.264

• 29.9 frames/second, 640 x 480 resolution, data rate from 384 – 512 kb/sec

• Delivery to user as QuickTime or Flash

NJVid – A Statewide Video Network Based on RUcore and Fedora

Documents

Transcript of NJVid – A Statewide Video Network Based on RUcore and Fedora