EADs

From UA Libraries Digital Services Planning and Documentation
(Difference between revisions)
Jump to: navigation, search
(New page: Archival staff are almost finished with revamping old Word and PDF finding aids into EAD (Encoded Archival Description) finding aids. Thus this diagram shows the creating of the EAD dur...)
 
Line 1: Line 1:
Archival staff are almost finished with revamping old Word and PDF finding aids into EAD (Encoded Archival Description) finding aids.    Thus this diagram shows the creating of the EAD during processing.  The archivists keep their copy in Archivists Toolkit, where it was created.  If remediated, or links are added, the newest copy is kept there, and Jody is notified to pick up new or altered EADs from a folder on the Share drive. When she does, she leaves a copy of each in a nearby folder dated for time of pickup.
+
This diagram shows the creation of the EAD in Archivists Toolkit during processing.  The archivists consider the copy in Archivists Toolkit to be the copy of record, so EADs altered by Digital Services are to be stored there as well as in the archive.
  
Some discussion of the linking from EADs, instructions, and implementation, can be found in [[Linking_out_from_EADS]].  Apart from the work developed for the Cabaniss project [[Cabaniss]], Jody has not yet developed the software to locate digitized content and link it into the proper EAD in the proper place.  We'll have to work out how to determine the proper location from the metadata (there must be a box and folder number locatable in the exported metadata spreadsheet for each item, or in the generated MODS for each item.
+
EADs are exported by archivists from Archivists Toolkit and placed in the "new" or "remediated" folders in the share drive S:\Special Collections\Digital_Program_files\EAD directory.
  
Prior to that, Jody will develop the methodology and scripts for processing EADs for the archive.
+
Every Friday night, a script ([[Image:getEads.txt]] picks up these EADs, makes a datestamped directory in the "uploaded" directory there on the share drive  (for example, "uploaded_new_20100803"), copys the EADs to the corresponding "uploaded" directory (so the archivists will know what was picked up when), and then copies the EADs into Acumen and places them in an "notInDbase" directory on libcontent1 (under /srv/deposits/EADs/).  This is to give Acumen time to index the content, before adding the entries into the online database that feeds our [http://www.lib.ua.edu/digital/browse collection list].  We don't want dead links showing up in this list.
  
[[image:EAD.png]]
+
On the following early Monday morning, a second script runs ([[Image:EadsToDbase.txt]]) which looks through these EADs, adding information to or updating the database, so the links will appear online.  Then the EADs are moved to the /srv/deposits/EADs/new/ directory to await archiving (by Jody when it will not interfere with LOCKSS harvests.  The script used for this is [[Image:relocatingEads.txt]].
 +
 
 +
Some discussion of the linking from EADs, instructions, and implementation, can be found in [[Linking_out_from_EADS]].  We are currently in the throes of analysis and repair of data entry in both the item-level metadata and the EADs to enable automated linking to digitized content from the finding aid.  (Already this is enabled in the [[Cabaniss]] project.
 +
 
 +
 
 +
[[Image:EAD.jpg]]

Revision as of 08:57, 4 August 2010

This diagram shows the creation of the EAD in Archivists Toolkit during processing. The archivists consider the copy in Archivists Toolkit to be the copy of record, so EADs altered by Digital Services are to be stored there as well as in the archive.

EADs are exported by archivists from Archivists Toolkit and placed in the "new" or "remediated" folders in the share drive S:\Special Collections\Digital_Program_files\EAD directory.

Every Friday night, a script (File:GetEads.txt picks up these EADs, makes a datestamped directory in the "uploaded" directory there on the share drive (for example, "uploaded_new_20100803"), copys the EADs to the corresponding "uploaded" directory (so the archivists will know what was picked up when), and then copies the EADs into Acumen and places them in an "notInDbase" directory on libcontent1 (under /srv/deposits/EADs/). This is to give Acumen time to index the content, before adding the entries into the online database that feeds our collection list. We don't want dead links showing up in this list.

On the following early Monday morning, a second script runs (File:EadsToDbase.txt) which looks through these EADs, adding information to or updating the database, so the links will appear online. Then the EADs are moved to the /srv/deposits/EADs/new/ directory to await archiving (by Jody when it will not interfere with LOCKSS harvests. The script used for this is File:RelocatingEads.txt.

Some discussion of the linking from EADs, instructions, and implementation, can be found in Linking_out_from_EADS. We are currently in the throes of analysis and repair of data entry in both the item-level metadata and the EADs to enable automated linking to digitized content from the finding aid. (Already this is enabled in the Cabaniss project.


EAD.jpg

Personal tools