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

127 results found

  1. Add job to bulk import asset metadata and files

    Currently there is actually no mechanism by which a batch of metadata and files for multiple assets can be imported into Esploro. Strongly recommend adding this functionality ASAP.

    34 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. 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…)
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. Improve management of previously affiliated researchers

    When a researcher leaves your institution, the only way to presently change their status from "Affiliated" to "Previously Affiliated" is to purge their user record from Alma.

    However, there may be reasons for an institution to retain the user's record even though they are no longer an affiliated researcher. For example, the user may be an alumnus or emeritus who retains certain library privileges or has fines associated with their account.

    As a result, institutions need a way to transition researchers to "Previously Affiliated" that doesn't require purging their user record.

    One possibility would be to add a toggle to…

    33 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. Resources in Esploro duplicated in Primo VE

    Resources inserted in Esploro are duplicated in Primo VE when a bibliographic record for the same work exists in Alma or in other collections.
    We are proposing that the deduplication process, used in Primo VE for other record sources, wolud be used also for Esploro resources

    31 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Other  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Improve version control of research assets

    Research outputs typically go through several different iterations or versions over the course of their lifecycle. NISO, for example, defines up to seven versions of scholarly journal articles http://www.niso.org/publications/niso-rp-8-2008-jav. In order to avoid confusion, support proper citation, and ensure compliance with publisher open access policies, it is critically important that institutional repositories clearly distinguish between different versions of the same work by prominently displaying this information in both the asset record and PDF cover sheet.

    Esploro currently offers two options for communicating version: asset type and file type.

    Asset type refers to the type of resource being deposited. When…

    31 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)
  6. Add dedicated accessibility fields

    Add fields to document the accessibility of individual research assets. This information can help Esploro managers track accessibility compliance for items and set expectations for users who may want to access items. At minimum, one field with controlled vocabulary terms and another for free-text entries would be helpful. See Cornell eCommons for sample controlled vocabulary terms addressing accessibility features and accessibility hazards: https://guides.library.cornell.edu/ecommons/batchmetadata#s-lib-ctab-19527879-4 We need our repositories to be in compliance with WCAG guidance and better mechanisms for tracking accessibility are paramount.

    30 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)
  7. Add job to batch edit and/or suppress file labels in File Viewer

    Currently, the file label displays in the File Viewer above the file itself and appears as prominently as the title of the asset (same font and size). For the thousands of assets we migrated to Esploro, this file label is by default the file name, which references the ID number of the file in our previous repository and nothing else (e.g., no author, title, year). This is not at all helpful to our patrons and is frankly quite ugly. So I would recommend that you add a job to edit and/or suppress the file labels in batch. Right now we…

    28 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)
  8. Export of search results from Portal

    Whereas in Primo, it is possible to export the results of a search (or at least, up to 50) by selecting them and then Exporting them, there does not seem to be the same option in the Researchers portal. We would like to be able to export search results from Esploro. Ideally, this export would not be restricted to 50.

    28 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)
  9. Fields that have content should be visible when editing an asset

    It should not matter what the asset type is, if it was brought into Esploro by DOI or Title, while the system populates fields automatically, all fields that were populated have to appear in the ‘Edit’ version of the form (and not only in the ‘Edit in Generic Form’, as it is today).

    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)
  10. LoC and DC Headings

    We would like to have the availablity to select Library of Congress or Dublin Core Subject Headings instead of the ExLibris base set of subjects. We found that ExLibris's base set is poorly inadequate and it became a huge annoyance and time consuming to copy and paste the Library of Congress headings for our catalogers.

    23 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)
  11. Move name variants and other researcher information when moving all assets and grants

    Right now when you move all assets and grants to another researcher record, you lose any unique information from the researcher record such as name variants, affiliations, areas of interest, research topics. You have to re-input this information into the researcher record you retain.

    Efficiency would be increased if unique information from a researcher record, including identifiers, moved along with assets and grants.

    22 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)
  12. 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…

    20 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)
  13. Add a facet for "Type of Degree"

    In case of different degree in the same faculty, such as School of Education offers both EdD and PhD. Currently, the search will return all ETDs in our repository that are associated with the School of Education. So it should capture all the Ed.D.'s, but it also include results of Ph.D.'s as well. There is no facet for type of degree. Therefore, it would be more user friendly for filtering search results by "Type of Degree".

    This is about as fine as we can parse it at the moment: https://researchdiscovery.drexel.edu/esploro/search/outputs?query=any,contains,*&page=1&sort=date_d&enable_asterisk_search=true&institution=01DRXU_INST&scope=ResearchETD&mfacet=facet_academic_unit,include,01DRXU_INST___3852,1

    19 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)
  14. Index the project type field

    ExLibris added a field called Project Type, which is an excellent way to distinguish types of theses (for instance, we would like to clarify which are senior honors theses, as opposed to master's theses). Unfortunately, without an enhancement, they will not index it, make it searchable, nor add it as a facet, which makes it pretty much useless. I would love to see this be a useful part of Esploro! This would also solve another idea, Add a facet for "Type of Degree"

    19 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)
  15. Separate configuration options for faculty and student works

    We would like to have more granular control over our asset display configurations. Theses/dissertations and other types of non-published student works do not have the same descriptive needs as published faculty works, and having a blanket configuration that is meant to address all types of published and non-published works is leading to confusion as to how to correctly present and interpret the presented metadata. In order to best represent our non-published student works and ETDs, it would be better to have those assets configured separately from faculty works.

    18 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)
  16. Link Esploro asset records to Alma bib records

    Permit Esploro asset records to be linked to bib records in Alma in the same way that holdings, portfolios, and digital representations are linked.

    Create an Alma job by which library staff can link assets to bib records by uploading a spreadsheet of asset IDs and their corresponding bib MMS IDs.

    Currently, we have two records for every ETD in our collection, the Alma bib record and the Esploro asset record. Both describe the same resource (the bib better than the asset record) and so they should be linked and not turn up in Primo as two separate search results.

    18 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)
    Under Review  ·  Dan Shor responded

    Esploro assets and Alma bib records are considered different entities, each one stands by itself so it is not planned to link an Esploro asset as a service of an Alma bib record. Having said that, we are considering to allow to create a relation between an asset and an Alma bib record in a similar way we allow to create relations between assets in Esploro today. Would this be a possible solution for your need?

  17. More options for adding asset metadata to notification approval emails

    It would be good if additional metadata options can be added to the notification approval emails, such as whether the asset is open access, value from a local field, or the complete citation of the asset. This would provide more detailed information to the researcher about which asset was approved, as well as whether it is open access.

    18 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)
  18. Local copyright permissions

    Over the years we've negotiated permissions with some publishers. Our local permissions can differ to information in Sherpa.

    We'd like a way to upload these permissions into Esploro so that we could interrogate it in a similar way to how we can through Sherpa in the form.

    17 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)
  19. Thesis advisor/committee member should populate Activities from the ETD record

    ETD asset records already have the activity of Thesis advisor/committee member connected directly with titles of ETDs, student names, dates and degree. Adding this information as separate Activities will be time consuming and will likely be filled with errors. This information should be maintained in one place, the ETD record, and then should display in the activity for the faculty member. We should not be creating duplicate information when we can help it. this would ensure that information remains current and is accurate

    17 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)
  20. Report on generated temporary links

    At the moment, you can generate a temporary link for a closed file with an expiry date. However there is no way to report on which files have links generated and what the expires are. This means there is no way to revoke links or update users if the file is changed. It would be good if the generated temporary links and the creation/expiry date could be reported on in Analytics.

    16 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)
← Previous 1 3 4 5 6 7
  • Don't see your idea?

Feedback and Knowledge Base