Remarks meeting Nov 18 2025

[tuurma]

Irene

• UX improved
• data lens much appreciated, wishes to maybe customize
• no problem with the data model
• good to force users to use ids (Zotero, TM, EAGLE), on the other hand if the place is not in the database you cannot enter it; might be good for some workflows to just enter a note and clean it up later; torn in opinion: considers it a good practice but sometimes not fitting the realistic workflow

Pietro

• likes it a lot, could edit and import with little hindrance
• plans to use it for his upcoming project
• strange data: empty attributes, fields getting into an attribute instead of element
• confirms that text fields sometimes disappear in the display but are saved in the db
• lost non-valid epidoc

Discussion

all records are editable in the database, therefore it's not a complete blocker if an entry for people or bibliography do not exist yet

[tuurma]

Concrete issues

• invalid XML not saved, configuration should give the ability to validate against specific epidoc schema
• small screen not supported
• empty attributes on TEI @corresp, @type to be pruned on save moved to review postprocessing #56
• use XSLT from epidoc to display the diplomatic/critical preview of the transcription
• epidoc contains charDecls and metDecls to enter special characters in the editor (feature request), like digamma or various dots and metric
• hiccups between leiden+ and xml; text pasted in XML saves with a lot of extra spaces abbr/expan; D: if you edit XML it blocks Leiden; assumed workflow is start with Leiden, then add extras in XML; Irene noticed a disclaimer to that effect and understood that roundtrips are not possible

• finddate - custom date; free text ends up in when-custom - this is unclear what the free entry is for: David uses it for extra notes and remarks; Pietro assumed a human-readable form of the date; when-custom should be kept for really custom dates, e.g. Ethiopian, and a separate remarks field (note) should be added

• namespaces in editors really breaks the reading - Wolfgang already addressed it in the component
• images: Pietro uploaded a larger image and it is not displaying
• FR: upload the image in the form
• when uploading the document: what happens with the uploaded data
• chaniotis... origDate/@when doesn't display: perhaps because its -0115
• verification: respStmt; it also offers the possibility for extensions of roles

• licence and availability turned to dropdowns
• FR: language: include several languages in the template, so users only delete unnecessary ones
• add xml:lang to div in transcription, translation, ...
• div type=edition on the top when saving
• repeatable translations (with xml:lang)

• maybe move apparatus out of Edition of text? D&F wanted a compact navigation

• transmission/prev ed/... go back under Bibliography again
• preview page or panel possibly using EpiDoc XSLT
• ask for selection of files to test the import
• space preservation
• configure/disable some sections (e.g. historical significance)
• rename expand button to expand/collapse

[tuurma]

Francisca

• concerned if there are blockers to produce the HTML and PDF outputs from the data we have in the form

• incorrect dropdown options
  • decoration
• incorrect navigation order and nesting

[tuurma]

Magda

• visual grouping via section background to bibliography and findspot and finddate (tbd if we want to extend that to other groupings)
• languages checkbox changed into dropdown main/other language, not free field
• Zeitpunkt in funddatum not stored and not displayed if @when-custom is removed from the epidoc-template

• verification date not shown to edit if not present in XML
• type of inscription and material as repeatable dropdowns, not expanded checkboxes
• free form as remarks / Anmerkungen
• free form for decor: Description of decoration, Dekorbeschreibung
• in repeats add button at the bottom

[tuurma]

Feature requests

extracted from the meeting notes

NB: feature requests are to be discussed and implemented only if approved and remaining budget allows

• repeatable translations (with @xml:lang)
• upload the image from disk to the form (not in scope, EDEp cannot provide infrastructure for uploading images); discussed solution that projects upload it e.g. into their public Git repositories, where it can be served from
• include predefined languages in the template, so users only delete unnecessary ones
• add xml:lang selection to div in transcription, translation, ...
• maybe move apparatus out of Edition of text? D&F wanted a compact navigation
• disable some sections (e.g. historical significance) in the profile configuration
• preview page or panel possibly using EpiDoc XSLT
• use XSLT from epidoc to display the diplomatic/critical preview of the transcription
• use charDecls and metDecls to enhance the editor with a button/dropdown to enter special characters, e.g. like digamma or various dots or metrical categories

[tuurma]

type of inscription and material will be realized as repeats, repeating the material and objectType elements in TEI

[tuurma]