Annotation profile evolution (wish list)

[daliboris]

This is the list of features we would like to see in the annotation profile. Please use comments to add your own ideas on how to improve the current state of annotation editing.

[daliboris]

Allow annotate the text with glosses

Glosses are defined in the list. An skeleton:

<standOff>
  <list type="glossary">
    <item xml:id="">
      <label type="main"></label>
      <label type="variant"></label>
      <gloss xml:lang="cs"></desc>
      <gloss xml:lang="en"></desc>
      <note></note>
    </item>
  </list>
</standOff>

[daliboris]

Search for the text to be annotated in the source XML

This is useful if the text is in a flexi-rich language such as Latin, Polish or Czech. If the XML contains a lemma, it's easy to annotate all occurrences with different forms but with the same lemma. In the current implementation, all occurrences are found based on the similarity of the selected text (or the added alternative forms).

[daliboris]

Show the content of the indexes

• show the content of separate indexes, like places, persons etc.
• allow user to search and browse them
• allow edit items from the page with index content (not only from the text itself)

Note: if the index is part of the <standOff> element, the usual browsing fails because there are no <pb> or <div> elements.

[ogierMontanus]

Handle tags
In the current (e.g. TP9) certain tags seem to confuse the annotate and cause it to miss the text fragment selected by the user. Nadine might be able to specify the technical causes.
An example: I have experienced recurring issues with and elements. When I select the text fragment "Sveas" the string is, at first, marked up correctly (as placeName). When saving the tag moves to the fragment "Fossen". The URL is
https://hcams.andersen.sdu.dk/exist/apps/svNames7/9de-mai-1861.xml?view=div&odd=annotations

[daliboris]

Allow localization of the annotation forms

Use <pb-i18n /> elements or @data-i18 for labels, messages and other UI elements.

An example:

<h1><pb-i18n key="annotations.gloss.header">Gloss</pb-i18n> <span class="annotations head">{instance('default')/*[1]}</span></h1>
<fx-confirm message="Close this editor?" data-i18n="[message]annotations.fore.close-the-editor">
  <fx-dispatch name="hide-authority" target="#document"></fx-dispatch>
</fx-confirm>

[daliboris]

Allow assigning @xml:id to an item when it is created

• user should be able assing @xml:id when creating new item (person, place etc.)
• if no @xml:id is provided by the user, one will be automatically generated (as in the current implementation)
• after saving, @xml:id cannot be changed

[nquenouille]

Toggle between Bottom and Side View in Annotation Tool

Currently, TP 9 has its view of transcription (HTML) etc. (e.g. the preview panel) at the bottom of the page. There is not enough space for scrolling or enlarging the window of this view. As with switching between displaying and not displaying, it should be possible to toggle between showing the window on the side or at the bottom - depending on the user's needs.

[nquenouille]

Insert Facsimile into the Preview Panel

It would be helpful to insert the facsimile into the preview panel, so users could check on it during annotation (useful for annotating gaps, additions, deletions, etc.).

[daliboris]

Allow document centric registers

The current registry implementation uses shared data for all documents (in the collection) that use registry records.

Sometimes we need metadata, that are related only to one document, for example critical apparatus. If the apparatus is attached via Double End-Point method, it can be created, edited and deleted like other registry entries.

The implementation can use new parameter (for example $souce containing file name) for this kind of entities that is sent with post and get requests.

One example is an application for Theatrum Neolatinum with critical apparatus stored in, for instance rochotius-comoedia.apparatus.xml file, that looks like following:

<list xmlns="http://www.tei-c.org/ns/1.0" xml:id="rochotius-comoedia.apparatus" type="apparatus">
  <item source="rochotius-comoedia.text.xml" xml:id="rochotius-comoedia.app.000001">
     <app from="#rochotius-comoedia.app.000001.start" n="1">
       <note>
         <cit>
           <quote>Salvere jubeo spectatores optumos</quote>
              <bibl>
                 <author>Plautus</author>, <title>Casina</title>, <biblScope>v. 1</biblScope>.</bibl>
                    <ref target="https://www.lateinlex.de/?call=Puc&amp;permalink=Plaut_Cas_Prologus">https://www.lateinlex.de/?call=Puc&amp;permalink=Plaut_Cas_Prologus</ref>
            </cit>
         </note>
     </app>
 </item>
</list>

The above item used in the main text:

<anchor type="delimiter" subtype="quote-start" n="1" xml:id="rochotius-comoedia.app.000001.start"/>
Salvere jubeo spectatores optumos
<anchor synch="#rochotius-comoedia.app.000001" subtype="quote-end" xml:id="rochotius-comoedia.app.000001.anch" type="delimiter" n="1"/>

Note: rochotius-comoedia.text.xml is the name of the file with main text, i.e. with <text>/<body> elements.