Adding and Encoding New Contributors - LiteratureInContext/LiC-data GitHub Wiki
Each contributor who has completed the contributor release form is given a unique two-to-three-letter identifier, which will be defined and stored in the file editors.xml (https://github.com/LiteratureInContext/LiC-data/blob/development/contributors/editors.xml). Be sure this identifier is unique; two contributors cannot have the same identifier.
In editors.xml, a new contributor is encoded as follows:
<person xml:id="AA">
<persName xml:lang="en">
<forename>Allaa</forename>
<surname>Abdelaziz</surname>
</persName>
<affiliation>Marymount University</affiliation>
</person>
In the element, use the @xml:id attribute to assign the unique identifier. In the case above, the unique identifier AA is for this student, Allaa, who has filled out a FERPA release. Include the persName, forename, surname, and affiliation elements in the broader element.
When a student has completed the contributor release form so as to be credited for their participation in the project, the digital edition will include the shorthand editors.xml#AA to indicate that contributor’s identity. This information may be in the TEI Header, but it can also be attached to specific annotations.
For broad participation, responsibility statements in the TEI header are added in the element as follows:
<respStmt>
<resp>Transcription, correction, editorial commentary, and markup</resp>
<name ref="editors.xml#MUstudstaff">Students and Staff of Marymount
University</name>
<name ref="editors.xml#FB">Felix Baquedano</name>
[…]
</respStmt>
Note that the initial element in the Header must include both a statement of responsibility, and each named contributor. You may include multiple s and s.
Student contributions that take the form of annotations are credited in the element, as follows:
<note type="editorial" xml:id="schools" target="schools_" resp="editors.xml#FB"> […] </note>
Note that here, the responsibility is indicated with the attribute @resp, instead of the element , which is used elsewhere. See the P5 Guidelines for more information. See also the documentation on encoding annotations.