Support for identifying external source records

[alexduryee]

Creator of issue

1. Alex Duryee
2. [email protected]

The issue relates to

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

Wanted change/feature

• Text: During discussion regarding SNAC/ArchivesSpace integration, there was a use case for including a source instance of an EAD document. For example, if a user generates a finding aid from a SNAC Resource record, there is no way to identify the source record in the new instance. This may also be an issue for aggregators, which have derived copies of EAD instances from harvested sources.

[kerstarno]

Hi @alexduryee,

question for clarification: was this looking at EAD 2002 or EAD3? Follow-up question: if this was looking at EAD3, couldn’t the <source> element within <control> be used for this?

Would be great if you could answer these two questions ahead of the Washington meeting and - in case that EAD3 was used as a basis - explain in a little more detail, why <source> wasn't considered useful?

Thanks.

[fordmadox]

BPG possibility: show an example of how this can be done using <maintenanceEvent> with @maintenanceEventType derived and having a <reference> in <eventDescription> if one wanted to point to the source.

[kerstarno]

TS-EAS discussed this issue in the context of the EAD revision meeting in Washington, DC, on 24 July with the result as mentioned in the previous comment. With this, this issue is more of a Best Practices Guide issue than a schema issue and will be transferred to the EAS-Best-Practices repository.

[deletedname]

If someone can send me some example code for this, I'll add it to BPG