Amy,
Below is an example of how we use <archref> to create links between files
at The Natural History Museum.
Like Richard Higgins we use a two level EAD encoded record to create a
break in what we quickly realized would have been unmanageable sized
records. Each record has an <archdesc> containing the detailed description
of a collection and the <dsc> contains brief summaries of component parts
of the collection from which links using <archref> are made to another
record containing a detailed <archdesc> with component summaries in <dsc>
as necessary.
<dsc>
<c01 level="otherlevel" otherlevel="class">
<did>
<unitid>cld-021005</unitid>
<unittitle>Diptera (flies) Specimen Collection</unittitle>
<abstract> The <archref href="cld-021005" actuate="user" show="replace">
Diptera (flies) specimen collection</archref> includes the collections
and/or types of many important dipterists. </abstract>
</did>
</c01>
<dsc>
Since we are using Cheshire II for display Rob Sanderson, Cheshire Software
Engineer added code to check for 'cld' as the first three characters and do
a search for that eadid as the URL generated for the HTML so that when you
click on the link it would take you to that document via a search.
So far it seems to work alright although maybe it's a bit clunky in terms
of navigation, ie. one click of the mouse too many but we've yet to think
up another solution. Any suggestions would be welcome!
Rachel
At 09:36 AM 11/6/01 -0500, you wrote:
>Bob,
>
>Your posting comes as welcome information, since I'm also looking at
>encoding a large document. Would you mind sharing how you did this with
>the Toscanini finding aid--that is, could you show us the actual code you
>used to make the "break"?
>
>Also, can anyone comment on their experiences using the method described in
>the EAD Application Guidelines, of using <archref> to establish and link a
>parent file with series files? (Described in section 7.3.3.2.)
>
>Amy McCrory
>Project Archivist
>Cartoon Research Library
>Ohio State University
>
>
>
>At 08:37 AM 11/6/01 -0500, you wrote:
>>I've worked (and am currently working on) finding aids that are two to
>>three hundred pages or more. As far as I can tell, the main problem with
>>long finding aids is not really a structural one, but rather that it takes
>>a long time for the pages to load in one's viewer/browser, especially if
>>one is using a 56K modem.
>>
>>I'm not sure this is entirely the proper way, but what I've done for some
>>of our huge finding aids is to "reinterpret" some of the structural
>>elements. Specifically, since in large finding aids the <c02 level
>>="subseries"> element leads to section breaks, I used that feature to
>>"break" the finding aid into smaller sections alphabetically.
>>
>>You can see what I've done with the scores that belonged to conductor
>>Arturo Toscanini:
>>
>>http://149.123.1.7/dynaweb/ead/music/mustoscanin/
>>
>>
>>The paper finding aid for the papers of conductor Bruno Walter was also
>>rather long (over 200 pages) but I didn't resort to that "breaking"
>>technique. Thus, the bulk of the collection (in Series 1) results in a
>>long loading time. Try it and see what you think:
>>
>>http://149.123.1.7/dynaweb/ead/music/muswalter/
>>
>>
>>Lastly, for an example of a finding aid (with only a single series) that
>>was rather long WITHOUT breaks, look at our collection of broadsides:
>>
>>http://149.123.1.7/dynaweb/ead/music/musbroadsides/
>>
>>
>>Though I say "what I've done," I would be remiss in not acknowledging the
>>help and assistance of my coworkers at my institution.
>>
>>
>>Bob Kosovsky, Librarian
>>Music Division -- The New York Public Library
>>[log in to unmask] [log in to unmask]
>>Listowner: [log in to unmask] ; [log in to unmask]
>>My opinions do not necessarily represent those of my institutions.
************************************************************************************************************
Rachel Perkins
Collection Level Description Officer
Department of Library and Information Services
The Natural History Museum
Cromwell Road, London, UK
SW7 5BD
020 7942 5646
[log in to unmask]
|