Joseph Deodato
My feedback
32 results found
-
28 votesJoseph Deodato supported this idea ·
An error occurred while saving the comment -
90 votesJoseph Deodato supported this idea ·
An error occurred while saving the comment Joseph Deodato commentedWe strongly support this idea. Our use case for this enhancement would be Unpaywall for CDI (Collection ID 61738162240004646). This is database collection with no portfolios that displays a link in record for open access content available from Unpaywall. The problem is the open access version of a publication can sometimes differ from the final published version. However, there is no way to communicate this to the user. Ideally, it would be great if Ex Libris could capture version information from Unpaywall and display this data along along with the access URL. At minimum, however, customers should have the option to add a public access note to the collection that displays with the link in record to let users know that the linked version may be different from the one described in the record.
-
161 votesJoseph Deodato shared this idea ·
-
3 votesJoseph Deodato shared this idea ·
-
71 votesJoseph Deodato supported this idea ·
-
3 votesJoseph Deodato shared this idea ·
-
5 votesJoseph Deodato shared this idea ·
-
2 votes
An error occurred while saving the comment Joseph Deodato commentedAssuming the path could be set to not display for suppressed collections, I don't think this would cause confusion.
While there are other ways of achieving this, we think they could be made much simpler with the addition of a visibility checkbox or toggle. And since this solution already exists in other Ex Libris products like Esploro, we thought it would be easy enough to implement in Alma. That said, we appreciate the suggested workarounds and welcome any others.
Joseph Deodato shared this idea · -
81 votesJoseph Deodato supported this idea ·
-
4 votesJoseph Deodato shared this idea ·
-
12 votesAdminTami Ezra (Admin, Ex Libris) responded
Continues to be part of longer term roadmap but no firm date yet so removed the "Planned" status.
Joseph Deodato shared this idea · -
44 votesJoseph Deodato supported this idea ·
-
1 voteJoseph Deodato shared this idea ·
-
1 voteJoseph Deodato shared this idea ·
-
3 votes
-
7 votesJoseph Deodato shared this idea ·
-
14 votesJoseph Deodato supported this idea ·
-
49 votesJoseph Deodato supported this idea ·
-
315 votesJoseph Deodato supported this idea ·
-
220 votes
The core user record will have a field for selecting a preferred pronoun. The options will be from a configurable drop down such as:
- he, him, his
- she,her,hers
The field will be updatable from:
- Alma form
- SIS
- API
- Primo (VE)
The preferred pronoun will in the Manage Fulfillment Options screen.
It will be possible to locally override this field without overriding from the SIS, like other fields allow (such as user group).
An error occurred while saving the comment Joseph Deodato commentedHi Moshe.
A similar request was submitted for Esploro. Would this field also be available for display in the researcher's profile?
See related request: https://ideas.exlibrisgroup.com/forums/929326-esploro/suggestions/44468628-add-preferred-pronoun-field
Joseph Deodato supported this idea ·
We strongly support this idea. We recently inquired with customer support as to why searching within a collection does not include the contents of its subcollections and were informed that this is "due to technical limitations that are caused by the way that the collection discovery tree is built".
Our users agree that this behavior is counter-intuitive and hope those limitations are not insurmountable.