Indiana University Digital Library Program. Joint venture of Libraries and University Information Technology Services (UITS) formed in 1997Bloomington-based; supporting 8 campusesEngaged in digital collection building, infrastructure design/management, and research activitiesSupporting library, archive, museum, academic department, and faculty-based digital collections projects.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
1. Building a Fedora Architecture to Support Diverse Collections Jon Dunn
Digital Library Program
2. Indiana University Digital Library Program Joint venture of Libraries and University Information Technology Services (UITS) formed in 1997
Bloomington-based; supporting 8 campuses
Engaged in digital collection building, infrastructure design/management, and research activities
Supporting library, archive, museum, academic department, and faculty-based digital collections projects
3. Digital Library Content Types at IU Books
Musical score images
Music notation files
4. Current DLP Technical Environment: Access Systems DLXS (University of Michigan)
IBM Content Manager
Cushman Photograph Collection
DIDO: Digital Images Delivered Online
Page turners (sheet music, METS Navigator)
5. Current DLP Technical Environment: Storage DLP server disk storage
Tivoli Storage Manager
IU Massive Data Storage System (MDSS)
1.6 petabytes of StorageTek and IBM automated tape
Access via FTP, PFTP, HSI
6. Motivations for a repository Centralize access and preservation functions for IU’s digital collections
Reduce DLP staff time and attention needed to create and maintain collections
Enable librarians, curators, archivists to digitize new collections
Enable digital preservation
7. DL Infrastructure Project Proposal funded by University Information Technology Services to reengineer digital library infrastructure around Fedora
Builds on experience with Fedora in context of EVIA Digital Archive (ethnomusicology video)
8. Building services and tools around Fedora Searching/browsing of metadata and content
End-user UI for display/navigation of metadata and content
Cataloging and ingest tools
9. IU Content Models
10. Defining a content model Focus on what you can do with an object
Behaviors are primary
Behaviors are the way all external processes will interact with the object
Keep datastreams “private”
11. Diversity Multiple media types
12. Standard disseminators All objects subscribe to the default disseminator
Most objects subscribe to the metadata disseminator
Most objects subscribe to type-specific disseminators
13. Simple images Each image is a single Fedora object
Images are available in a variety of sizes
Each image belongs to one or more collections
15. Object-level disseminators Image
16. Collection-level disseminators Collection
viewText(pid, pagenum, style)
viewChunk(pid, label, style)
viewPage(pid, num, style)
17. Image Demos Sample Image
Frank M. Hohenberger Collection
U.S. Steel Collection
18. But what about the metadata? Different content types have different types of metadata
MARC for general library holdings
MODS for collections we catalog
TEI for textual collections
EAD for archival collections
Combinations: Some items need METS for structure, TEI for text, MODS for description, etc.
19. The solution: METS No, not the Fedora METS
METS within a datastream, and everything else within the METS
A standard way of dealing with DC, MODS, technical, structural, provenance, process, etc.
20. Implementing the disseminators Simple Image
RELS-EXT Paged Object
21. Want more info?
More detailed content model pages
are available on our project wiki.
22. IU Fedora Tools
23. Ingest Tool
The Ingest Tool transforms raw metadata and media files into Fedora objects that conform to our content models.
24. METS Navigator METS Navigator is a METS-based system for displaying and navigating multi-image digital objects.
It was built to be extendible and configurable.
Web pages with navigational structure are built from metadata in the repository.
Available from http://metsnav.sourceforge.net
Default METS Navigator Collection
Jane Johnson Collection
26. Using METS Navigator with Fedora METS document must meet minimal format requirements
Logical and physical structMap
Files marked with USE and GROUPID attributes
Files are URLs that point to Fedora
METS Navigator may be called from a disseminator, but it is better if called separately.
Full integration instructions
27. Cataloging tools No good solutions for non-MARC descriptive/structural metadata creation
Some exist for specific domains: e.g. art image cataloging
Need content- or collection-appropriate interfaces
Catalog directly into Fedora or into database?
Data synchronization issues
Common framework or separate tools?
Starting to investigate
28. Delivery tools Right now: collection-specific web sites
Moving towards: generic applications appropriate to content models
Examples: documentary photos, art images, books, sheet music…
May integrate components from other places (e.g. Virginia collector tool)
Exposing metadata to external services via OAI-PMH, SRU (for Metasearch)
29. Other tools and services via Fedora Service Framework Search tool
Expanded, with thesaurus support
Preservation integrity services
30. Infrastructure Project Challenges Time and resources vs. scope of work
Sorting out old collections – digital archeology
Implementing new infrastructure while continuing to do new projects
Maintaining current functionality
31. Infrastructure Project Challenges Metadata entry / cataloging tool design
Integration with MDSS/HPSS - classes of storage