Add a new type of event (life cycle traceability)

[ArchivageNumeriqueSIAF]

Creator of issue

1. Manonmani Restif (manonmani.restif@culture.gouv.fr)
2. Louis Vignaud (louis.vignaud@culture.gouv.fr)
3. Archives de France (SIAF)
4. @ArchivageNumeriqueSIAF

The issue relates to

• [ ] EAC-CPF schema issue
• [ ] EAC-CPF Tag Library issue
• [x] EAD schema issue
• [x] EAD Tag Library issue
• [ ] Schema issue
• [ ] Tag Library issue
• [ ] Suggestions for all schemas
• [ ] Suggestions for all Tag Libraries
• [ ] Other

Wanted change/feature

• Add descriptive metadata to encode some event affecting the archival resources that are not pertaining to the chain of ownership and custody before reaching the archives (<custodHist>) or archival activities pertaining to the described material (<processInfo>).
• These two existing elements do not cover activities done by the creator of the archival material such as it’s creation, revision, deletion, destruction…, or by the archival institution other than description, such as digitization, conservation, exhibition, etc.
• Especially for born digital documents, some information can be retrieved through technical metadata or documents deleted by the creator could be restored partially or completely.
• As to date, no element of EAD2002 or EAD4 enable to encode satisfactorily these informations which might raise issues of communicability and more broadly ethical issues.

Suggested Solution

Solutions proposed :

1. Extend the perimeter of and/or to allow these informations.
2. Create a new element inspired by :

• RiC-CM : relation RiC-R057 “is event associated with” and attribute RiC-A18 “event type”
• LIDO model of ICOM : element and child element (http://www.lido-schema.org/schema/v1.1/lido-v1.1.html#eventSet)
• Event element (inspired by PREMIS) from SEDA, french standard for carrying digital born archives.

Two examples of encoding are submitted below.

Your Environment can be a clue to a bug

EAD4_Example_describing_events_LIDO.pdf EAD4_Example_describing_events_SEDA.pdf

[kerstarno]

Will be discussed by TS-EAS during their meeting on 12/13 August 2024 at the SAA Annual Meeting.

[kerstarno]

Adding the following comment from the general feedback provided by Ruth Tillman in https://github.com/SAA-SDT/eas-schemas/issues/131 for further review as it might be pointing in a similar direction concerning the entity of events.

I think that there was some potential in <chronlist> to map to linked data event structures (e.g. the Bibframe ARM events) and perhaps someone can figure out how to demonstrate this in an example too. Maybe that's too into the weeds. I know that doing it as anything other than HTML would not validate with EAS tools.

[kerstarno]

Adding the following comment from the general feedback provided by Mary Lacy in #133 for further review as it relates to <chronlist> as the "home" of events in EAD3 (and EAD 2002).

One particular case of loss of specificity we find disturbing is the removal of <chronlist> as a valid tag. Instead, one must use the generic table tagging which removes the ability to tag dates (and geognames, as was added in EAD3). It is difficult for us as we continue to work to take advantage of tags made available in EAD3 to know what will become of them in EAD4.