The support.orcid.org website is on a UserVoice platform that has a different privacy policy from our other sites. You may view the details at http://support.orcid.org/tos
X

I suggest that...

Search API - Need for additional fields in result list

With API 2.0 all requests to /search are answered with just a list of identifiers.
This is not sufficient for many use cases and forces clients to perform additional HTTP requests in order to present search results to human users.
In my opinion the existing /search endpoint should be extended to display all available index fields if needed.
This could easily be done without breaking existing contracts, e.g. by introducing another optional request parameter that allows clients to specify what fields should come with the response or by introducing an additional content type that allows clients to ask for full records in their search requests.

3 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Jan Schnasse shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  AdminORCID (EMEA) (Admin, ORCID) responded  · 

    Thanks for your suggestion to improve the ORCID Registry.

    We’re going to add this to our list of improvements to consider for the future and will update here accordingly.

    Warm regards,
    ORCID Community Team

    0 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...

      Feedback and Knowledge Base