search

srophe / britishLibrary-data

GNU General Public License v3.0
0 stars 3 forks source link

Using tei:note of type="data-model-incomplete" to indicate where transmission history too complex to fully capture #33

Open wlpotter opened 2 years ago

wlpotter commented 2 years ago

Some manuscripts and manuscript parts have transmission histories that are too complex to fully capture in our current data model. 497 is an example, Add. 14,669, foll. 1-18. Fol. 8 of this ms seems to have circulated with the other 17, been separated, and then later rejoined before finally being bound together into Add. 14,669. We don't have a way to precisely and succinctly model this complexity, so instead we will add a note of [@type="data-model-incomplete"].

This note will appear either on the tei:msDesc or tei:msPart, depending on the level at which the complexity occurs. A corresponding tei:change will be added to the additional/adminInfo/recordHist/change (see srophe/britishLibrary-data#32). The note's text node should be constructed as follows:

<note xml:lang="en" type="incomplete-data-model" resp="http://syriaca.org">Note to Readers: This manuscript has a complex transmission history. The database structure is not fully able to model that complexity in this description. [Prose note].</note>

The tei:note should also include a @corresp attribute pointing to the additional/adminInfo/recordHist/change/@xml:id of the change element of @type="data-model". The 'Prose note' should attempt to explain, concisely, the nature of the complexity.

wlpotter commented 2 years ago

@davidamichelson I believe this is ready to go and we just need to implement in our data by identifying which records need these notes.

wlpotter commented 2 years ago

Have we added this to our documentation? We should include in the manual and then also include as a documentation page (make app issue for this? also need one related to #32 and #29 I believe)

wlpotter commented 2 years ago

I believe this is going in the tei:head? So waiting on #101