Open eu-genia opened 5 months ago
I think, in a manuscript record, the names should be given exactly as it is discernible from the manuscript text. Alternative names as for instance regularized or standardized forms should be possible to get by clicking on the word or on a box next to it or by scrolling over this word. Transliterated forms should not appear in fidal-text.
Carsten, the issue is for naming and nesting of the div
in edition (xml:id
and n
attributes) and how to print them
At the moment the
type
andsubtype
anddiv
number
are printed as a string without breaks, followed if available bycorresp
as linke.g.
DW03
https://betamasaheft.eu/manuscripts/DW03/text:I think that in such cases we must be very consistent with numbering, nesting, and names
That is, if we introduce a
div
withxml:id="Maskaram" type="textpart" subtype="month"
then we also need adiv
withxml:id="Teqemt" type="textpart" subtype="month"
etc, if we have inside of a month adiv
with subtypeday
for "1 Maskaram", we should also have it for "12 Maskaram", etc, and inside of theday
we nest singlecommemoration
s - or we just go for commemorations but then have no days.I am also not sure that the way it is currently displayed is the best one, I do not think a user would undersand what all those
mean.
And the way the links to msItems resolved from
corresp
are displayed could also be optimized (I was thinking of not printing the label of the msItem at all, but simply have a link name (e.g. "see item **"), same for all, this requires less space and less transformation so actually saves time).Now that @HelenaSabel is working on text display (thank you Helena!) we probably should provide precise indications on what we want to see.
@thea-m @CarstenHoffmannMarburg @DenisNosnitsin1970
(@thea-m in this example I think the word "Isaiah" should not be there as the tag content?)