teiHeader, etc. for BL records

[wlpotter]

I'm going to spin these out into different sub-tickets for components of the teiHeader

• Update tei:titleStmt in all records #1933 (titleStmt)
• editionStmt (fine as-is, as it will be the first edition once published)
• revise publicationStmt #1942
• Add a seriesStmt for SMBL #1931
• revise encodingDesc #1943
• revise profileDesc #1944
• mark all records as published in revisionDesc/@status #1945

---

OLD NOTES
A few notes to discuss regarding the distinction between this repo and the manuscript records that will be on the main Syriaca union catalog:

• will we need to adapt the teiHeader info (titleStmt, seriesStmt, etc.) for the BL catalogue db? Will the URIs need to change, both for the ms and for the editors, etc.?
• will we need to have some way of linking to the Syriaca ms URI (a skos:SameAs somewhere, maybe a second idno in the msIdentifier?)
• we will need to retain the teiHeader info, or portions of it, for the Syriaca ms record. We should discuss how this will look at some point, as well as what sorts of data we will include for non-BL projects (e.g., how we give credit when ingesting from e-ktobe or HMML or Sinai)
• we will need to decide how the Syriaca mss LOD record will look from a back-end data perspective. And also work out methods for data ingestion from these projects. I'd imagine we'd want the shelf mark and other ids, a very simple physical desc paragraph; a summary of the contents; any important date or provenance info; and any kind of relations between this and other codicological units. The HTML view should not be more than a page on an average desktop screen, with the link to the full catalogue being prominent

[wlpotter]

@davidamichelson this is quite a general issue...I think the main thing to discuss here are changes to the titleStmt and seriesStmt now that we've split this off as a separate publication from the Syriaca ms module.

The question of URIs is addressed in #17 (though see [this comment[(https://github.com//issues/21#issuecomment-1139710466)).

Other aspects of this issue that concern Syriaca's linked data mss module are important but should be moved to an issue in the app-data repo.

[wlpotter]

Draft up a draft of the teiHeader for the BL-specific files to discuss

[wlpotter]

I've created a draft in this gist: https://gist.github.com/wlpotter/e07a8ecbc7d77e06b1fca1e0e67b39bf

I think the main questions I have

• do we have an m-level title or do we move to a seriesStmt? Will The Digital Wright ultimately be one volume in the series of publications of Syriac manuscripts in the BL?
• Are these the correct funders, etc.?
• Include tei:principal? Syriaca projects have been moving away from this, but the BL data is stand-alone
• Double check that this is the right list of editors (should I be on this list?). We will want to move general editor(s) to a seriesStmt if we have one
  • add technical editors?
• Who is the publicationStmt/authority? Is it closely-enough related to Syriaca.org?
• I just copied over the 3.0 CC license, but we can update to 4.0 if we'd like
• Do we need to include info about Wright's catalogue in the publicationStmt? (In SBD, I think, we mention sources but that may only be because they are not public domain?)
• We should probably make a separate issue for revising the editorialDecl. We'd likely want to include here things like pointing to our list of changes described in Using additional/adminInfo/recordHist/change with controlled vocabulary to track adaptations of Wright #32. Maybe our use of tei:head for defining palimpsest types, Perhaps use a tei:head to give typing for the msParts #18, and so on.
• Revise and finalize list of languages allowed and extant in manuscript data #26 is for revising the list of languages which will go in the profileDesc
• I think, according to Move encoding of Wright taxonomy keywords to a tei:head/tei:listRelation/tei:relation element #22, we will get rid of //textClass entirely in favor of a tei:head/tei:list?

[wlpotter]

@davidamichelson can you post a link to the updated Gist?