If you have a collections management system (e.g. ArchivesSpace), it should be theoretically possible to derive EAD dynamically from the database when a user requests it, so the EAD is always current.

On Wed, Feb 17, 2016 at 4:16 PM, Dale Patterson <[log in to unmask]> wrote:
It strikes me that suggesting the EAD does not work for record groups, as some have, because they will not be up-to-date, misses the point of record group processing; you will always be behind with records from active offices.  It doesn't matter if it is from a database, or a typewritten document or an EAD instance, new material is always coming in.  We even use an XML-based database which updates our EADs as we work and still find ourselves behind.  It is not EADs fault. 

On 2/17/2016 4:03 PM, Michele R Combs wrote:

Just out of curiosity, why do you need to keep track?  Why not just re-export your EAD every quarter?


Alternatively, why not just re-export the finding aid each biannually and the time of the new stuff is added?

 

Michele

 

From: Encoded Archival Description List [mailto:[log in to unmask]] On Behalf Of Peter Carini
Sent: Wednesday, February 17, 2016 3:56 PM
To: [log in to unmask]
Subject: Re: EAD3 Implementation

 

 

Again, while this works for manuscript collections it fails when it comes to archival record groups, which are a moving target and will always be out of sync with what is actually available in the repository. We add significant holding so up to 30 different records groups biannually. It is almost impossible to keep track of which need new finding aids generated. 

 


-- 
L. Dale Patterson
Archivist-Records Administrator
General Commission on Archives and History
United Methodist Church 
36 Madison Ave., Madison, NJ 07940
973-408-3195   www.gcah.org
https://listserv.loc.gov/cgi-bin/wa?A3=ind1602&L=EAD&E=quoted-printable&P=123204&B=--001a114dfc4a50cd7a052bfdcc0b&T=text%2Fhtml;%20charset=UTF-8
listserv.loc.gov
CC-MAIN-2023-50
5734
application/http; msgtype=response
sha1:OQE4B4XXGYVXGNQZ5MIG3W4ESDJ7RXMQ
<urn:uuid:2dab5ec3-6efe-4461-af62-032337399ed1>
2023-12-05T17:56:37Z
104.16.54.16
text/html
sha1:VH3QJQU6F65RX3L6KGLYFQUGEZMUEIXN
<urn:uuid:4398e8d3-944c-4c96-b409-1e2e2210606c>
https://listserv.loc.gov/cgi-bin/wa?A3=ind1602&L=EAD&E=quoted-printable&P=123204&B=--001a114dfc4a50cd7a052bfdcc0b&T=text%2Fhtml;%20charset=UTF-8
response
<urn:uuid:961bb6f1-c270-4874-a4b9-a6900c86750e>
isPartOf: CC-MAIN-2023-50
publisher: Common Crawl
description: Wide crawl of the web for November/December 2023
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-156
software: Apache Nutch 1.19 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.5-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/