-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correction proposals for places in HGV - 1 #401
Comments
I typically leave decisions about HGV to James, but I would respond to these items as follows:
Please prepare these items as separate commits, which will make them easier to untangle in the future (if necessary). |
Thank you for your reply @samosafuz ! I wanted to flag these as I noticed the discrepancies in the XML code, but I don't know when I can look at it, apart for point 5 that is easy enough to implement, and points 2 and 3 as well. I can certainly provide lists of TM numbers for the more thorny issues, if you would like to look at them too. |
As I am working closely with places for a small project, I'm noticing some possible corrections in the HGV metadata.
I'll open issues as I go along with proposals for corrections. Some seem straightforward, like the first suggestion below, but for others I am not sure what the best course of action is.
<provenance>
but it can be added from the origPlace which is not "unbekannt" (e.g. TM 79319)@type
: should the type 'located' be added?<p>
elements inside. But there are also 7 documents with two 'located' provenance, and 1 with two 'sent' provenance. I am not sure if both encoding are valid, or if the first one is preferable.The text was updated successfully, but these errors were encountered: