You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Gendering Maximilian: "Wie umfangreich soll das Label bei Personen sein? Wann sollen wir Namensvarianten in Klammer anführen?" => Alternative Names would usually be Naming statements.
Additionally: relationship between Factoid.label and statements could clarify this (and similar topics) in the Guidelines
The text was updated successfully, but these errors were encountered:
When creating new persons in Factoid builder, the "alternative names" should be in square brackets in the LABEL (see the Schuh example).
If using the FactoidBuilder to add a new person, it would not make sense to be able to add more Naming statements: the reason we can add one naming statement inline is because we already have the Source — it's necessarily selected already. If a naming variation has a different source, then it should be attributed to that source as a newly-created Naming statement.
If one point in a source is a list of a person's variant names, then there might be a use-case for this; but I'm hesistant about making it easier to do this, as someone is certain to use it to attribute all name-variations to a single source.
As people are extracting data from secondary literature, the use case of alternative spellings recorded in one source is likely, but I see the risk. Probably it would be a good idea to keep current setting for inline and ask people to add explicit naming statements for this use case?
(e.g. https://manmax.acdh-dev.oeaw.ac.at/manmax/factoid-builder/edit/74431)
Gendering Maximilian: "Wie umfangreich soll das Label bei Personen sein? Wann sollen wir Namensvarianten in Klammer anführen?" => Alternative Names would usually be Naming statements.
Additionally: relationship between Factoid.label and statements could clarify this (and similar topics) in the Guidelines
The text was updated successfully, but these errors were encountered: