Skip to content

Sources view#598

Draft
SteffenAstheimer wants to merge 29 commits into
developfrom
sources-view
Draft

Sources view#598
SteffenAstheimer wants to merge 29 commits into
developfrom
sources-view

Conversation

@SteffenAstheimer

@SteffenAstheimer SteffenAstheimer commented Feb 9, 2026

Copy link
Copy Markdown
Contributor

To-Do:

  • apparatus

    • TEI
      • fileDesc
        • titleStmt –> <title level="a"> builds the html header
        • publicationStmt –> irrelevant
        • notesStmt
          • relatedItem/@target –> processed to "Verknüpfte Dokumente" with title and link to the work
          • note/@type="editorial" -> bunch of list elements with <head> elements as "Kurzbeschreibung" and "Nachweise" – data model is not quite systematical imo and the layout is in need of improvement (header sizes)
        • sourceDesc
          • msIdentifier –> processed to text witnesses with signature and fold-out source description – seems to be fully functional
          • biblStruct –> needs improvement; we have mainly imprint elements and need to read the publishers; often note with price -> currently processed as annotation
      • profileDesc
        • textClass –> bunch of classifications; unsure if meant as filter options or to be processed as output
        • handNotes –> no processing currently
    • MEI
      • identifier
        • @type="WeGA" –> processed to "Verknüpfte Dokumente" same as tei:notesStmt/relatedItem
        • @type="JV" –> not processing currently – needs to be reworked in the data – 396 cases
      • titleStmt
        • title –> builds the html header
        • title/@type="sub" –> no processing currently – often subtitles like "Klavierauszug ohne Text"
        • respStmt –> no processing currently – lists of authors, composers, librettists etc.
      • physDesc –> no processing currently, bunch of descriptions with titlePage, watermark, physMedium, handList, extent, dimensions, condition, plateNum
      • notesStmt –> bunch of additional information classified by @type (eg.: "Anmerkung", "Literatur", "Kurzbeschreibung")
      • classification –> has to be processed like tei:textClass
      • itemList –> ... no clue about this. Contains information about history/provenance and physLoc. But there is a sibling element history.
      • creation
      • history
      • pubStmt
      • relationListcontains relation/@target; has to be processed like identifier
      • langUsage
      • seriesStmt
      • componentList
      • editionStmt
  • text – layout

    • general text distribution and layouting
      • display text as centered columns, similar to printed libretti 2b9b5bd (transformation and basic styling), a289e80 (more styling), 2965e64 (indenting for lg and verseLine), d39021e (placement for '-M' and '-F' blocks), 416cb6d (indenting exceptions)
      • visualize page breaks breaks and page numbers f0c12c8
      • make inline rendering work for block level elements
        • works for: speaker–stage, l–stage
        • doesn't work for: head–stage, speaker–caption, sp–stage, sp–addSpan, anchor–addSpan, caption–stage
      • mobile layout
      • justification not working in scenarium after pb in p (A225861)
    • braces and other graphical elements
      • draw role braces for castGroup (eg. A227656, page 2, "ein Brautpaar") bac9179
        • breaks in A227659 where the names of the singers are meant to be in a fourth column 9051093
      • draw braces and margin text for things like "{ zugleich" (eg. A227656, page 9) cd44f3f
        • breaks on page 25r in A225857 – possibly because of <pb>
      • include <actor> in schema and allow for leader dots to be displayed 9051093
    • deletions and additions
      • display hand for add and subst–> eg. "Ersetzung von…" 86e3c96 (this can only count as a rough first step – this commit introduces main and further hands in the apparatus and assigns the individual additions etc. to each hand; furthermore the hand label is output in the popup of the text constitution)
      • how to deal with nested add and del elements?
      • element damage is not displayed (twice in A225860, should be as in A042305)
      • allow del/@rend="converted" 9d53f53
      • how to display delSpan and addSpan?

        Zu den delSpan/AddSpan-Geschichten habe ich eine Idee: Bei den normalen subst/del/add-Elementen kommt ja ein Fenster mit dem entsprechenden Sachverhalt. Das ist für großflächige Streichungen sicher keine Lösung. Wäre es möglich, dass wir das einfach so machen, dass wir jeweils am Beginn und am Ende einer Streichung nur einen Hinweis geben, den Text aber nicht streichen? Es würde doch auch verständlich, wenn der gestrichene Text hellgrau angezeigt würde. Die Hinweise können wir mittels unserer herkömmlichen Textkonstitutionszeichen vornehmen, und wenn das Fenster aufgeht, steht da "Text gestrichen – Anfang" o.ä., am Ende "Text gestrichen – Ende". Bei einem anschließenden AddSpan könnte man wieder genauso Anfang und Ende markieren, der Text müsste aber normal grau bleiben. Oder man markiert nur jeweils den Anfang der del/addSpans und im Fenster steht dann ein Zitat des letzten Textes vorm jeweiligen anchor-Element. Das wäre dann unserer sonstigen Praxis ähnlicher.
        Zweites Problem dabei ist, was passiert mit delSpan/addSpan, wenn man unter den Einstellungen den Knopf für Textkonstitutionen abwählt? Ideal wäre es, wenn dann alles innerhalb des DelSpan ausgeblendet wird und alles innerhalb AddSpan stehen bleibt. Es kommt vor, dass ein del/addSpan über einen Seitenumbruch geht. Wäre es rein theoretisch möglich, dass die Seitenumbrüche trotzdem angezeigt bleiben? Evtl. kommt es auch mal vor, dass eine großflächige Streichung über einen Szenenwechsel reicht, da müssen wir dann mal schauen, ob die bisherige Codierung gut ist oder evtl. noch angepasst werden muss.
        Ganz gut ausprobieren könnte man das mal an A225860, da gibt es nur jeweils drei delSpans/addSpans.

    • further bugs
      • in A225860 a stage is prohibited by the schema right before the recurring second scene (in A227656 there is a stage right before a scene.
      • in A225876 there is a missing padding between two verses, possibly due to the delSpan and anchor inbetween
  • functionality

    • links to other WeGA entities not working (eg. A224044, A224045, A225872 –> references in source description)
      2603fc5 (not working?)
    • links to thematic commentaries not working – also thematic commentary should be listed in sidebar
    • default to editorial as active pane if no transcription is available (-> needs to update expected results) 7ecc329
    • table of content – currently roughly working, needs heavy refactoring
      • roughly working proof of concept cbe5427 and 3729560
      • include all heads of libretti
      • use random anchor id's to avoid duplicate names
      • achieve proper nesting
      • refactor function for TOCs so it can be called for guidelines and sources (currently two duplicate functions)

to prevent an error if not `@type` is set for `notesStmt/relatedItem`.
This only prevents an error – for the view of sources we should still either add types or overhaul the whole context section
accept the key from `mei:manifestation/mei:identifier[@type='WeGA']` to derive the related wega work. There isn't any equivalent for the related item type though, so that remains is a placeholder for now.
@SteffenAstheimer SteffenAstheimer self-assigned this Feb 9, 2026
depending on the presence of a transcription
logical overhaul for grid and indenting of libretti
refactor scss to be compact and understandable
more inline adjustments
add xslt templates for source-relevant attributes
- call app:prepare-text() earlier to make the transformed transcription available for querying from the sidebar
- rewrite the tei:head transformation to include all heads and give them unique anchors and correct nesting
- rewrite app:doc-toc() to create toc-items from the already transformed html tree
- regularized page width
- indenting for various elements up to indent-5
- paragraphs by default justified
- new logic to differentiate between pages and leafs in breaks
- fixed lineGroup bracketing
- whitespace between two following `<subst>` elements
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant