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

GBIF Clustering feature - make outcome more visible to users #5038

Open
gbif-portal opened this issue Nov 10, 2023 · 0 comments
Open

GBIF Clustering feature - make outcome more visible to users #5038

gbif-portal opened this issue Nov 10, 2023 · 0 comments
Labels

Comments

@gbif-portal
Copy link
Collaborator

gbif-portal commented Nov 10, 2023

GBIF Clustering feature - make outcome more visible to users

This is a question that was raised during the November 2023 session of the Technical support hour for Nodes (https://discourse.gbif.org/t/how-gbif-identifies-related-occurrence-records-gbif-technical-support-hour-for-nodes/4177).

What would be the best way to make users aware of related occurrences? and how can we give them access to related records so that they can make an informed decision?

Some ideas mentioned:

  • Should there be a flag to let users know that there are related records?
  • Should the related records be downloadable? (see also feedback on clusters view hosted-portals#263 (comment))
  • If so, what should be the format? a Darwin Core Relationship extension?
  • Should the associatedOccurrences field be available in the SIMPLE download format?

Note that being able to download related record would mean that they imported (or at least the relationships) into collection management systems.


Github user: @ManonGros
User: See in registry - Send email
System: Safari 17.1.0 / Mac OS X 10.15.7
Referer: https://www.gbif.org/occurrence/2557230648/cluster
Window size: width 1602 - height 929
API log
Site log
System health at time of feedback: OPERATIONAL

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants