Local override

[escowles]

One of the features requested by Holly was a predictable process for getting new content from partners to show up in the site. Given the irregularity of the Getty publishing, and the issues with partner metadata that sometimes prevents linking correctly, I think we should have a local override file that lets us link partner IIIF manifests to DCL numbers.

Ideally, this would be updated by Marquand staff (Airtable, Google spreadsheet, etc.) and pulled into the application by IT staff at regular intervals.

[cwulfman]

In the current workflow, we download the Getty Portal, winnow out the non-Cicognara records, and convert the remaining records to TEI documents: a TEI header with the bibliographic data + a element for the IIIF manifest. In this capacity, the TEI documents are little more than bibliographic records expressed in a well-known, well-documented, and validatable bibliographic format. Then we construct a teiCorpus for each Catalogo item, with header data coming from the Catalogo and the components coming from the Getty documents (associated via dclnum). These Item-level TEI documents are used to construct the static site and the new Fuse index.

I propose we treat these item-level components as we do the encoded Catalogo: as first-class objects, maintained under version control and curated and edited as the Catalogo is. Our staff can easily be taught to update these files to correct errors in the partner data, and new records can be appended to the Item documents when they are added to the Getty Portal (this seldom happens in practice).

[escowles]

We have decided we don't need this — adding to the Getty Research Portal and harvesting from there is a workable solution.

[cwulfman]

We should talk about this, then. The ability to edit locally was the rationale for the entire TEI apparatus beyond the Catalogo.