We are using SQL Server to gather descriptive metadata destined for output
in the context of METS objects. The database, originally designed around
the MOA2.DTD, gathers all of the descriptive, administrative and structural
metadata necessary to generate METS objects with MODS descriptive metadata
and (minimal) MIX image technical metadata. However, the descriptive
metadata portions of the database were NOT designed around MODs. Rather,
long before MODS was conceived, The Bancroft Library staff helped us
identify the descriptive metadata elements the database needed to
accommodate for archival materials; and we have now mapped these elements
to MODS after the fact. An overview of our METS-based architectures is
At 12:19 PM 7/11/2003 -0800, you wrote:
>As I recall, there are a few IT people on this list. Has anyone looked at
>or worked on implementing MODS in a relationship database (oh, something
>like PostgreSQL or MySQL)?
>If not, then all MODS storage is in flat files now?
>I'm trying hard to convince the people involved in the Open Office
>bibliographic module project to adopt a MODS-like database model, but I
>really know nothing about DB design, so I don't feel qualified to offer
>specific suggestions on how to do this. If anyone has any suggestions,
>please let me know.
>http://www.fastmail.fm - A fast, anti-spam email service.
Lead Software Engineer: Research and Development
Library Systems Office
Rm 386 Doe Library
University of California
Berkeley, CA 94720-6000