API search for Affiliation gives result set that includes records where affiliation matches records having a matching affiliation in the past (but current affiliation(s) is not a match).
Enhancement request - ability to limit affiliation searches to records that match only most current affiliation(s) in researcher's ORCID record (i.e. exclude records where affiliation match was in the past / or is not current).
As suggested from support, one possible way would be to hook into where Affiliation has no ending date or is null on ending date.8 votes
Thanks for your suggestion to improve the ORCID Registry’s API search.
We’ll take this suggestion into consideration as we look into further improvements of our affiliations search feature and will update when we have further information.
ORCID Community Team
One of the commonest spellings of names which contain double letters, such as my surname, Mabbett, is to omit one if the letters.
Search for neither "Andy Mabbet" nor "Andy Mabett" finds my ORCID record.
The search algorithm should handle such cases.3 votes
Thank you for your suggestion to improve the ORCID registry.
We have submitted this iDea — improving fuzzier searches — for consideration in our next round of projects and will update you when we have further information on it going forward.
ORCID Community Engagement and Support
Please try to improve Search options in 2 ways:
1.- Aspect: show Search box in another locatiom, shape and colours. It's not obvious that this grey line is the Search box.
2.- More fields in Advanced Search: add affiliation and fields combined with Boolean operators
Thanks for your suggestion to improve the ORCID Registry. Since you’ve first submitted this suggestion, we’ve improved the appearance of the search bar, and are now working on the affiliations search. You can follow progress on the Current Development Trello at:
In the meantime, we would suggest that those looking into advanced search options also consider using the ORCID Public API. A tutorial is available at:
ORCID Community Team
A data source I am using to discover potential ORCID ids may/may not have initials as given-names. If your Lucene index had an EdgeNGram on given-names, to help accommodate incoming queries that contain abbreviated given-names, this would be immensely useful.
Alternatively, an additional, computed field like "given-name-initials" with EdgeNGram would be equally useful and would not change the behaviour of your existing Solr field, "given-names". A relatively simple regex-based method from https://github.com/berkmancenter/namae/blob/master/lib/namae/name.rb#L178 might prove useful.8 votes
Thanks for the suggestion. After discussing this with our development team this looks like something we can do using your initial suggestion of using EdgeNGram on the given-names field.
I’ve added this to our list of projects to get to this year. But our developers are working on a number of other major improvements to the ORCID Registry, so I don’t have an exact timeline as when we’ll get to this.
Search text should remain in the search box to facilitate revision and connect the user to the search results
The search string should remain in the search box so that it is easier for users to revise a search and to also help them make sense of the search results.10 votes
This is a great idea, but one we will not be able to get to soon. Right now we’re focused on major functionality and fixing bugs. But we plan to come back to these smaller but time consuming improvements soon.
- Don't see your idea?