Help extracting occurrence IDs on the Data page

[mbelisle]

From hp-canadian-biodiversity #16

I have been experimenting with the Data page in order to make accessible the occurrence IDs associated with the current filters without having the download the results. I have added two buttons - one to copy the IDs to the clipboard, the other to include them in an email. This would be for the eventual ability to seamlessly send specimen requests to our in-house collections.

My current strategy is to translate the filter in the URL to an API request and obtain the results that way. I worry about using this strategy because:

• Some of the filters don't have an exact equivalent in the occurrence API (e.g. "notIssue")
• Translating each possible type of filter to its API equivalent seems like a duplication of work and would be error prone.

Would anyone have a suggestion for a better strategy? I'm thinking that making a graphql request might make more sense, but I'm not sure.

• Code mostly resides here
• See this search as example of current behaviour.

Comments, suggestions welcome!

[MortenHofft]

@langeveldNMR and @jholetschek you might have an interest/opinion in this?

I'm not thinking about the technical solution just yet, I'm mostly interested in gauging the interest and scope.

As I understand it, the desire is to have an easier way for users to request access to specimens using the hosted portal.

So the question I'm curious to answer is:

• Is there a broader interest in mediating loan/access requests through the hosted portals?
• If so where does those requests go? @mbelisle mentions email. Are there other places/examples of where this information should go to?
• In above example the access request is scoped by a search result, but what other ways should the users should be able to do this? For example sending a mail from an individual specimen, or having the option to put individual specimens in a "checkout cart"?

[jholetschek]

Hi Mélianie, Morten,

for the German VH herbarium, I think there is no real need so far for such a feature (yet). My two cents on the topic:

• The emails should go to the content contact of the dataset - so in most cases, it would be several mails.
• For the European specimen collections, DiSSCo is working on a loan system (ELViS). I think it's still in an early phase, and probably it will be something tht GBIF will need to address somehow also for its regular portal. Just wanted to mention that there is something that will address this for a lot of collections.

[tucotuco]

I am aware that many collections have very specific requirements and forms for loan requests, and I suspect that their first reaction to such a capability would be how to opt out of it.

[mbelisle]

I realize that my experiment is a fairly rudimentary solution to a much more complex issue. In this specific case, I have limited the email option to searches specific to a few targeted collections.

[MortenHofft]

I am aware that many collections have very specific requirements and forms for loan requests, and I suspect that their first reaction to such a capability would be how to opt out of it.

Thanks - that should certainly be an option as this do not make sense for most

[langeveldNMR]

From our viewpoint (that is one collection of one institution available through the portal), I think for the purpose of loans or receiving more information on a specimen/number of specimens a simple "Contact us [with a mailto: or website URL] for more information on this specimen." at the bottom of each detailed view of a record would help. The mailto:/website URL would be the same for all specimens contained in the dataset. This simple solution obviously would not work for portals with a broader scope.