Skip to content
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

GRSciColl - How is the description of an institution created after setting a publishing organization as its mastersource? #598

Open
spalp opened this issue Jul 17, 2024 · 1 comment
Assignees

Comments

@spalp
Copy link

spalp commented Jul 17, 2024

After adding the publisher as a master source to a GRSciColl institution, the description of the GRSciColl entry does not equal the description of the publishing organization (expected behaviour). Still, alongside the description of the organization, there is a piece of additional information (marked in yellow in the examples below).
Where does the yellow text come from? And why is it appended by two dots (..)? It looks like an aggregation of the fields 'Taxonomic coverage' and 'Geographical coverage' of the collections. If so, could the two dots be replaced by "Geographic and taxonomic coverage" (preferably separate for each piece of information) and may be moved to a new paragraph, otherwise, it looks as if something was truncated/missing. Also, looking at this description one would not know whether geological and mineralogical collections are present as they do not have taxonomic coverage....

Example 1:
https://registry.gbif.org/institution/3e2c3303-f852-4ea4-9699-2134157bf6fc
image

Example 2:
https://registry.gbif.org/institution/27bcef1d-2467-41c5-8cb6-8acd1fcc513e
image

@ManonGros

@ManonGros
Copy link
Contributor

Hi @spalp thanks for logging the issue. I suspect that this is because of the change in the schema that we implemented a few months ago. We concatenated the information from the coverage fields that we deleted.

I have saved the publisher info again and that updated the information in the institution page. Sorry for the mishap. Please let me know if you notice more of these. Thanks!

@ManonGros ManonGros self-assigned this Jul 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants