#151 Address custodial history in Guidelines

[Tom Elliott]

Currently, the EpiDoc Guidelines include no discussion of the custodial history mechanisms provided by the TEI. This should be remedied, not least because the DCLP project is making extensive use of same and therefore provides interesting examples.

[Scott Vanderbilt]

Bumped -> Future.

[Tom Elliott]

Reassigning to Elli with ask Scott D. because USEP has examples and is thinking about this right now.

[Elli Mylonas]

Will work on this for next release

[Elli Mylonas]

@sdigiulio and @ellimylonas looked at this issue. The link in the opening comment refest to the TEI <custodialHistory> element which is part of msDesc/adminInfo. We feel that Epidoc doesn't use this element, but instead, puts the same informatio in the origin and provenance elements which appear in the history section. Those seem fairly well developed.

If we want to improve the <provenance> recommendations and example, we could rationalize the lists of values, which in some cases seem to repeat or have values that are not clearly differentiated. And we can recommend in more detail how to document transactional events. by marking names and roles.

[Scott DiGiulio]

@ellimylonas and I will add a sentence or two into either supp-history.xml or supp-histmodern.xml to describe the use of <custodialhist> for specific custodial events like conservation or loans at the holding institution. @paregorios, if you feel that a more detailed description needs to be added to the EpiDoc guidelines beyond what the TEI provides, please share a couple of examples with us. We did find the following (https://github.com/papyri/idp.data/blob/master/DCLP/63/62962.xml), but we'd probably only include by way of example a simplified version of what's here.</custodialhist>

[Elli Mylonas]

with @sdigiulio made change to Provenance of the Text Bearing Object and Modern and Last Known Locations to include a reference to the TEI curatorialHist element and to provide attribute values for provenance when type="transferred". Status changed to pending so it can be looked at before closing, in case it needs corrections or additions. Otherwise, it can be closed and included in the next release.

[BODARD Gabriel]

Looks great! Tweaked the speclists of both pages, and marking ticket as 'done'.