Please constrain based on https://bl.syriac.uk/documentation/author-editor-roles.xml

[davidamichelson]

@wlpotter Should https://syriaca.org/documentation/author-editor-roles.xml be updated to https://bl.syriac.uk/documentation/author-editor-roles.xml?

[davidamichelson]

Move for now, but later integrate into Syriaca.org taxonomy

[davidamichelson]

@dlschwartz this will be for msItem/editor/@role

[wlpotter]

Also for /msItem/author/@role -- for attributed, claimed, disputed, etc.

[davidamichelson]

@dlschwartz The file is created, so please do constrain the attribute values for msItem/editor/@role and /msItem/author/@role

@wlpotter We have some clean up to do, we have both editor and author with @ROLE translator, also translator is not using an xml:id ref back to this document but it could. Thoughts?

[wlpotter]

The authors with translator role is a mistake I think I made when doing the author and persName normalization. I can switch those back.

They aren't currently pointing to that doc, but we can update them to. I think we were using this as a label for translators in the app so we'll want an issue for changing how those display

[dlschwartz]

This URL doesn't resolve to HTML. Also, I would like to validate against a GitHub raw file.

[davidamichelson]

@dlschwartz here is your file: https://github.com/srophe/britishLibrary/blob/main/documentation/author-editor-roles.xml

[dlschwartz]

@davidamichelson Yesterday we said the following
//tei:msItem/tei:editor/@role = "translator"
//tei:titleStmt/tei:editor/@role = either "creator", "general-editor", "technical-editor"

Do we want to keep any of this?

[wlpotter]

The "creator", "general-editor" and "technical-editor" are all for titleStmt and seriesStmt, so we likely want to allow in the schema. Do we want a schematron rule to further constrain what is allowed in the msItem/editor and msItem/author contexts?

I did notice that we have general and creator in the author-editor-roles.xml file:

• Creator
• General

[dlschwartz]

This issue initially suggested I should allow any values in the editors/author site list. I've implemented that for msItem/author/@ROLE. If we further marked up the editors file to indicate certain roles for editors and other roles for authors, I could use that to allow only certain values in certain contexts. Otherwise, I can just hard code the values for the different contexts directly in the ODD without pointing out to the editors file.

[wlpotter]

The values for creator, general, and translator are all sub-categories of the category for "editor", so we could say that there are roles available for authors and editors, which come from: /TEI/teiHeader/encodingDesc/classDecl/taxonomy/category[@xml:id="claimed"]//category/@xml:id (this gives us attributed, disputed, pseudo, etc.).

There are then the editor-specific ones that come from /TEI/teiHeader/encodingDesc/classDecl/taxonomy/category[@xml:id="editor"]//category/@xml:id for general, creator, translator.

This might be worth discussing more though