-
Notifications
You must be signed in to change notification settings - Fork 2
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
Display Typified Name in AVH #24
Comments
I second that. We first need to fix the typifiedName element though. At the moment what is displayed as Typified name is previousIdentifications. This is probably because the data was initially migrated from AVH 3 and the typified name is now delivered with a rather opaque ABCD URI (http://wiki.tdwg.org/twiki/bin/view/ABCD/AbcdConcept0604). I suggest deleting the field from AVH and then I can redeliver it with a proper HISPID URI (http://hiscom.chah.org.au/hispid/terms/typifiedName). |
We could try to index |
That would work for the type status facet, so that's part of a solution, but in addition to the "type status" we would also like TypifiedName indexed. There is a data management issue with TypifiedName, as what is currently in the TypifiedName field in the database is in fact previousIdentifications. |
This is mainly a data issue... DwC doesn't have a TypifiedName field... this will become more relevant when Herbaria start delivering GPI images. |
This issue was again discussed at HISCOM (2017), so have removed the low priority... Need to understand it more re: how it is delivered and where it is used... |
Just FYI, there will be a |
We would like to see Typified name indexed so it can be faceted and so people can search on it and download it.
This will be necessary in order to correctly display type information in the collections browser once type images are delivered by herbaria (first batch is due in late March 2015).
The text was updated successfully, but these errors were encountered: