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.
56 results found
-
Add notes that display in Esploro brief record display
Though many Esploro researcher deposits naturally disappear from the research deposits queue as part of their lifecycle -- approved, returned to researchers, etc. -- for deposits that for one reason or another have to remain in the deposits queue for an extended period, a type of internal note explaining their presence in the brief display would be very helpful.
In our case, our library does the work of seeking OA permissions for deposits, leaving deposits in the queue awaiting responses for a period of days, weeks, and in rare cases months. As you may imagine, this can build up very…
13 votes -
Allow repository staff to send canned responses
Allow customers the ability to create and store canned messages that can be used when communicating with researchers. Esploro already offers the ability to create custom return reasons that can be selected when returning a deposit. But this feature would be even more useful if selecting of one of those reasons also sent customizable canned message that could be used to provide further instruction to the researcher on how to modify and resubmit their deposit. It would be useful to have a set of canned messages that could be used when approving a deposit to notify the researcher if any…
2 votes -
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 votesThis Idea is very broad, and since it was opened new functionality has been added, in particular the Update by CSV. CSV update covers all metadata fields in the Asset but does not include Authors, either creators or contributors, or Files.
It would be helpful to get an updated list of priorities.
-
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 votesThis idea has been accepted which means that it has been added to our backlog. The status will be updated to "planned" when it has been scheduled.
-
Add a creation date to the summary asset record
In order to manipulate and identify files for individual or batch processing, the display of the asset record creation date in the summary asset record would be very useful.
I've attached an image of the existing summary asset record. At present, only an 'Asset last updated' field is included. It would be a logical next step to display when the record was created.6 votes -
Add way to facet research deposit by assigned to person
As staff members are learning how to add deposits to Esploro, I review the work. Now that we have several people adding items, it would be helpful to be able to filter to one specific person to aid in training/reviewing their work
9 votes -
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.
29 votes -
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…
34 votesUnder Review · AdminShoshana de la Fuente (Product Manager, Esploro Repository, Ex Libris) respondedThank you for your suggestion. We are considering allowing batch update of file display titles through CSV update.
-
Add Thesis dc Field to OAI Output
Add the <dc:type>Thesis</type> to identify theses.
Theses are frequently searched for by our Research Repository users and this would make them more discoverable.
Thank you
Keely Chapman
RMIT University Library2 votes -
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.
18 votes -
More granular history tab in asset mediated form
It would be good to have more granular information in the History tab of the asset form. At the moment it only records when a deposit was created or approved. Adding when fields were edited and which fields were edited, similar to what is in the Researcher History tab, would allow for greater auditing of when metadata is changed. This would be particularly useful when large teams are editing records.
9 votes -
Include affiliation when replacing an author with an existing researcher
It would be more efficient if we could add an affiliation when we are replacing a creator/contributor on a record with an existing researcher. As it is, I need to replace and then go back and edit the researcher to include an affiliation.
7 votesThank you for this idea. We will look into adding this functionality to the roadmap.
-
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 -
Duplicate an existing record for new record edit
It would be good to be able to duplicate an existing asset in order to create and edit a new asset. This could be especially useful if there are multiple book chapters from the same book, or conference papers from the same conference.
12 votesThank you for this idea. We will work on adding this feature. What kind of metadata would you like to duplicate and copy to the new asset? What kind of data would you not want to copy over to the new asset?
-
Batch edit creators and contributors
When library staff are mediating a deposit, it would be good to be able to edit creator or contributor information in a batch using check boxes next to each creator/contributor and options at the top of the creator section - add/edit role, add/edit affiliation and delete creators/contributors. This would save considerable time as the librarian wouldn't be required to edit each name individually.
9 votes -
Ability to reorder fields with multiple lines via drag and drop in back end and on profile
We would like to see drag and drop functionality implemented across all fields in both the repository and the portal that have mutlitple lines, e.g. relationaships on assets so that relationships can be displayed in desired order. Links on the profile page. Education. Research topics and keywords. Related content on the asset.
Currently many of theses fields display in the order they are entered and some display in a random undetermined order. If links need to be reordered they have to be deleted and re-added. This is a duplciaiton of effort.
2 votesThanks for raising this idea . In the next couple of releases we will gradually add support for reordering of fields on the researcher record – both in the Research Profile and the Researcher Management page – and on the asset page.
- Don't see your idea?