ErwinKomen / RU-passim

0 stars 0 forks source link

MS export: XML-TEI #429

Closed MennaRempt closed 1 year ago

MennaRempt commented 3 years ago

Add the possibility to download manuscript descriptions in XML-TEI.

ErwinKomen commented 2 years ago

General: download options

Right now we have two download options: Excel and Json. So when we add a third option, it is time to change the download button a little bit. First doing that... ... okay, that took some time, but this is now working.

Specific: add handing of TEI

Add handling of dtype==tei in ManuscriptDownload, get_data() Add templates: tei-template.xml, tei-additional.xml, tei-msitem.xml, tei-contents.xml

TEI-P5 guidelines

See: https://msdesc.github.io/consolidated-tei-schema/msdesc.html

Questions

Not all Passim's fields are currently processed into the TEI-XML download. Some might not be included anyway. But how should the following fields be processed with regard to the TEI-P5 standard?

  1. The corresponding Passim Authority File (if linked)
  2. The Gryson/Clavis codes belonging to the corresponding Authority File. These should be coded on the level of the individual sermon, but there doesn't seem to be an identificational element at the sermon level (which is an <msItem>).
  3. Bibliography:
    1. There seems to be room at the manuscript level for bibliographic information in the <listBibl> item. Should the manuscript-level bibliographic references be processed in here?
    2. But there doesn't seem to be room at the level of the <msItem>
  4. keywords

One possibility would be to put each sermon into its own <msPart> element, but that may be too far. And using <msFrag> would also not be very much 'standard'.

ErwinKomen commented 2 years ago

Note: we will continue the discussion on this topic in 2022

MennaRempt commented 2 years ago

Suggested amendments to the XML-TEI description of MSS, to include the Gryson/Clavis codes: (NB. 'grégoire' should not be used as a label, but the labels already in use in the database for the signatures should be used, i.e. 'Gryson', 'Clavis' and 'Other code') image

MennaRempt commented 2 years ago

Comments by Iris: The solution for identification under ‘title’ (as posted in June) seems useful (AU s 202), but some questions:

image

ErwinKomen commented 1 year ago

Implementation

The relevant code is in seeker/views.py, view ManuscriptDownload (so it's not just downloading one sermon, but a manuscript consisting of a number of sermons). The XML templates is in seeker/tei-template.xml

  1. About author:
    1. The TEI P5 lists a way to deal with ascribed author: just precede the name of the author with (ascr. author name )
    2. The certainty of an author is indicated using the @cert attribute
    3. If no author is supplied, then no <author></author> XML code is added
    4. If there is an author (ascribed), then also supply the @key attribute with the Passim-internal ID of the author
  2. About title:
    1. I checked, and TEI-P5 indeed allows nesting of <title> statements
    2. Stemmatology already defines a number of title @type attributes: gryson, passim, gr, ot, cl
    3. So I added all Signatures from the equality set per sermon
  3. About rubric:
    1. that is in the tei-msitem.xml template, but it is only used when there is a subtitle field specified in the SermonDescr