Open gbif-portal opened 7 years ago
Combining external APIs into the dataset search sounds like it would be a headache. Unclear how to combine a taxon search and an ORCID search for example.
@kbraak could you please help estimating the impact of this? @fmendezh could you estimate the cost of updating the dataset search api to support search and autocomplete for orcId (and possibly other contact identifiers?)
I initially suspected it wouldn't be to hard to use the ORCID API to build a list of matching datasets, and then subsequent filters using the GBIF API would just take the intersection of datasets with that list... what do you think @MortenHofft?
In terms of impact for the user, it may not be big because they can already search DataCite for a list of datasets they contributed to (currently this only works if they are the dataset's creator though). It is also possible to add these datasets to their ORCID profile. In any case, the ability to show the complete list of datasets that they have contributed to is important in the eyes of funders and employers and is akin to listing the articles that they co-authored.
In terms of impact for GBIF, I think it will be big because it will help us assess our networks contributors' skills and activity level. By making this type of search more prominent, it will also make it easier to convince metadata authors to fill in the metadata correctly with the contributors' ORCIDs.
There seem to be two things here, one is the ability to search GBIF by ORCID, the other is linking datasets to ORCIDs.
For the first, I'm guessing the issue is whether GBIF can add ORCID as a field to be searched on to the database and to the registry API. I've no idea of the cost of doing this as I don't have a feel for how GBIF manages registry data.
For the second, going forward we can expect more EML files to contain ORCIDs so there's no additional work there. There would be some retrospective work to be done to assign ORCIDs to people and datasets we already have but for which we don't know the ORCIDs, but that would be doable and separate from any API or interface issues.
Long term I'd like to extend the use or ORCIDs by (a) being able to display papers about GBIF linked to ORCIDs, and (b) for anyone who logs in with an ORCID and who has contributed data indirectly (e.g., by describing a new species) we should be able to display those papers. This would require knowing more than we already know (e.g., taxonomic names linked to DOPis linked to ORCIDs, but I'm happy to help with that).
Allow users to filter datasets by ORCID iD
This would enable users to find all datasets a person has contributed to, so long as that person's ORCID was entered properly in the dataset metadata.
Making ORCID a prominent filter will highlight its value to GBIF's users and publishers.
The ORCID API can support this type of query, in case the GBIF API cannot. So too can the DataCite Search API could also support this type of query.
In the future, GBIF may allow a user to login using their ORCID account (https://github.com/gbif/portal16/issues/297). In this case, GBIF will be able to easily show the user a filtered list of all the datasets that they have contributed to.
fbitem-0059f96b33a12ae38a9a2449c0865b3a3cdfe76c Reported by: @kbraak System: Firefox 52.0.0 / Mac OS X 10.10.0 Referer: https://demo.gbif.org/dataset/search?q=0000-0002-3696-3496 Window size: width 1232 - height 1009 API log&_a=(columns:!(request,response,clientip),filters:!(),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E499%20AND%20(request:%22%2F%2Fapi.gbif.org%22)')),sort:!('@timestamp',desc))&indexPattern=uat-varnish-&type=histogram) Site log&_a=(columns:!(request,response,clientip),filters:!(),index:'prod-varnish-',interval:auto,query:(query_string:(analyze_wildcard:!t,query:'response:%3E399%20AND%20(request:%22%2F%2Fdemo.gbif.org%22)')),sort:!('@timestamp',desc))&indexPattern=uat-varnish-&type=histogram)