Make your own free website on Tripod.com
« December 2005 »
S M T W T F S
1 2 3
4 5 6 7 8 9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29 30 31
You are not logged in. Log in
Entries by Topic
All topics  «
Blog Tools
Edit your Blog
Build a Blog
RSS Feed
View Profile
Related Links
DASER Home
ASIST
Digital Archives for Science & Engineering Resources (DASER) Blog
Saturday, 3 December 2005
Leslie Johnston, UVa: Repository Development at the University of Virginia Library
Mood:  sharp
Notes by Christina Pikas

She is discussing a curated digital library. It's been around since 2003.

Fedora: Flexible Extensible Digital Object Repository Architecture

Not an out-of-the-box repository, it's the underlying toolkit that is a Digital Asset Management architecture (Mellon funded, UVa and Cornell, for the software development, but not for their implementation)

Assumptions
- part of a global network of repositories
- all media types
- searching and browsing equally important
- curated
- primary users UVa community, they do have restricted content
- they'd like to have all digital collections in this repository

Process
Phase I, 2003, prototype
- electronic texts from the library's special collections
- art architecture ...
- got a lot of feedback (130 comments), they categorized, ranked, prioritized them
- number one comment: have more stuff

Phase II, Fall 2004 (final for Fall 2006)
See her article in D-lib for information on testing.

What did it take?
Standards
- ad hoc group documented production standards for media files
- metadata steering group documented local encoding practice, minimum standards, mapped various standards to the local standard
- community digitization standards

Content production
- subject librarians select, with technical assessment (ease of production, need for metadata enrichment, time constraints such as instructional deadlines, funding)
- centralized digital library production service (w/7.5 FTE plus student "scanning monkeys")
- new software tools and scripts

Development
- working groups for functional requirements
- functional requirements and analysis of media files and metadata to document content models (classes of objects and behaviors and mechanisms)
- processes for ingest
- interface
- search

Technology

Developers
- they had no budget
- they borrowed people from other parts of the library

Library Content
- huge queue of stuff to be done
- science stuff (herbarium images, glass astro slides from the parallax project)

Faculty Content
- born digital
- digital humanities projects

Support- librarians, programmers

D. Stern - seems intimidating, but it only took 3 programmers 2 weeks to be able to add info

Posted by asistdaser at 3:10 PM EST

View Latest Entries