I'm not exactly sure what you mean by "the database entry for the <dao>."
At the moment, the only thing within the database that points to the
transcription of an item are the transcription records which can be
entered on the subobject form, and the associated STTagIDs which allow
you to match a subobject with a particular element within a transcription
by a reference to an ID attribute within that transcription. Since subobjects
(including root subobjects) can be matched with particular locations within
a transcription file via STTagIDs, the database can have three different
objects point to the same transcription file, and point to the appropriate
location within the transcription file that matches the beginning of this
particular object.
If you're referring to FindingAid field on the Object Form in the database,
that can contain a URL to the full finding aid or, if you choose, a locator
using XPointer syntax to specify a location within the finding aid that
corresponds
with this particular digital object, e.g,
http://www.libraries.psu.edu/crsweb/speccol/labor/pabridge.sgm
[Full Finding Aid]
http://www.libraries.psu.edu/crsweb/speccol/labor/pabridge.sgm#ID(photo5219)
[Locator within Finding Aid using XPointer syntax]
If you're going to use XPointer syntax, I *strongly* recommend using ID
attributes
in your EAD Finding Aids and specifying XPointer ID Locations (e.g., ID(name))
rather than using relative locations or other XPointer oddities. Do keep
in mind that much of the world's software does not currently process
XPointers when deciding what to put in your FindingAid fields in the database.
If you're actually wondering what will go within the <dao> element in
the finding aid to point to the digital object itself, that will probably
be a URL that will point to a page which will load the digital object
which we'll create at Berkeley after we get all the databases. As a necessary
byproduct of that fact, Berkeley is going to have to fill in the appropriate
addresses in the finding aids *after* we get the databases from the various
participating institutions, create the digital objects, and make them
available over the web. Which more or less translates to, I think that's
our problem, not yours. :)
Jerome McDonough -- jmcdonou@library.Berkeley.EDU | (......)
Library Systems Office, 386 Doe, U.C. Berkeley | \ * * /
Berkeley, CA 94720-6000 (510) 642-5168 | \ <> /
"Well, it looks easy enough...." | \ -- / SGNORMPF!!!
-- From the Famous Last Words file | ||||