|
|
|
|
|
Different types, functions,
structures |
|
flat file, relational,
hierarchical…. |
|
DAM databases are unique |
|
Objects are digital surrogates |
|
e.g., images of an object |
|
Objects are digital assets
themselves |
|
e.g., digital video clips,
digital images of events |
|
Digital object in a database
field = repository |
|
Digital object stored
separately = referatory |
|
|
|
|
|
|
Librarians have crafted
metadata for decades |
|
The schema (read open standards) |
|
Dublin Core, VRA, METS, etc |
|
MARC record and the OPAC |
|
Database of bibliographic and
item records |
|
Searchable, indexed |
|
No digital surrogate, only
metadata |
|
Cataloged objects are physical |
|
Interconnected: convert
DC->MARC; Embed DC in HTML |
|
|
|
|
|
Libraries: |
|
Digital library initiatives at
larger institutions, national efforts |
|
Institutional collections –
formal cataloging |
|
Specialized data sets (social
science, GIS, etc) |
|
Repositories of scholarship
(faculty and student…both archival and ephemeral) |
|
Instructional technologists: |
|
Faculty collections scattered
in space, different platforms |
|
Excel, Access, FileMaker,
analog content |
|
Course management systems,
ePortfolios |
|
Training and support issues |
|
Technologists: |
|
Another db on a server –
reliability, backup, authn/access |
|
|
|
|
|
Among technologists,
librarians, faculty, students |
|
All confront: |
|
Policy issues |
|
intellectual property, rights
management |
|
Presentation issues, in class
and out |
|
manipulation, retention,
printing |
|
Metadata issues |
|
standards, effort to create |
|
Open source DAM? |
|
By higher ed, for higher ed |
|
Greenstone, Fedora, Connexions,
DSpace, Sakai |
|
|
|
|
|
Digitize |
|
Standards per collection, by
discipline, national and international requirements |
|
Full-resolution versus service
quality, thumbnails |
|
Create metadata |
|
Standard schema, with additions
and mapping |
|
Make accessible |
|
Copyrights, releases,
consortial agreements, export |
|
Connect to course management
systems |
|
See the OCLC E-learning white
paper |
|
Open Archives Initiative and
WorldCat |
|
|
|
Allows collaborative and
distributed collection development/management |
|
Basic and advanced searching
across collections, across sites (federated searches, virtual collections,
stored result sets) |
|
Web-based client with
easy-to-use interface |
|
Common client-side
players/viewers |
|
Client tools for manipulation,
comparison, per-user annotation |
|
Support for multiple metadata
standards |
|
Support for many object
formats, and developing formats (e.g., jpeg 2000) |
|
Support for high-resolution,
zoom-in features |
|
Supports Unicode text for
display and searching |
|
URL access to objects |
|
Customizable display interface |
|
Based on open standards
(database, metadata, etc.) |
|
Flexible access control list
features |
|
Standards-based export
functions to avoid “lock-in” and promote remote indexing |
|
Platform (hardware, operating
system) agnostic – server and client |