-
Notifications
You must be signed in to change notification settings - Fork 6
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
DOI search - not working #236
Comments
sorry Paul I just cannot get this to work on any DOI search |
@paulineobps I'm now able to find the document in your original comment using the search value |
The problem is that your retrieval actual DOI is : http://dx.doi.org/10.25607/OBP-1724
sorry Paul
Pauline
Pauline SIMPSON
Ocean Best Practices System Project Manager
https://www.oceanbestpractices.org/
UNESCO /IOC Project Office for IODE, Wandelaarkaai 7/61, 8400 Oostende, Belgium
Email: ***@***.******@***.***>; Alternate email: ***@***.******@***.***>; Skype: Pauline Simpson
ORCID: 0000-0003-2551-5740
<http://www.iode.org>
…________________________________
From: Paul Pilone ***@***.***>
Sent: 23 August 2022 12:16
To: iodepo/OceanBestPractices ***@***.***>
Cc: Simpson, Pauline ***@***.***>; Mention ***@***.***>
Subject: Re: [iodepo/OceanBestPractices] DOI search - not working (Issue #236)
CAUTION: This email is external from UNESCO. Please be vigilant on its sender and content. ATTENTION : Cet e-mail est externe à l'UNESCO. Soyez vigilant sur son expéditeur et contenu.
@paulineobps<https://github.com/paulineobps> I'm now able to find the document in your original comment using the search value 10.25607/OBP-561. When I use the value 10.26198/gfgr-fq47 I get 33 results ... so I'm not sure if that's correct or not. e.g. here is one of my searches:
[image]<https://user-images.githubusercontent.com/981227/186209383-226208f0-8423-4308-862e-1cd5b030ee1b.png>
—
Reply to this email directly, view it on GitHub<#236 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFZQUQZS7CUYW4WOGRVPXSTV2T2NVANCNFSM556SFQDA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Ok I see it now. It actually looks like it's matching because of the |
@paulineobps for the DOI - do we only care about the last 2 parts of the path? e.g. the metadata field can be stored as the full URL The other option is I handle DOI searches and append a wildcard to them so the actual search becomes I'm trying to understand if we want to support both options of searching or just require the user to follow the instructions in the search tips. |
everything before 10.25607/OBP-561 might not be unique, but every DOI will have a 10.xxxxx/nr, so go with that. It is in the Search Tips but also in future work, we have asked for a short tip in the search box when you choose a particular search parameter so for the DOI search it would have text in the search box that the search should be in the format 10xxxx (eg. 10.25607/OBP-561 or 10.1021/acssensors.1c01685 etc) |
This has been temporarily fixed and I'm going to remove myself as the assignee. This should still be looked at and fixed in a more permanent way. See the linked PR for more information or look at this line:
|
format 10.1021/acssensors.1c01685 is working now. _This should still be looked at and fixed in a more permanent way. Is this robust enough now |
on the new interface I tried 2 DOI searches- both of which are in the database - neither worked
http://dx.doi.org/10.25607/OBP-561
10.26198/gfgr-fq47
the search help indicates using format: 10.26198/gfgr-fq47
The text was updated successfully, but these errors were encountered: