Esploro

Your feedback matters to us. Help us improve Esploro by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.


  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. ORCID Integration to populate other identifiers

    The current Esploro ORCID integration writes the employer to the ORCID. At Southern Cross we have an integration that also pulls the other identifiers from the ORCID record. It would be ideal if the Esploro ORCID integration also wrote the identifiers contained on the ORCID record to Esploro. For example ResearcherID and SCOPUS ID.
    Many researchers have linked these identifiers to their ORCID we would like to see them automatically linked via the API to the Esploro Researcher record.

    25 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. OAI_dc output improvements

    We would like some improvements to be made to the OAI_dc output file, for example

    dc:identifier:

    There are a number of identifiers for each record (ISSN, ISBN, DOI, Asset ID, URLs, Esploro URLS (long-type permalink, Viewer, document within viewer) but there is no qualifier to differentiate the identifier/link type

    dc:date:

    Both published date and conference/event date range appear as dc:date - they can be different years - how do we differentiate?

    dc:publisher:

    Shows both publisher and country - how to differentiate between the two?

    dc:rights:

    Includes licence information, copyright statement and internal rights (e.g. open, closed, metadata restricted) - how…

    14 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Create a new Researcher Profile API that returns the Researcher Profile as a complete entity

    Please create a new Researcher Profile API that returns the Researcher Profile as a complete entity. That is, it returns the contents of the Overview (including the profile URL), the Output, the Projects, and the Grants(?) tabs.

    1) It would be great to have all of this information returned in one API; and
    2) You currently have to filter the Assets API by "Shown in profile: Yes" in order to mimic the display in the Researcher Profile; and
    3) Projects (and future Grants?) information is not currently available via API.

    Thanks,
    Blake

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. "Update DOI Registration Agency - Research Assets" Job Improvements

    The "Update DOI Registration Agency - Research Assets" job that runs daily does not provide detailed reporting. A detailed report of successfully updated, failed, and migrated assets would aid in troubleshooting and administration of the job.

    3 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Feedback and Knowledge Base