search

TEIC / TEI

The Text Encoding Initiative Guidelines
https://www.tei-c.org
Other
282 stars 84 forks source link

Role taxonomies, better examples for respStmt #2462

Open ebeshero opened 1 year ago

ebeshero commented 1 year ago

The August 2023 TEI-L discussion (subject-line "Credit Taxonomy in teiHeader") suggests some good ways to improve our Guidelines guidance on encoding <respStmt>, providing examples of role taxonomies. Let's update the Guidelines to improve how we credit contributors with various roles on projects. Here's a refined example anonymized for general use.

ebeshero commented 1 year ago

Here's an updated version of that example, supplied by Martina Gödel:

<respStmt n="dh">
     <persName>
         <surname>Musterfrau</surname>
         <forename>Erika</forename>
         <idno type="orcid">https://orcid.org/0009-0002-4707-0404</idno>
         <affiliation>BBAW (TELOTA - The Electronic Life Of The Academy)</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/methodology/"
         from="2023-03">Datenmodellierung 
         (ODD-Entwicklung/Schemaerstellung)</resp>
     <resp ref="https://credit.niso.org/contributor-roles/data-curation/" 
          from="2023-03">Qualitätssicherung (Schematron)</resp>
</respStmt>
JanelleJenstad commented 1 year ago

Here's are some sample respStmt from Linked Early Modern Drama Online:

<respStmt>
               <resp ref="resp:aut">Author</resp>
               <persName ref="pros:SHAK1">William Shakespeare</persName>
            </respStmt>`
        `<respStmt>
               <resp ref="resp:ptr">Printer</resp>
           <persName ref="pros:PARS1">Marmaduke Parsons</persName>
            </respStmt>`
            `<respStmt>
               <resp ref="resp:bsl">Publisher and Bookseller<date when="1637"/></resp>
               <persName ref="pros:HAYE3">Laurence Hayes</persName>
            </respStmt>`
             `<respStmt>
                <resp ref="resp:edt">Transcriber</resp>
               <persName ref="pers:MASS1">NAME</persName>
            </respStmt>

They link to a responsibility taxonomy that we developed from MARC relators (LONG list follows):

<taxonomy xml:id="emdRespTaxonomy">
               <desc>
                  <term>Responsibilities</term>
                  <gloss>Responsibilities</gloss>
               </desc>

               <category xml:id="aut" corresp="marc:aut">
                  <!--Replaces @role="author"-->
                  <catDesc>
                     <term>Author</term>
                     <gloss type="marc">A person, family, or organization responsible for creating a
                        work that is primarily textual in content, regardless of media type (e.g.,
                        printed text, spoken word, electronic text, tactile text) or genre (e.g.,
                        poems, novels, screenplays, blogs). Use also for persons, etc., creating a
                        new work by paraphrasing, rewriting, or adapting works by another creator
                        such that the modification has substantially changed the nature and content
                        of the original or changed the medium of expression.</gloss>
                     <gloss type="emd">LEMDO uses the term author in two contexts: (1) to indicate
                        the author of a primary work or document (such as Hamlet), and (2) to
                        indicate the author of a secondary text (such as the Critical Introduction
                        to Hamlet, by David Bevington).</gloss>
                  </catDesc>
               </category>
               <category xml:id="aut_attrib" corresp="marc:att">
                  <!--Replaces @role="author" and @class="attributed"-->
                  <catDesc>
                     <term>Supposed Author</term>
                     <gloss type="marc">An author, artist, etc., relating him/her to a resource for
                        which there is or once was substantial authority for designating that person
                        as author, creator, etc. of the work.</gloss>
                     <gloss type="emd"/>
                  </catDesc>
               </category>
               <category xml:id="bsl" corresp="marc:bsl">
                  <!--Replaces @role="bookseller"-->
                  <catDesc>
                     <term>Bookseller</term>
                     <gloss type="marc">A person or organization who makes books and other
                        bibliographic materials available for purchase. Interest in the materials is
                        primarily lucrative.</gloss>
                     <gloss type="emd">LEMDO uses the term bookseller only in the metadata for
                        publications and copies. In cases where a publication was issued with
                        variant title pages, list all booksellers in all variant states of the title
                        page.</gloss>
                  </catDesc>
               </category>
               <category xml:id="csl" corresp="marc:csl">
                  <catDesc>
                     <term>Consultant</term>
                     <gloss type="marc">A person or organization relevant to a resource, who is
                        called upon for professional advice or services in a specialized field of
                        knowledge or training.</gloss>
                     <gloss type="emd">Consultant or Technical Advisor: A person who is called upon
                        for professional advice during the editorial and/or encoding processes. Give
                        a person a credit in the edition page if their role is more than one would
                        list in the Acknowledgements page. LEMDO uses this value for a Technical
                        Advisor who provides training, answers questions, and advises on encoding
                        matters.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt" corresp="marc:edt">
                  <!--Replaces @role="editor"-->
                  <catDesc>
                     <term>Editor</term>
                     <gloss type="marc">A person, family, or organization contributing to a resource
                        by revising or elucidating the content, e.g., adding an introduction, notes,
                        or other critical matter. An editor may also prepare a resource for
                        production, publication, or distribution. For major revisions, adaptations,
                        etc., that substantially change the nature and content of the original work,
                        resulting in a new work, see author.</gloss>
                     <gloss type="emd">LEMDO uses the general term editor only in edition metadata
                        and only to indicate when a person is responsible for editing all parts of
                        an edition. Otherwise, use the more granular terms to describe the precise
                        nature of the editorial role.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_asstcoord">
                  <!--Replaces @role="editor" and @class="assistant coordinating"-->
                  <catDesc>
                     <term>Assistant Coordinating Editor</term>
                     <gloss type="emd">The term assistant coordinating editor appears in the
                        metadata for documents produced before 2017. From 2017 on, this term is
                        reserved for project-level credits.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_assoccoord">
                  <!--Replaces @role="editor" and @class="associate coordinating"-->
                  <catDesc>
                     <term>Associate Coordinating Editor</term>
                     <gloss type="emd">Gloss needed</gloss><!-- NV: I've written "gloss needed" in all the empty glosses. -->
                  </catDesc>
               </category>
               <category xml:id="edt_assoctext">
                  <!--Replaces @role="editor" and @class="associate textual"-->
                  <catDesc>
                     <term>Associate Textual Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="cont">
                  <catDesc>
                     <term>Generic Contributor</term>
                     <gloss>DO NOT USE: This is a generic contributor for which it is impossible to
                        determine a more precise role for this person. All generic contributors
                        should be replaced by a more specific value.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_cont">
                  <!--Replaces @role="editor" and @class="contributing"-->
                  <catDesc>
                     <term>Contributing Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_coord">
                  <!--Replaces @role="editor" and @class="coordinating". A legacy term to be used only for texts first published in the ISE site on the ISE platform.-->
                  <catDesc>
                     <term>Coordinating Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_cpy">
                  <catDesc>
                     <term>Copy Editor</term>
                     <gloss type="emd">LEMDO uses the term owner for the person who checks facts,
                        quotations, and citations; may make formatting changes; may convert from one
                        citation style to another; may suggest wording changes; and enforces
                        conformity with the project style guide.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_gen">
                  <!--Replaces @role="editor" and @class="general"-->
                  <catDesc>
                     <term>General Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_gentext">
                  <!--Replaces @role="editor" and @class="general textual"-->
                  <catDesc>
                     <term>General Textual Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_genperf">
                  <catDesc>
                     <term>General Editor (Performance)</term>
                     <gloss type="emd">A person responsible for the performance strategy and methodology of a project.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_mrk" corresp="marc:mrk">
                  <!--Replaces @role="editor" and @class="markup"-->
                  <catDesc>
                     <term>Markup Editor</term>
                     <gloss type="marc">A person or organization performing the coding of SGML,
                        HTML, or XML markup of metadata, text, etc.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_perf">
                  <!--Replaces @role="editor" and @class="performance"-->
                  <catDesc>
                     <term>Performance Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_text">
                  <!--Replaces @role="editor" and @class="textual"-->
                  <catDesc>
                     <term>Textual Editor</term>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="prn" corresp="marc:prn">
                  <!-- Role added 2020-12-19 by JENS1 -->
                  <catDesc>
                     <term>Production Company</term>
                     <gloss type="marc">An organization that is responsible for financial, technical, and organizational management of a production for stage, screen, audio recording, television, webcast, etc.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="edm" corresp="marc:ptr">
                  <!-- Role added 2020-12-03 by JENS1  -->
                  <catDesc>

                     <term>Video Editor</term>
                     <gloss type="marc">A person, family, or organization responsible for assembling, arranging, and trimming film, video, or other moving image formats, including both visual and audio aspects</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>

                  <category xml:id="pbd" corresp="marc:pbd">
                     <!-- Role added 2020-12-03 by JENS1. From 2020 on, should be used instead of Coordinating Editor. -->
                     <catDesc>
                        <term>Anthology Lead</term>
                        <gloss type="marc">A person or organization who presides over the elaboration of a collective work to ensure its coherence or continuity. This includes editors-in-chief, literary editors, editors of series, etc.</gloss>
                        <gloss type="emd">A person who presides over the creation of an anthology on the LEMDO platform, a role that includes commissioning editions, approving proposals, supporting editors, arranging for peer review, and liaising with the LEMDO Platform Team.</gloss>
                     </catDesc>

                  </category>
               </category>
               <category xml:id="ptr" corresp="marc:ptr">
                  <!--Replaces @role="printer"-->
                  <catDesc>
                     <term>Printer</term>
                     <gloss type="marc">A person, family, or organization involved in manufacturing
                        a manifestation of printed text, notated music, etc., from type or plates,
                        such as a book, newspaper, magazine, broadside, score, etc.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="rtm_ra" corresp="marc:rtm">
                  <!--Replaces @role="editor" and @class="ra"-->
                  <!--Replaces @role="researchAssistant"-->
                  <catDesc>
                     <term>Editorial Research Assistant</term>
                     <gloss type="marc">A person who participated in a research project but whose
                        role did not involve direction or management of it</gloss>
                     <gloss type="emd">Legacy term. Use rtm or appropriate role from 2017
                        on.</gloss>
                  </catDesc>
               </category>
               <category xml:id="rtm" corresp="marc:rtm">
                  <catDesc>
                     <term>Research Team Member</term>
                     <gloss type="marc">A person who participated in a research project but whose
                        role did not involve direction or management of it.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>

               <category xml:id="scr" corresp="marc:scr">
                  <catDesc>
                     <term>Scribe</term>
                 <gloss type="marc">A person who is an amanuensis and for a writer of manuscripts proper.</gloss>
               <gloss type="emd">
                  Gloss needed.
               </gloss>
                  </catDesc>
               </category>

               <category xml:id="trl" corresp="marc:trl">
                  <!--Replaces @role="translator"-->
                  <catDesc>
                     <term>Translator</term>
                     <gloss type="marc">A person or organization who renders a text from one
                        language into another, or from an older form of a language into the modern
                        form.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="pdr" corresp="marc:pdr">
                  <catDesc>
                     <term>Project Director</term>
                     <gloss type="marc">A person or organization with primary responsibility for all
                        essential aspects of a project, has overall responsibility for managing
                        projects, or provides overall direction to a project manager.</gloss>
                     <gloss type="emd">LEMDO uses the term project director for the person who
                        directs the LEMDO project. For anthology leads, use pbd.</gloss>
                  </catDesc>
               </category>
               <category xml:id="drt" corresp="marc:drt">
                  <catDesc>
                     <term>Director</term>
                     <gloss type="marc">A person responsible for the general management and
                        supervision of a filmed performance, a radio or television program,
                        etc.</gloss>
                     <gloss type="emd">LEMDO uses the term <term>director</term> for the person who
                        manages or supervises a performance. We do not use it for project level
                        directors.</gloss>
                  </catDesc>
               </category>
               <category xml:id="pfr" corresp="marc:pfr">
                  <catDesc>
                     <term>Proofreader</term>
                     <gloss type="marc">A person who corrects printed matter.</gloss>
                     <gloss type="emd">LEMDO uses the term proofreader for the person who performs
                        minor corrections to a finalized document, which usually include
                        typographical or rendering fixes. For copy-editing, use
                           <soCalled>resp:edt_cpy</soCalled>.</gloss>
                  </catDesc>
               </category>
               <category xml:id="own" corresp="marc:own">
                  <catDesc>
                     <term>Owner</term>
                     <gloss type="marc">A person, family, or organization that currently owns an
                        item or collection, i.e.has legal possession of a resource.</gloss>
                     <gloss type="emd">LEMDO uses the term owner for the person, family, or library
                        that owns the physical copy of an artifact reproduced in facsimile on the
                        platform. The owner is often but not necessarily the copyright
                        holder.</gloss>
                  </catDesc>
               </category>
               <category xml:id="vet">
                  <catDesc>
                     <term>Peer Reviewer</term>
                     <gloss type="emd">LEMDO uses the term peer reviewer for a person who reviews a
                        transcription, critical materials, dataset, and/or some or all components of
                        an edition.</gloss>
                  </catDesc>
               </category>
               <category xml:id="cph" corresp="marc:cph">
                  <catDesc>
                     <term>Copyright Holder</term>
                     <gloss type="marc">A person or organization to whom copy and legal rights have
                        been granted or transferred for the intellectual content of a work. The
                        copyright holder, although not necessarily the creator of the work, usually
                        has the exclusive right to benefit financially from the sale and use of the
                        work to which the associated copyright protection applies.</gloss>
                     <gloss type="emd">Normally the editor is the copyright holder for an LEMDO
                        edition.</gloss>
                  </catDesc>
               </category>
               <category xml:id="edt_comp" corresp="marc:com">
                  <catDesc>
                     <term>Compiler</term>
                     <gloss type="marc">A person, family, or organization responsible for creating a
                        new work (e.g., a bibliography, a directory) through the act of compilation,
                        e.g., selecting, arranging, aggregating, and editing data, information,
                        etc.</gloss>
                     <gloss type="emd">LEMDO uses the term compiler for the person who chooses and
                        aggregates the resources included in an edition, if those resources are not
                        all by the editor of the edition. The compiler and the editor may be the
                        same person; in that case, the person needs two responsibility
                        statements.</gloss>
                  </catDesc>
               </category>
               <category xml:id="aut_ann" corresp="marc:cwt">
                  <catDesc>
                     <term>Author of Annotations</term>
                     <gloss type="marc">A person or organization responsible for the commentary or
                        explanatory notes about a text.</gloss>
                     <gloss type="emd">LEMDO uses the term author of annotations for a person who
                        writes annotions for a text.</gloss>
                  </catDesc>
               </category>
               <category xml:id="ann" corresp="marc:ann">
                  <catDesc>
                     <term>Annotator</term>
                     <gloss type="marc">A person who makes manuscript annotations on an
                        item.</gloss>
                  </catDesc>
               </category>
               <category xml:id="aut_col">
                  <catDesc>
                     <term>Collator</term>
                     <gloss type="emd">A person who compiles the vertical collations for a
                        text.</gloss>
                  </catDesc>
               </category>
               <category xml:id="anl" corresp="marc:anl">
                  <catDesc>
                     <term>Analyst</term>
                     <gloss type="marc">A person or organization that reviews, examines, and
                        interprets data or information in a specific area.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="prg" corresp="marc:prg">
                  <catDesc>
                     <term>Programmer</term>
                     <gloss type="marc">A person, family, or organization responsible for creating a
                        computer program.</gloss>
                     <gloss type="emd">Gloss needed</gloss>
                  </catDesc>
               </category>
               <category xml:id="trc" corresp="marc:trc">
                  <catDesc>
                     <term>Transcriber</term>
                     <gloss type="marc">A person, family, or organization contributing to a resource
                        by changing it from one system of notation to another.</gloss>
                  </catDesc>
               </category>
               <category xml:id="wtm" corresp="marc:wtm">
                  <!-- This should actually be lemdo code for now as opposed to marc. We have to write to the LoC to get them to add it. -->
                  <catDesc>
                     <term>Technical Writer</term>
                     <gloss type="marc">Writer of Technical Material: A person responsible for
                        writing or compiling documentation of the projectʼs editorial, encoding, and
                        programming practices.</gloss>
                  </catDesc>
               </category>
            </taxonomy>
Martin-de-la-Iglesia commented 1 year ago

We're going to have a meeting about this issue later this month, and then we'll hopefully be able to finalize our encoding. I'll post an example here as soon as it's ready, of course.

Martin-de-la-Iglesia commented 1 year ago

OK, here's a real-world example of our use of the CRediT taxonomy from our journal, Zeitschrift für digitale Geisteswissenschaften (https://zfdg.de/2022_008):

<respStmt>
    <persName>
        <forename>Maximilian</forename>
        <surname>Görmar</surname>
        <email>goermar@hab.de</email>
        <idno type="gnd">1077317964</idno>
        <idno type="orcid">0000-0003-3608-1140</idno>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp>
    <resp ref="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/data-curation/">Data curation</resp>
    <resp ref="https://credit.niso.org/contributor-roles/formal-analysis/">Formal analysis</resp>
    <resp ref="https://credit.niso.org/contributor-roles/investigation/">Investigation</resp>
    <resp ref="https://credit.niso.org/contributor-roles/methodology/">Methodology</resp>
    <resp ref="https://credit.niso.org/contributor-roles/resources/">Resources</resp>
    <resp ref="https://credit.niso.org/contributor-roles/visualization/">Visualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing – original draft</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing – review & editing</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Jörn</forename>
        <surname>Münkner</surname>
        <email>muenkner@hab.de</email>
        <idno type="gnd">115844031</idno>
        <idno type="orcid">0000-0003-0493-6482</idno>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp>
    <resp ref="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/investigation/">Investigation</resp>
    <resp ref="https://credit.niso.org/contributor-roles/methodology/">Methodology</resp>
    <resp ref="https://credit.niso.org/contributor-roles/project-administration/">Project administration</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing – original draft</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing – review & editing</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Hartmut</forename>
        <surname>Beyer</surname>
        <email>beyer@hab.de</email>
        <idno type="gnd">136449824</idno>
        <idno type="orcid">0000-0002-1158-1547</idno>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="http://id.loc.gov/vocabulary/relators/aut">Author</resp>
    <resp ref="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/investigation/">Investigation</resp>
    <resp ref="https://credit.niso.org/contributor-roles/methodology/">Methodology</resp>
    <resp ref="https://credit.niso.org/contributor-roles/resources/">Resources</resp>
    <resp ref="https://credit.niso.org/contributor-roles/software/">Software</resp>
    <resp ref="https://credit.niso.org/contributor-roles/visualization/">Visualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing – original draft</resp>
    <resp ref="https://credit.niso.org/contributor-roles/writing-review-editing/">Writing – review & editing</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Peter</forename>
        <surname>Burschel</surname>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/funding-acquisition/">Funding acquisition</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Ulrike</forename>
        <surname>Gleixner</surname>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/funding-acquisition/">Funding acquisition</resp>
    <resp ref="https://credit.niso.org/contributor-roles/project-administration/">Project administration</resp>
    <resp ref="https://credit.niso.org/contributor-roles/supervision/">Supervision</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Katrin</forename>
        <surname>Schmidt</surname>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</resp>
    <resp ref="https://credit.niso.org/contributor-roles/data-curation/">Data curation</resp>
    <resp ref="https://credit.niso.org/contributor-roles/investigation/">Investigation</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Rebecca</forename>
        <surname>Sperl</surname>
        <affiliation>Herzog August Bibliothek Wolfenbüttel</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/data-curation/">Data curation</resp>
</respStmt>
<respStmt>
    <persName>
        <forename>Martin</forename>
        <surname>Wiegand</surname>
        <affiliation>Forschungsverbund Marbach Weimar Wolfenbüttel</affiliation>
    </persName>
    <resp ref="https://credit.niso.org/contributor-roles/project-administration/">Project administration</resp>
</respStmt>

Note that we use the MARC relator code "aut" in addition to the CRediT roles in order to distinguish the (main) authors from other contributors.