Skip to content

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

6 results found

  1. Improvements to Scopus Citation Metric loading

    In order to add Scopus Citation Metrics to Esploro assets, we currently have to create a list of DOIs, run the list through a script created by Mark Paris of Brandeis University, that script runs each doi through Scopus' API then outputs excel file(s) with the citation counts, we then upload the file(s) into Esploro following the method described in the Knowledge Base: https://knowledge.exlibrisgroup.com/Esploro/Product_Documentation/Esploro_Online_Help_(English)/Working_with_the_Esploro_Research_Hub/010_Working_with_Research_Assets#Loading_Citation_Metrics

    Script for harvesting citation metrics from Scopus: https://github.com/Brandeis-Library/esploroCitationUploads_Scopus

    Unfortunately, Esploro has a hard limit of 999 citations per excel file. At present, we have 90,000 assets that we need citation metrics for. We ask that ExLibris…

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

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

    In the January 2026 release there is a new API endpoint for loading Metrics. Will be able to match on MMS_ID, DOI, Web of Science ID, and Scopus ID.

  2. 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

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  3. 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.

    34 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  4. 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…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  5. SWORD for non-ETDs

    The SWORD integration currently allows only ETD deposits. Since we have a lot of works that would be deposited by non-researchers that are not ETDs, such as masters projects and posters, we would want to be able to create a SWORD tool that allows deposits of those assets as well by the user themselves. This request is specifically asking for a new SWORD endpoint that allows deposits of normal, non-ETD assets.

    8 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  6. Export Esploro assets (Mainly Theses) in known formats

    Hi,
    We have Theses in Esploro which we want to export to another system.
    We would like to be able to export the theses in at least one of these formats:
    Marc
    Marc XML
    DublinCore (DC)

    7 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
  • Don't see your idea?

Feedback and Knowledge Base