jcdl contentmodels

Introduction to Fedora and Its Applications: 

Introduction to Fedora and Its Applications June 7-11, 2004 JCDL, Tucson AZ Ronda Grizzle University of Virginia Ross Wayland University of Virginia Chris Wilper Cornell University

Fedora Content Models: 

Fedora Content Models Deciding how to structure and deliver your content.

Review of Fedora Object Model: 

Review of Fedora Object Model

Users access data objects through behaviors.: 

Application Users access data objects through behaviors. Dynamic data services

Repository Managers have direct access to each component of a data object.: 

Repository Managers have direct access to each component of a data object.

Digital Object Model Architectural View: 

Persistent ID ( PID ) Default Disseminator Datastream (item) Datastream (item) Datastream (item) Your Extension Your Extension Digital Object Model Architectural View

Digital Object Model Example “content model”: 

PID = uva-lib:100 Default Views Image (mrsid) DC (xml) Thumbnail (jpeg) Image Views Metadata Views Get Profile List Items/Get Item List Methods Get OAI_DC Get Thumbnail Get Medium Get High Get MARC Get DC Multiple Disseminations Digital Object Model Example 'content model'

Digital Object Model Service Relationships: 

Digital Object Model Service Relationships

Fedora Content Models: 

Fedora Content Models Definitions

What is a Content Model?: 

What is a Content Model? Describes the internal structure of a group of similar Fedora objects Number of datastreams Types of datastreams (MIME types) Number of disseminators Types of disseminators Loosely defined; not currently an integral part of Fedora architecture

How are Content Models Useful?: 

How are Content Models Useful? Provide a handle for describing the structure of similar groups of Fedora objects Facilitate the creation of 'batches' of like objects Facilitate identifying and querying similar groups of Fedora objects in a repository

Which content model to use ?: 

Which content model to use ? Fedora does not prescribe a content model for objects There appear to be two primary ways of thinking about content models Simple or 'atomistic' models Compound models Choice of content model is dependent on the structure of your content, your internal workflow, and your anticipated delivery and search methodology

Content Model Categories: 

Content Model Categories Atomistic – a data object with one or more content datastreams that are all considered primary to the object. Compound – a data object consisting of multiple content datastreams that are not all primary to the object.

Atomistic Model: 

Atomistic Model

Atomistic Example: 

Atomistic Example

Compound Model: 

Compound Model

Compound Example: 

Compound Example

Pros/cons of Atomistic approach: 

Pros/cons of Atomistic approach Pros Enables wider discovery of content in different contexts Provides greater flexibility in reuse of objects Cons Creates greater number of objects Relies on metadata or markup to maintain associations between physically related objects

Pros/cons of Compound approach: 

Pros/cons of Compound approach Pros Tightly bundles related content Makes maintenance of related content easier Cons Limits discovery of bundled content in contexts outside the primary object Creates a greater number of datastreams per object

Content Models at UVa: 

Content Models at UVa

UVa Fedora Project: 

UVa Fedora Project (www.lib.virginia.edu/digital)

UVa Default Disseminator: 

UVa Default Disseminator One behavior definition shared by all objects. Methods interpreted for each object Methods like: getPreview getLabel getDescription getFullView getDefaultContent Collector

Image Content: 

Image Content

UVa Image Content Models: 

UVa Image Content Models Bitonal 1 Bitonal TIFF datastream HighRes 1 MRSID datastream 1 static JPEG screen size datastream 1 static JPEG thumbnail datastream LowRes 1 JPEG screen size datastream 1 JPEG thumbnail datastream

UVa Bitonal Content Model: 

UVa Bitonal Content Model

UVa Bitonal Content Model: 

UVa Bitonal Content Model link

Bitonal Image Example: 

Bitonal Image Example link

UVa HighRes Content Model: 

UVa HighRes Content Model

UVa HighRes Content Model: 

UVa HighRes Content Model link

HighRes Image Example: 

HighRes Image Example link George Catlin and his Indian Gallery, organized by the Smithsonian American Art Museum in 2002

UVa LowRes Content Model: 

UVa LowRes Content Model

UVa LowRes Content Model: 

UVa LowRes Content Model link

LowRes Image Example: 

LowRes Image Example link

Text Content: 

Text Content

UVa Text Content Models: 

UVa Text Content Models EAD (transcription and page images) TEIGenText (transcription only) TEIBook (transcription and page images) TEILetter (transcription and page images) PageBook (page images only)

EAD Finding Aid Content Model: 

EAD Finding Aid Content Model

Finding Aid Example: 

Finding Aid Example link

UVa TEI GenText Content Model: 

UVa TEI GenText Content Model

UVa TEI Book Content Model: 

UVa TEI Book Content Model

1st TEI Book Example: 

1st TEI Book Example link

2nd TEI Book Example: 

2nd TEI Book Example link

TEI Letter Example: 

TEI Letter Example link

UVa PageBook Content Model: 

UVa PageBook Content Model

Book Page Image Example: 

Book Page Image Example link

Quantitative Data: 

Quantitative Data XML Codebook SQL Database

UVa Quantitative Data Content Model: 

UVa Quantitative Data Content Model

1st Quantitative Data Example: 

1st Quantitative Data Example link

2nd Quantitative Data Example: 

2nd Quantitative Data Example link

Collection Content Models: 

Collection Content Models

Definition of a “collection”: 

Definition of a 'collection' A collection is an aggregation of related content. The criteria that governs membership in a collection can be implicit (i.e., rule-based) or explicit (i.e., members are enumerated).

Explicit Collection Content Model: 

Explicit Collection Content Model

Explicit Collection Example: 

Explicit Collection Example link

Datastreams containing references to other objects function as a “pseudo collection”: 

Datastreams containing references to other objects function as a 'pseudo collection'

Implicit Collection Content Model: 

Implicit Collection Content Model

Implicit Collection Example: 

Image courtesy of Bill Parod [search] [art] Dissemination: Image with Metadata Implicit Collection Example

Other Uses of Collection Objects: 

Other Uses of Collection Objects

The digital library as a network: 

The digital library as a network

Modeling Serials: 

Modeling Serials

Quantitative Data Collections: 

Quantitative Data Collections

Descriptive Modeling: 

Descriptive Modeling [link]

Census Data: 

Census Data

Collecting Scholarly Projects: 

Collecting Scholarly Projects

Fedora at Other Institutions: 

Fedora at Other Institutions

Fedora @ Northwestern: 

Fedora @ Northwestern [link] Image courtesy of Bill Parod

Slide65: 

content maps container node file node relationship Faculty may sketch out their course content, relationships and pathways through this content using a simple set of moveable objects or nodes. web resource notes Fedora @ Tufts Slide courtesy of David Kahle

Slide66: 

OKI andamp; FEDORA Leveraging OKI technical standards will facilitate the sharing, distribution and integration of this new educational tool in educational systems beyond Tufts. Fedora @ Tufts Slide courtesy of David Kahle

Content Submission (NSDL): 

Content Submission (NSDL) [NSDL DEMO]

Fedora Future Development: 

Fedora Future Development

Fedora 1.3 (July 2004): 

Fedora 1.3 (July 2004) Fedora Object XML (FOXML) New internal storage format (AIP in OAIS) Simple, direct expression of Fedora object model SIPs and DIPs - METS/f, FOXML Simple Authentication plug-in #1 HTTP basic authentication SSL user/password file Administrative Reporting Batch object modification utility

Fedora 2.0 (October 2004): 

Fedora 2.0 (October 2004) Authentication and Authorization Authentication plug-in #2 with LDAP tie in Basic ACL; move towards XACML policy expression language Fedora policy enforcement module Performance Scale testing (benchmark ~1 million objects) Concurrent usage stress Performance tuning as needed (ingest, search, dissemination) Resource Index (RDF) Object metadata (DC, Fedora) Object Delta metadata (all representations of object, with freshness dates) Relationship metadata Query interface Rebuild Repository Utility Delta Notification Model (publish and subscribe service for event notification) Full Featured OAI Provider Service ( support for sets, 'what’s changed') Consider SRW Interface Web Forms for Easier Content Submission

Next Development Proposal: 

Next Development Proposal Fedora R2R - Distributed, Federated Repositories Shared name resolution service Any repository can fulfill a dissemination request within a federation Fedora Proxy Service for distributed virtual repository Federated or distributed searching (SRW, OAI, other approaches) Shared web services (for behaviors) Repositories as Service Registries (like UDDI) Fedora Power Server High Performance (andgt;10 million objects) Storage expansion schemes Mirroring and Replication Repository clustering Load balancing Preservation feature set Quality of Service (QoS) and Fault Tolerance ? Object Creation Tools Simple workflow utilities based on content models Object 'workbenches' Web interface for document/content submission

Questions: 

www.fedora.info Questions

Today’s Presentations:http://www.fedora.info/pubs.shtml: 

Today’s Presentations: http://www.fedora.info/pubs.shtml