This page summarises all manual editing (currently with focus onNE204) that cannot be covered by the XSL transformation and also highlights typical pitfalls to take special care of during quality assurance.

For manual editing, all elements are listed in the order of their appearance in the TEI schema / template. Conceptualized for internal use.

Hint: If you would like to delete or replicate a line / lines, mark them at the very beginning (column 1, not the beginning of the element), and mark additional ones with CTRL+CursorDown, this will not create any damage to the indents or create blank lines in the TEI.

tei:header

tei:titleStmt

Musical Genre

              <note type="genreTranscription" xml:lang="ota">
                 <ref target="genreGlossary.xml##[xml:id]">[Enter type of genre for this piece or delete element.]</ref>
               </note>

• Replace "##[xml:id] in tei:ref@target with a correct "#xml:id" used in the glossary, e.g. "#semai". The value of @target will always fail validation if not provided correctly.
• Replace "[Enter type of genre for this piece or delete elements.]" with the musical term as it can be transcribed from the source, e.g. "Semāʿī".
• In the unlikely event that the musical genre is not applicabale or reconstructable or cannot be given for any reason, delete the entire codeblock as displayed above.

Usûl (written in source)

<note type="usulTranscription" xml:lang="ota">
   <ref target="usulGlossary.xml##[xml:id]">[Enter type of usul for this piece or delete elements.]</ref>
</note>

• Replace "##[xml:id]" in tei:ref@target with a correct "#xml:id" used in the glossary, e.g. "#cenber". The value of @target will always fail validation if not provided correctly.

Replace "[Enter type of usul for this piece or delete elements.]" with the musical term as it can be transcribed from the source, e.g. "Çenber", with the inital letter of the first word in uppercase.

• In the unlikely event that the usûl is not applicabale or reconstructable or cannot be given for any reason, delete the entire codeblock as displayed above.

Usûl (reconstructed)

<note type="usulStandardized" xml:lang="ota">
   <ref target="usulGlossary.xml#semai">
      <supplied reason="provided-by-editor" cert="1" resp="#CM">Aksak semâî</supplied>
   </ref>
</note>

• In the rare case that the usûl is not provided, but reconstructable, or wrongly attributed:
  • tei:note@type will be replaced with "usulStandardized", and
  • with tei:supplied is nested, having the following information:
    • @reason with "provided-by-editor",
    • @cert with an appropriate value, and
    • @resp will be applied with a valid "#NN".
    • Validation will fail if any of the above is not provided correctly.
    • Replace "[Enter type of usul for this piece or delete elements.]" with the standardized musical term as per the list published.

Poetic Form and Genre

<note type="poeticForm" xml:lang="ota">
    <ref target="poeticGlossary.xml##[xml:id]">
        <supplied reason="provided-by-editor" cert="1" resp="#ND">[Enter type of poetic form for this piece or delete element.]</supplied>
    </ref>
</note>
<note type="poeticGenre" xml:lang="ota">
    <ref target="poeticGlossary.xml##[xml:id]">
        <supplied reason="provided-by-editor" cert="1" resp="#ND">[Enter type of poetic genre for this piece or delete element.]</supplied>
    </ref>
</note>

• Poetic form and genre both refer to the same glossary, as they are indispensible if reconstructable and are both obsolete if unknown.
• Replace "##[xml:id]" in tei:ref@target with a correct "#xml:id" used in the glossary, e.g. "#gazel" or "#naatiserif". The value of @target will always fail validation if not provided correctly.
• A tei:supplied is nested, having the following information:
  • @reason with "provided-by-editor",
  • @cert with an appropriate value, and
  • @resp will be applied with a valid "#NN".
  • Validation will fail if any of the above is not provided correctly.
  • Replace "[Enter type of poetic form/genre for this piece or delete elements.]" with the standard poetic term as provided in the glossary within tei:orth, e.g. "Gazel" or "Naat-ı şerîf".
• In the not so unlikely event that the poetic form/genre is not applicabale or reconstructable or cannot be given for any reason, delete the entire codeblock as displayed above.

Bahir

<note type="bahir" xml:lang="ota" corresp="[#vezin@xml:id]">
   <ref target="bahirGlossary.xml##[xml:id]">
      <supplied reason="provided-by-editor" cert="1" resp="#ND">[Enter type of bahir for this piece and multiply if necessary or delete element.]</supplied>
   </ref>
 </note>

• Replace "[#vezin@xml:id]" in tei:note@corresp with the correct value of tei:metSym@xml:id from tei:met:Decl@xml:id="vezin". The value of @corresp will always fail validation if not provided correctly.
• Replace "##[xml:id]" in tei:ref@target with a correct "#xml:id" used in the glossary, e.g. "#remel". The value of @target will always fail validation if not provided correctly.
• A tei:supplied is nested, having the following information:
  • @reason with "provided-by-editor",
  • @cert with an appropriate value, and
  • @resp will be applied with a valid "#NN".
  • Validation will fail if any of the above is not provided correctly.
  • Replace "[Enter type of bahir for this piece and multiply if necessary or delete element.]" with the standard meter name as provided in the glossary within tei:orth, e.g. "Remel".
• Multiply the entire tei:note block in case a piece contains more than one type of prosodic meter.

Meter Structure

<note type="meter" xml:lang="ota" corresp="[#feet@xml:id]">
    <supplied reason="provided-by-editor" cert="1" resp="#ND">[Enter type of meter structure for this piece and multiply if necessary or delete element.]</supplied>
</note>

• Replace "[#feet@xml:id]" in tei:note@corresp with the correct values and amount needed of tei:metSym@xml:id from tei:met:Decl@xml:id="feet", e.g. "#mefulu #mefailu #mefailu #feulun". The value of @corresp will always fail validation if not provided correctly.
• A tei:supplied is nested, having the following information:
  • @reason with "provided-by-editor",
  • @cert with an appropriate value, and
  • @resp will be applied with a valid "#NN".
  • Validation will fail if any of the above is not provided correctly.
  • Replace "[Enter type of meter structure for this piece and multiply if necessary or delete element.]" with the correct meter structure as provided (either source document or tei:metDecl), e.g. "Mef’ûlü / mefâ’îlü / mefâ’îlü / fe’ûlün", with the inital letter of the first word in uppercase.

Author

<author role="" cert="[0-1]" resp="[#Initials]">[Enter name of author here and multiply if necessary or delete elements.]</author>

• There is usually at least one author who can be attributed to a piece, normally the composer, but in addition, the lyricist(s).
• For the tei:author element, provide the following information:
  • @role as either "composer" or "lyricist",
  • @cert with an appropriate value, and
  • @resp with a valid "#NN".
  • Validation will fail if any of the above is not provided correctly.
  • Replace "[Enter name of author here and multiply if necessary or delete elements.]" with the name of the person.
• If the person has already an entry in the source catalogue, do the following
  • Mark the entire name of the person and hit CTRL+E in oXygen
  • In the pop-up, type "persName" and hit ENTER.
  • In the element inserted, add a @ref attribute.
  • Copy the URL of the source catalogue entry as a value of @ref.
  • You will have code that e.g. looks like this: <author role="lyricist" cert="0.5" resp="#ND"><persName ref="https://corpus-musicae-ottomanicae.de/receive/cmo_person_00000081">Hâmî</persName></author>
• Repeat element and above steps if there is more than one author.

Editors

<editor role="">[Add additional name and role if necessary with either @corresp or @ref or delete element.]</editor>

• Delete entire element if there are no additional editors.
• Otherwise:
  • Enter appropriate value for @role.
  • This is an open list, currently with "author", "contributor", "proofreader", and "compiler" defined, but other values may be entered.
  • Replace "[Add additional name and role if necessary with either @corresp or @ref or delete element.]" with name of person.

tei:sourceDesc

Witness List

<sourceDesc>
    <listWit>
        <!-- Multiply tei:witness as often as necessary. -->
        <witness xml:id="cmo_source_########">
            <idno type="CMO">[Enter CMO identifier, if existant, or delete element.]</idno>
            <idno type="RISM">[Enter RISM identifier, if existant, or delete element.]</idno>
            <biblFull>
                <!-- Attention: This is note a complete code block, as not necessary for NE204. -->

• Please be advised that this code is not as represented in the transformed pieces of NE204, but serves as a template to indicate where immediate changes are needed. This concerns in most cases currently one tei:idno element.
• In the transformation, there is an empty tei:idno@type="RISM", (visible as <idno type="RISM"/>
• Check, if the source identified with tei:idno@type="CMO" has a RISM number already in the source catalogue (use the value of tei:witness@xml:id in the browser address line to access the source)
• If no, do nothing.
• If yes, do
  • remove the closing "/" of the empty tei:idno element to create a closing tag,
  • then write or copy and paste the RISM identifier from the source catalogue into the element.
  • You will receive code that e.g. looks like <idno type="RISM">TR-Iüne 204-2</idno>
• Repeat for all tei:idno@type="RISM" elements that occur within tei:listWit.

tei:encodingDesc

Metrical Declaration (Feet)

<metDecl xml:id="feet" corresp="#symbols" type="met">
    <metSym xml:id="fa" value="fâ’" terminal="false">-|</metSym>
    <metSym xml:id="failatu" value="fâ’ilâtü" terminal="false">-u-u|</metSym>
    <metSym xml:id="failatun" value="fâ’ilâtün" terminal="false">-u--|</metSym>
    <metSym xml:id="failun" value="fâ’ilün" terminal="false">-u-|</metSym>
    <metSym xml:id="falun" value="fâ’lün" terminal="false">--|</metSym>
    <metSym xml:id="feilatun" value="fe’ilâtün" terminal="false">uu--|</metSym>
    <metSym xml:id="feilun" value="fe’ilün" terminal="false">uu-|</metSym>
    <metSym xml:id="feul" value="fe’ûl" terminal="false">u-|</metSym>
    <metSym xml:id="feulun" value="fe’ûlün" terminal="false">u--|</metSym>
    <metSym xml:id="mefulu" value="mef’ûlü" terminal="false">--u|</metSym>
    <metSym xml:id="mefulun" value="mef’ûlün" terminal="false">---|</metSym>
    <metSym xml:id="mefailu" value="mefâ’îlü" terminal="false">u--u|</metSym>
    <metSym xml:id="mefailun1" value="mefâ’ilün" terminal="false">u-u-|</metSym>
    <metSym xml:id="mefailun2" value="mefâ’ilün" terminal="false">u---|</metSym>
    <metSym xml:id="mufteilatun" value="müfte’ilâtün" terminal="false">-uu--|</metSym>
    <metSym xml:id="mufteilun" value="müfte’ilün" terminal="false">-uu-|</metSym>
    <metSym xml:id="mustefilun" value="müstef’ilün" terminal="false">--u-|</metSym>
    <metSym xml:id="mutefailun" value="mütefâ’ilün" terminal="false">uu-u-|</metSym>
</metDecl>

• This is a complete list of all feet used in Ottoman poetry.
• Check with any source document that indicates which feet are used in the bahir (remember there can be more than one in a piece!)
• Delete the lines with the feet not used in the piece.
• Check correspondance with the tei:note@type="meter" above in the header in terms of tei:metSym@xml:id in the tei:note@corresp values.

Metrical Declaration (Bahir)

       <metDecl xml:id="meters" corresp="#symbols" type="met">
           <metSym xml:id="cedid1" value="Cedîd 1" terminal="false">uu--|uu--|u-u-|</metSym>
           <metSym xml:id="hezec1" value="Hezec 1" terminal="false">--u|u--u|u--u|u--|</metSym>
           <metSym xml:id="hezec2" value="Hezec 2" terminal="false">--u|u---|u-u|u--|</metSym>
           <metSym xml:id="hezec3" value="Hezec 3" terminal="false">--u|u-u-|u--|</metSym>
           <metSym xml:id="hezec4" value="Hezec 4" terminal="false">u---|u--|u---|u--|</metSym>
           <metSym xml:id="hezec5" value="Hezec 5" terminal="false">u---|u---|u---|u---|</metSym>
           <metSym xml:id="hezec6" value="Hezec 6" terminal="false">u---|u---|u---|u--|</metSym>
           <metSym xml:id="hezec7" value="Hezec 7" terminal="false">u---|u---|u--|</metSym>
           <metSym xml:id="hezec8" value="Hezec 8" terminal="false">u---|u---|</metSym>
           <metSym xml:id="hezecahreb1" value="Hezec (Ahreb) 1 (Rubâî Meter)" terminal="false">--u|u---|--u|u-| </metSym>
           <metSym xml:id="hezecahreb2" value="Hezec (Ahreb) 2 (Rubâî Meter)" terminal="false">--u|u--u|u--u|u-| </metSym>
           <metSym xml:id="hezecahreb3" value="Hezec (Ahreb) 3 (Rubâî Meter)" terminal="false">--u|u---|---|-| </metSym>
           <metSym xml:id="hezecahreb4" value="Hezec (Ahreb) 4 (Rubâî Meter)" terminal="false">--u|u---|u---|-| </metSym>
           <metSym xml:id="hezecahreb5" value="Hezec (Ahreb) 5 (Rubâî Meter)" terminal="false">--u|u---|u--u|u-| </metSym>
           <metSym xml:id="hezecahreb6" value="Hezec (Ahreb) 6 (Rubâî Meter)" terminal="false">--u|u---|u---|-| </metSym>
           <metSym xml:id="hezecahrem1" value="Hezec (Ahrem) 1 (Rubâî Meter)" terminal="false">---|--u|u--u|u-| </metSym>
           <metSym xml:id="hezecahrem2" value="Hezec (Ahrem) 2 (Rubâî Meter)" terminal="false">---|--u|u---|-| </metSym>
           <metSym xml:id="hezecahrem3" value="Hezec (Ahrem) 3 (Rubâî Meter)" terminal="false">---|---|--u|u-| </metSym>
           <metSym xml:id="hezecahrem4" value="Hezec (Ahrem) 4 (Rubâî Meter)" terminal="false">---|---|--u|-| </metSym>
           <metSym xml:id="kamil1" value="Kâmil 1" terminal="false">uu-u-|u--|uu-u-|u--|</metSym>
           <metSym xml:id="muzari1" value="Muzâri 1" terminal="false">--u|-u-u|u--u|-u-|</metSym>
           <metSym xml:id="muzari2" value="Muzâri 2" terminal="false">--u|-u-u|--u|-u--|</metSym>
           <metSym xml:id="muctes1" value="Müctes 1" terminal="false">u-u-|uu--|u-u-|uu-|</metSym>
           <metSym xml:id="munserih1" value="Münserih 1" terminal="false">-uu-|-u-|-uu-|-u-|</metSym>
           <metSym xml:id="munserih2" value="Münserih 2" terminal="false">-uu--|-uu--|</metSym>
           <metSym xml:id="recez1" value="Recez 1" terminal="false">-uu-|u-u-|-uu-|u-u-|</metSym>
           <metSym xml:id="recez2" value="Recez 2" terminal="false">-uu-|-uu-|-uu-|-uu-|</metSym>
           <metSym xml:id="recez3" value="Recez 3" terminal="false">--u-|--u-|--u-|--u-|</metSym>
           <metSym xml:id="remel1" value="Remel 1" terminal="false">-u--|-u--|-u--|-u-|</metSym>
           <metSym xml:id="remel2" value="Remel 2" terminal="false">uu--|uu--|uu--|uu-|</metSym>
           <metSym xml:id="remel3" value="Remel 3" terminal="false">-u--|-u--|-u--|</metSym>
           <metSym xml:id="remel4" value="Remel 4" terminal="false">-u--|-u--|-u-|</metSym>
           <metSym xml:id="remel5" value="Remel 5" terminal="false">-u--|-u--|-u--|-u--|</metSym>
           <metSym xml:id="remel6" value="Remel 6" terminal="false">uu--|uu--|uu--|uu--|</metSym>                     
           <metSym xml:id="seri1" value="Serî 1" terminal="false">-uu-|-uu-|-u-|</metSym>
       </metDecl>

• This is an incomplete list of vezin/bahir used in Ottoman poetry. The list only includes the meter patterns used in the sung poetry in CMO editions.
• Check with any source document that indicates which bahir is/are used in the piece (remember there can be more than one!)
• Delete the lines with the vezin not used in the piece.
• Check correspondance with the tei:note@type="bahir" above in the header in terms of tei:metSym@xml:id in the tei:note@corresp values.

tei:body

tei:div@type="newPieceStart"

PDF Reference

<milestone unit="cite" source="#cmo_mods_########"/>

• Replace the eight-character sequence "########" with the correct identifier that directly points to the PDF edition of the piece.
• For NE204, the overview page is https://www.corpus-musicae-ottomanicae.de/receive/cmo_mods_00000061.
• From there, click on the corresponding piece number, then on "Text Edition" and copy and paste the eight-digit identifier over the placeholder.

Locus

<locus from="‌[page]" to="‌[page]">‌p. [page number]</locus>

• The text within the tei:locus element only specifies the initial page and is replicated in @from and @ to.
• In a few cases, a piece stretches over two pages, in this case the value of @to needs to be adapted, so e.g. <locus from="1" to="2">p. 1</locus>.

Incipit

<incipit>
   <supplied reason="derived-from-lyrics" cert="1" resp="#ND">[First line of main lyrics]</supplied>
</incipit>

• Manuscript NE204 does not provide the incipit in a separate line, so it is provided with tei:supplied here.
• Replace "[First line of main lyrics]" with the text from the first line that is either
  • formatted in bold text, or
  • is marked-up with tei:seg@ana="mainPartLyrics" further down below within tei:l@n="1".
  • Alternatively use a source document that already provides the incipit.

tei:div@type="blockLyricsTranscription"

Language and Direction

<div type="blockLyricsTranscription" xml:lang="ota" style="direction:ltr;">

• Replace the value for @xml:lang with the one used for the entire lyrics, if it is different to Ottoman Turkish, other common values may be "far" for Persian, "arb" for Arabaic or "arm" for Armenian.
• If only a single line group or line of the lyrics deviate for the standard "ota", indicate that by an individual @xml:lang in the appropriate element!!!
• Retain @style for all languages that normally use or have used a right-to-left writing system, even if the text is transcribed in Latin here, otherwise delete attribute (e.g. with Armenian).

Line Group(s)

<lg n="1" decls="[#vezin@xml:id]" rhyme="">

• Replace "[#vezin@xml:id]" in tei:lg@decls with the correct value of tei:metSym@xml:id from tei:met:Decl@xml:id="vezin". The value of @decls will always fail validation if not provided correctly. NOTE: Value of @decls must be used without hashtag, e.g. decls="remel2".
• Enter the rhyme schema for the line group accordingly, e.g. rhyme="a-a-b-a".
• In case a piece consists of more than one prosodic meter, replicate the tei:lg element accordingly and increment the value of @n. Do not forget to close all elements. Terennüm lines do not receive their own tei:lg element, but are included until a new element is in use. See piece 78 as a reference.

Line Scansion

<l n="3" real="IZI-|Iu--|IZ--|-u--|">

• Each line inherits the canonical meter structure from tei:lg@decl. In case, the scansion differs in an individual line, insert @real.
• Enter the prosodic structure using the symbols defined in tei:metDecl@xml:id="symbols".
• Stick to the defined pattern, i.e. each foot must have between 1 and 5 symbols, there are between 1 and 4 feet and each feet (also the last one!) needs to be terminated with "|", otherwise validation will fail.

QA: Wrong Order within tei:l

<!-- Wrong output of transformation. -->
               <l n="3">
                  <anchor xml:id="w6180s"/> Ḥalḳa-ı <anchor xml:id="w6180e"/>
                  <seg type="vocal" ana="mainPartLyrics">
                     <anchor xml:id="w6181s"/>zülfüñ<anchor xml:id="w6181e"/> hevāsı <anchor xml:id="w6183s"/>bendeni<anchor xml:id="w6183e"/>
                     <anchor xml:id="w6184s"/>mecnūn<anchor xml:id="w6184e"/> ėder</seg>
               </l>
 
<!-- Correct order of elements. -->
               <l n="3">
                   <seg type="vocal" ana="mainPartLyrics"><anchor xml:id="w6180s"/>Ḥalḳa-ı<anchor xml:id="w6180e"/>
                     <anchor xml:id="w6181s"/>zülfüñ<anchor xml:id="w6181e"/>hevāsı<anchor xml:id="w6183s"/>bendeni<anchor xml:id="w6183e"/>
                     <anchor xml:id="w6184s"/>mecnūn<anchor xml:id="w6184e"/>ėder</seg>
               </l>

• In some instances, the XSL transformation used for NE204 casts a wrong order of elements when the first word in a line is related to the critical apparatus.
• Validation fails with the error message: element "anchor" not allowed yet; expected element "seg" or "stage".
• Usually, the tei:seg element then follows the word(s) surrounded by the opening and closing tei:anchor.
• SOLUTION: Move the tei:seg element directly following the tei:l, so that the word(s) surrounded by the two tei:anchor are within.
• Remove possible, superfluous blank spaces.

Performance Instructions

<stage type="" ana="">
   <seg type="instruction" ana="terennüm">
      <supplied reason="omitted-in-original" cert="1" resp="#ND">tem</supplied>me</seg>
</stage>

• Any performance instruction comes with an empty @type and @ana.
• Provide the values as defined in the CMO Schema, and be aware of the constraints of the values, i.e. only certain @type with certain @ana.

Lyricist (unknown)

<note type="lyricist">
   <supplied reason="provided-by-editor" cert="" resp="#ND">Lyricist: <anchor xml:id="w970s"/>Rezmî<anchor xml:id="w970e"/></supplied>
</note>

• The last element in tei:div@type="blockLyricsTranscription" is a remark on the lyricist, which is in NE204 always inferred by the editor.
• Enter the same value for @cert as in tei:author@role="lyricist" in the header.

QA: Lyricist (multi-word) Name

<!-- Wrong order. -->
            <note type="lyricist">
               <supplied reason="provided-by-editor" cert="" resp="#ND">Lyricist: Hâfız-ı <anchor xml:id="w3043s"/>Şîrâzî<anchor xml:id="w3043e"/></supplied>
            </note>
 
<!-- Correct order. -->
            <note type="lyricist">
               <supplied reason="provided-by-editor" cert="" resp="#ND"><anchor xml:id="w3043s"/>Lyricist: Hâfız-ı Şîrâzî<anchor xml:id="w3043e"/></supplied>
            </note>

• In most instances, the XML transformation used for NE204 places the starting tei:anchor to link the lyricist's name with the apparatus before or within the name, when it consists of more than one word.
• SOLUTION: Move the starting tei:anchor directly after the tei:supplied.

QA: Lyricists known, multiple

<!-- Wrong: All lyricists in one element. -->
            <note type="lyricist">
               <supplied reason="provided-by-editor" cert="" resp="#ND">[Lyricist: Emîr Hüsrev-i Dihlevî &amp; Hâfız-ı <anchor xml:id="w2239s"/>Şîrazî]<anchor xml:id="w2239e"/></supplied>
            </note>
 
<!-- Correct: All lyricists in individual elements. -->
            <note type="lyricist">
               <supplied reason="provided-by-editor" cert="1" resp="#ND"><anchor xml:id="w2239s"/>Lyricist: Emîr Hüsrev-i Dihlevî<anchor xml:id="w2239e"/></supplied>
               <supplied reason="provided-by-editor" cert="1" resp="#ND"><anchor xml:id="w2240s"/>Lyricist: Hâfız-ı Şîrazî<anchor xml:id="w2240e"/></supplied>
            </note>

• In case there is more than one lyricist, the XSL transformation of NE204 has them both in one tei:note@type="lyricist" element. NOTE: Sometimes the square brackets may still be in place, if so, delete.
• SOLUTION: Replicate the tei:supplied element.
  • Delete the second name from the first element,
  • delete the first name from the second element, and
  • eventually delete any "and", "&", or "&amp;" that used to connect the names in the text.
• Retain the opening and closing tei:anchor elements for the first name.
• Create two new tei:anchor for the second name with a unique value for @xml:id following the pattern "w[1-9]s" and "w[1-9]e".
• Split the corresponding tei:app element in tei:div@type="annotations"
  • Provide the second tei:app with @from and @to with the @xml:id values of the second tei:anchor elements.
  • Create a new tei:lem with the second name.
  • Provide the text concerning the second lyricist in its own tei:note element.
  • See the example below or piece 78 from NE204 for a structural role model.

QA: Lyricist (unknown)

<note type="lyricist">
   <supplied reason="provided-by-editor" cert="" resp="#ND">
      <supplied reason="omitted-in-original" cert="1" resp="#ND">Lyricist: unkown</supplied>
   </supplied>
</note>

• In case the lyricist is not known, the XSL transformation for NE204 provides an unvalid, double tei:supplied.
• In case of an unknown lyricist, no information on the author needs to be provided in the document.
• SOLUTION; Delete the entire tei:note@type="lyricist" element with all its children.

tei:back

tei:div@type="provenance"

Reading in Referred Source

<rdg wit="#cmo_source_00000092" type="orthographic-variant">Saḳṣonya<ref target="#cmo_source_00000092">Ha</ref></rdg>

• Each tei:rdg element can be enhanced with a @type attribute which specifies what kind of reading is attested in the referred sources. The value of @type will always fail validation if not provided correctly.

QA: Split Different Witnesses

<!-- Correct: One reading variant in one or more sources in one element. -->
            <app from="#w28s" to="#w28e">
               <lem>ṣürāḥīyle</lem>
               <rdg wit="#cmo_source_00000030 #cmo_source_00000091" type="misspelled">sürāhiyle <ref target="#cmo_source_00000030">NE204</ref>, <ref target="#cmo_source_00000091">NE3466</ref>
               </rdg>
            </app>
 
<!-- Wrong: All different readings in one element. -->
            <app from="#w15s" to="#w15e">
               <lem>reftār u ẓarāfet</lem>
               <rdg wit="#cmo_source_00000091 #cmo_source_00000092">reftār-ı ẓarāfet<ref target="#cmo_source_00000091">NE3466</ref>; reftār ol nezāket<ref target="#cmo_source_00000092">Ha</ref></rdg>
            </app>
 
<!-- Correct: Different readings in individual elements. -->
            <app from="#w15s" to="#w15e">
               <lem>reftār u ẓarāfet</lem>
               <rdg wit="#cmo_source_00000091" type="variant-reading">reftār-ı ẓarāfet <ref target="#cmo_source_00000091">NE3466</ref></rdg>
               <rdg wit="#cmo_source_00000092" type="variant-reading">reftār ol nezāket <ref target="#cmo_source_00000092">Ha</ref></rdg>
            </app>

• In the XSL transformation, all readings and a reference to their source are placed in one tei:rdg element, with all sources combined as values of @wit, while the sources are referred to individually with the value of their respective @target attribute.
• This is of no concern, when only one different reading is attested in one or more sources, see the first example with "ṣürāḥīyle".
• If there is more than one reading in different sources, the tei:rdg element needs to be split in a way that every reading has its own tei:rdg element, because:
  • this secures a 1:1 relationship of the reference values in @wit and @target, and
  • each reading attested may have a different tei:rdg@type.

tei:div@type="annotations"

QA: Split Lyricist Note

<!-- Original rendition with two lyricists in one note. -->
            <app from="#w2239s" to="#w2239e">
               <lem>Lyricist Emîr Hüsrev-i Dihlevî & Hâfız-ı Şîrazî</lem>
               <note>The first distich and miyânhâne are first and fourth distiches of a nine-couplet gazel (no. 84) by Emîr Hüsrev-i Dihlevî (d. 1325). This is the Turkish pronounciation of his name, which can also be transcribed as Amîr Kosrow Dehlavî following Encyclopaedia Iranica (Schimmel 2011). The last distich is the last couplet of a eight-couplet gazel (no. 2) by Hâfız-ı Şîrazî (d. 1390?); see Emîr Hüsrev-i Dihlevî [n.d.] and Hâfız-ı Şîrâzî 1983, 20.</note>
            </app>
 
<!-- Corrected rendtion with two notes. -->
            <app from="#w2239s" to="#w2239e">
               <lem>Lyricist Emîr Hüsrev-i Dihlevî</lem>
               <note>The first distich and miyânhâne are first and fourth distiches of a nine-couplet gazel (no. 84) by Emîr Hüsrev-i Dihlevî (d. 1325). This is the Turkish pronounciation of his name, which can also be transcribed as Amîr Kosrow Dehlavî following Encyclopaedia Iranica (Schimmel 2011).</note>
            </app>
            <app from="#w2240s" to="#w2240e">
               <lem>Lyricist Hâfız-ı Şîrazî</lem>
               <note>The last distich of the lyrics is the last couplet of a eight-couplet gazel (no. 2) by Hâfız-ı Şîrazî (d. 1390?); see Emîr Hüsrev-i Dihlevî [n.d.] and Hâfız-ı Şîrâzî 1983, 20.</note>
            </app>

• With each lyricist having an individual tei:note element (see above), it becomes necessary to also split the note
• This is a structural example and the way the note will be split depends on the text.
• Also see piece 78 from NE204 as a role model.

Citing Secondary Sources

<app from="#w47s" to="#w47e">
   <lem>Lyricist Hâmî</lem>
   <note>The lyrics are by a poet with the pen name (mahlas) Hâmî, indicated in the last
      line of the lyrics. It is possible that the poet is in fact Hâmî Ahmed Âmidî (d.
      1747), though the editors could not locate the lyrics in his dîvân; see <ref
         target="https://www.zotero.org/neslihandemirkol/items/Q2HCUPQQ">Hâmî Ahmed Âmidî 1885</ref>
      and <ref
         target="https://www.zotero.org/neslihandemirkol/items/7UDKRYQU">Yılmaz 2017</ref>. <ref
         target="https://www.zotero.org/neslihandemirkol/items/XHEPKTYF">Öztuna (2006, vol. 1, 426)</ref>
      and <ref
         target="https://www.zotero.org/neslihandemirkol/items/F58H6YW9">Aksüt (1983, vol. 1, 148)</ref>
      attribute the lyrics to Mehmed Kâmî Efendi (d. 1724). However, the editors could not
      locate the poem in his dîvân either; see <ref
         target="https://www.zotero.org/neslihandemirkol/items/2LYLMGGG">Erişen Yazıcı 2017</ref>
      and <ref
         target="https://www.zotero.org/neslihandemirkol/items/IWPP8RKS">Özyılmaz 1994</ref>.
   </note>
</app>

• The critical apparatus in tei:div@type="annotations" may cite information from secondary sources, which are given as in-text citations.
• The bibliography will be provided as external references in Zotero.
• To link a citation:
  • Mark the citation (author, year, page number)
  • Press CTRL+E in oXygen
  • In the pop-up, type "ref" and hit ENTER.
  • In the element inserted, add a @target attribute.
  • Copy the URL of the source catalogue entry as a value of @target.
  • Ensure that the URL is of the format "https://www.zotero.org/USER/items/########", where "########" is the persistent identifier of the reference.
  • All other formats of URL that Zotero might produce are functionable at this point of time, but are not stable!