Appendix A: Seven Relational Databases

spacer gif

The Digital Assets Management Database consists of seven relational FilemakerPro Pro 5.0 databases. The different databases provide information on the surrogates, ranging from the individual files and the objects they represent to the broader context of collections and their particular hierarchical organization. All input (with the exception of Collection Level information) takes place in ten layouts ofSubObjectDB: ObjectInfo (2 Layouts), Versions, Rights, Access, Describe Structure and Sequence. Three further layouts provide orientational and navigational functions: Collection Overview, All Objects Overview, SubObjects Overview. Three additional layouts in SeriesDB facilitate the data entry for the Collections Level: Describe Structure, Add Info and Preview.

The export layout for the EAD sits in the SeriesDB, while the export layout for MOA2 has its home in SubObjectDB.

The following paragraphs give a brief overview over the 7 individual databases, their functionality and interrelation. I have ordered the presentation of the databases by the hierarchy level at which they capture data.
spacer gif

Collection Level:

CollectionDB and SeriesDB have a one-to-many relationship and describe the set of Series comprising a Collection. For example, a collection of conceptual art may be represented by several series such as Videos, Installations, Performances, etc, which in turn may branch out into separate (sub)series. Within SeriesDB, individual entries take their place within the hierarchy by a system of parent - child relationships. Each Series must have a parent, and may have further children. The data captured in Collection DB and SeriesDB make up the structural backbone of EAD mark-up by providing the collection hierarchy tagged as <coX> in the final finding aid.
spacer gif

Object Level:

ObjectDB and SubObjectDB have a one-to-many relationship and describe the set of subobjects comprising an Object. For example, an artist's book may be represented by various pages grouped into various chapters. Within ObjectDB, individual entries take their place within the hierarchy by a system of parent - child relationships. Each subobject must have a parent, and may have further children. The data captured in ObjectDB and SubObjectDB provides (1) the EAD with item-level descriptive information, and (2) MOA2 with the exact structural description of a complex Object.
spacer gif

Surrogate Level:

VersionDB, ImagingDB and TranscriptDB describe the surrogate digital files created for each object and its subobjects. VersionDB tracks settings for master files and derivatives on an object level, while ImagingDB and TranscriptDB host the information on the actual files created for each subobject. The data captured in VersionDB facilitates the easy set-up of image and transcript files for all the subobject of one object. The data captured in ImagingDB populates the MOA2 mark-up with the individual files found in the structure of a complex Object. The ImagingDB hosts the transcript or any other related textuals and will facilitate TEI mark-up of text documents associated with an Object.

 


Back  |  Appendix A  |  Appendix B