-
Notifications
You must be signed in to change notification settings - Fork 7
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
Adding publication types "Statistics" and "Standards" #531
Comments
We already have |
Deployed to test, see HT018722247 (json) (publication type "Statistic") and HT019072754 (publication type "Standard" which wasn't included in the set of example resources). |
HT018722247: Changed resource to statistic (MAB 051). HT019072754: Changed resource to norm (MAB 051). No resources yet in collection which is typed "standard". Also sorted context and morph a bit. See #531
HT018722247: Changed resource to statistic (MAB 051). HT001039253: No resources yet in collection which is typed "standard". Also sorted context and morph a bit. See #531
Updated to include HT001039253 (json) instead of HT019072754. HT019072754 was a resource by the customer but didn't include |
As discussed offline, we will use the plural "Statistics". Otherwise, +1. |
HT018722247: Changed resource to statistic (MAB 051). HT001039253: No resources yet in collection which is typed "standard". Also sorted context and morph a bit. See #531
HT018722247: Changed resource to statistic (MAB 051). HT001039253: No resources yet in collection which is typed "standard". Also sorted context and morph a bit. See #531
HT018722247: Changed resource to statistic (MAB 051). HT001039253: No resources yet in collection which is typed "standard". Also sorted context and morph a bit. See #531
…hbz/lobid-resources Resolves #531. Conflicts: src/main/resources/morph-hbz01-to-lobid.xml src/test/resources/hbz01XmlClobs.tar.bz2
An edoweb customer wants the publication types "Statistics" and "Standards". From the Jira ticket:
I have to think / read about the most precise English term. Of course we should type resources with other "Erscheinungsformen" also as the same type.
The text was updated successfully, but these errors were encountered: