1015 results found

1. Alma APIs Multilingual Code-tables

   We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

   Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

   We’d also like to highlight an inconsistency: the addressFrom field, which represents an email address, is language-dependent in the current setup. Since email addresses are universal and not language-specific, it would make more sense for this field to remain constant across all languages.

   Allowing language-neutral fields like addressFrom to remain consistent would simplify multilingual management and avoid unnecessary duplication across language settings.

   We’d like to request an enhancement to the Alma API that would allow PUT and POST requests to include translation updates. Currently, only GET requests support the lang parameter for retrieving localized data, while updates ignore these descriptions. Enabling translation updates via API would streamline content management across languages, making it easier to keep localized information current and consistent.

   Updating code tables for around 80 patron-facing letters in three different languages via the web UI is extremely time-consuming and inefficient. Allowing translation updates through the API would greatly improve this process, making Alma more effective for multilingual institutions.

   … more

   20 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Allow institutions to export and import all configurations from Alma

   Ex Libris has the new policy of forcing a refresh of the sandbox for all customers on the premium sandbox twice a year. This presents a significant challenge for institutions that use the sandbox actively, because it means that before every refresh, we have to go through the largely manual process of exporting all configurations out of the sandbox so we can keep record of them. Then if we want to recreate the old configurations, we have to do this manually.

   Ex Libris offers no way to export or import these configurations in bulk. This policy change reduces the value of the premium sandbox for customers who were already using it with the old policy, when we could request refreshes when we wanted. We would like Ex Libris to make it possible to export all configurations in bulk, and then reimport these configurations after the refresh. Ideally these would be exportable in bulk, and then you could pick and choose which configurations to reimport.

   Ex Libris has the new policy of forcing a refresh of the sandbox for all customers on the premium sandbox twice a year. This presents a significant challenge for institutions that use the sandbox actively, because it means that before every refresh, we have to go through the largely manual process of exporting all configurations out of the sandbox so we can keep record of them. Then if we want to recreate the old configurations, we have to do this manually.

   Ex Libris offers no way to export or import these configurations in bulk. This policy change reduces the value… more

   33 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Request for Improved linking to courses associated with a title from the ‘All Titles’ citation list

   As Library staff I want to be able to link to an associated Course code without the multiple clicking that is currently required.

   What is required:
   We are requesting that the result of an All titles search immediately displays with a “Courses” hyperlink for each title that would result in the courses list displaying on the next page.
   The Courses hyperlink would preferably display where the Orders and Requests hyperlinks currently display on the citation list page.

   Reasons:
   This would have the benefits of
   • Immediate identification of an associated course
   • Providing a 1 link click (rather than multiple clicking)

   Current scenario:
   1. Alma > All Titles > Keyword search
   2. For any title, click ‘Other details’
   3. Click the Courses link
   4. Go to More Actions > Reading List to see the citation in the reading list

   Please see the suggested screen mock-up in the attached file.

   As Library staff I want to be able to link to an associated Course code without the multiple clicking that is currently required.

   What is required:
   We are requesting that the result of an All titles search immediately displays with a “Courses” hyperlink for each title that would result in the courses list displaying on the next page.
   The Courses hyperlink would preferably display where the Orders and Requests hyperlinks currently display on the citation list page.

   Reasons:
   This would have the benefits of
   • Immediate identification of an associated course
   • Providing a 1 link click (rather… more

   • 

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello All,

   This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

   This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

   We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team

4. Pick up Requested Resources "Note"

   When Patrons make comments on Primo, we are unable to see them even when we have "Note" checked and marked out on custom view of "Pick up Requested Resources". If one clicks on more actions on the request...and click edit then see the comment the patron made. However, it would be good to have this show on directly "Pick up Requested Resources view"?

   2 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Fulfillment - Requests  ·  Delete…  ·  Admin →
   Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello All,

   This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

   This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

   We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team

5. Rapid ILL: ALMA Created lending request. To have .PDF Preview viewer also in 'Download Electronic Resource'

   In ALMA there are two different ways to upload a .PDF file to a Rapid ILL created lending request. The 'Ship item digitally' (Document Delivery) way allows upload and also content preview of the actual .PDF file. The other way is via 'Download Electronic Resource' which is better because citation information also appears. But the 'Download Electronic Resource' way does not have a content preview of the .PDF file. The idea proposed is to add the same .PDF file preview window, within the 'Download Electronic Resource' option. This will improve accuracy and efficiency in our workflow.

   1 vote

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Sharing  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. "Electronic material type originating from Bib" vs "Electronic material type" : a display issue in the Portfolio service editor's list

   In an electronic portfolio, there is a field called "Electronic material type originating from Bib" which can be overloaded by another field called "Electronic material type".
   The Job "Change electronic portfolio information" allows to update the material type of portfolios into the field "Electronic material type" into a set of portfolios.
   If we do so, the material type is not updated into the Portfolio service editor's list... which is confusing.

   our request : when the material type of a portfolio has been updated in the field "Electronic material type", ALMA should only considare this material type and display it in the Portfolio service editor's list.

   In an electronic portfolio, there is a field called "Electronic material type originating from Bib" which can be overloaded by another field called "Electronic material type".
   The Job "Change electronic portfolio information" allows to update the material type of portfolios into the field "Electronic material type" into a set of portfolios.
   If we do so, the material type is not updated into the Portfolio service editor's list... which is confusing.

   our request : when the material type of a portfolio has been updated in the field "Electronic material type", ALMA should only considare this material type and display it in… more

   •  

   •  

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Ability to customise email subject heading in Alma letters using letter data

   As library staff we would like the ability to customise the email subject heading of Alma letters using letter data so that we can flag something up to a customer/use in their email inbox.

   For example, we've recently customised our On Hold Shelf Letter using XSL to have different content when a customer is picking up a Resource Sharing request as we ask customers to collect these from our Customer Services desk whereas other requests are placed on a self service hold shelf in the library.
   We were able to customise the letter using XSL, but could not find a way to change the email subject heading for resource sharing requests in the same way as we were able to make the rest of the letter content conditional using XSL.

   As library staff we would like the ability to customise the email subject heading of Alma letters using letter data so that we can flag something up to a customer/use in their email inbox.

   For example, we've recently customised our On Hold Shelf Letter using XSL to have different content when a customer is picking up a Resource Sharing request as we ask customers to collect these from our Customer Services desk whereas other requests are placed on a self service hold shelf in the library.
   We were able to customise the letter using XSL, but could not find… more

   15 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. include cancellation note in create digitization cancellation email

   If a create digitization request on a lending request is cancelled, the explanation/message from the library/stores team is not included in the cancellation email to the lending partner.
   It would be nice if this went into the cancellation email as an extra bit of information explaining why the request has suddenly been cancelled.
   When the ILL Team cancel a request, we usually give a bit of an explanation, like missing from shelf, missing pages, too fragile, etc.

   3 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →
   Closed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

   Thank you for taking the time to share your idea with us. We truly appreciate your engagement and the thought you put into your suggestion.

   While we initially hoped it might align with broader needs, the idea has not gained the traction we typically look for to prioritize development. As a result, it’s unlikely to be pursued in the foreseeable future.

   That said, your feedback remains valuable, and we’re grateful for your contribution.

9. Improve OpenURL generation to remove blanks and duplicates

   Openurls generated could by Alma/Primo be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Background:

   We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

   We believe the responsibility here is on the Alma/PRimo side as the urls generated could be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Note: For our (UW-Madison's) locally developed discovery interface, we generate our own OpenURL links for things like "Request a copy" from article searching and the catalog records, so we can ensure proper length limits.

   ExLibris generates OpenURL links in their UResolver (Find it) and Primo Search API

   Alma/Primo OpenURLs

   For example, following a "Find it at UW-Madison" link from Google Scholar and then doing "Request a copy" (sending the OpenURL on to our ILLiad server):

   Starting in Google Sholar, and ending up here:
   https://uwi-primoalma-prod.hosted.exlibrisgroup.com/primo-explore/openurl?sid=google&auinit=PM&aulast=Vitousek&atitle=Beyond%20global%20warming:%20ecology%20and%20global%20change&id=doi:10.2307%2F1941591&title=Ecology.&volume=75&issue=7&date=1994&spage=1861&issn=0012-9658&vid=WISC&institution=WISC&url_ctx_val=&url_ctx_fmt=null&isSerivcesPage=true

   Provides an OpenURL link (request a copy) of:

   https://madison.hosts.atlas-sys.com/illiad/OpenURL?Action=10&Form=30&rft.genre=article&rft.title=Ecology.&rft.stitle=Ecology.&rft.atitle=Beyond+global+warming%3A+ecology+and+global+change&rft.jtitle=Ecology.&rft.au=&rft.date=1994&rft.month=&rft.volume=75&rft.issue=7&rft.number=&rft.spage=1861&rft.epage=&rft.edition=&rft.issn=0012-9658&rft.eissn=1939-9170&rft.aulast=Vitousek&rft.aufirst=&rft.auinit=PM&rft.pub=Brooklyn+Botanical+Garden&rft.pubdate=1920-&rft.pubyear=&rft.publisher=Brooklyn+Botanical+Garden&rft.place=Brooklyn%2C+NY+%3A&rft.doi=10.2307%2F1941591&rfe_dat=35698209&rfr_id=google

   Where the following parameters are included, yet blank:

   au, month, number, epage, edition, aufirst, pubyear

   Primo Search API

   In order to display electronic availability for articles we have to query the OpenURL resolver in alma to get data back. The string we use to query the resolver is provided to us by the Primo Search API

   Primo API Docs - Ex Libris Developer Network

   This one is by far the biggest offender, as that API returns the "GetIt1" URL we need to use. An example URL returned to us looks like:

   https://na02.alma.exlibrisgroup.com/view/uresolver/01UWI_MAD/openurl?svc_dat=CTO&ctx_enc=info:ofi/enc:UTF-8&ctx_id=10_1&ctx_tim=2020-02-07T10%3A04%3A19IST&ctx_ver=Z39.88-2004&url_ctx_fmt=info:ofifmt:kev:mtx:ctx&url_ver=Z39.88-2004&rfr_id=info:sidprimo.exlibrisgroup.com-proquest&req_id=&rft_val_fmt=info:ofifmt:kev:mtx:journal&rft.genre=article&rft.atitle=Telltale%20warming%20likely%20to%20hit%20poorer%20countries%20first&rft.jtitle=Nature&rft.btitle=&rft.aulast=Schiermeier&rft.auinit=&rft.auinit1=&rft.auinitm=&rft.ausuffix=&rft.au=Schiermeier,%20Quirin&rft.aucorp=&rft.date=2018-04-26&rft.volume=556&rft.issue=7702&rft.part=&rft.quarter=&rft.ssn=&rft.spage=415&rft.epage=416&rft.pages=415-416&rft.artnum=&rft.issn=00280836&rft.eissn=14764687&rft.isbn=&rft.sici=&rft.coden=&rft_id=info:doi/10.1038d41586-018-04854-2&rft.object_id=&rft.eisbn=&rft.edition=&rft.pub=Nature%20Publishing%20Group&rft.place=London&rft.series=&rft.stitle=&rft.bici=&rft_id=info:bibcode&rft_id=info:hdl&rft_id=info:lccn&rft_id=info:oclcnum&rft_id=info:pmid&rft_id=info:eric((addataeric}}&rft_dat=%3Cproquest%3E2056433252%3Cproquest%3E%3Curl%3Ehttp:search.proquest.com/docview/2056433252/%3C/url%3E,language=eng,view=MD&svc_dat=viewit&req.skin=MADskin&rft_pqid=2056433252&rft_galeid=572639507&rft_cupid=&rft_eruid=&rft_nurid=&rft_ingid=

   Previously we ran this URL through a parser to validate it and then remove empty parameters. There are three issues with this data - 1) sometimes keys are duplicated, which goes against best practices 2) Data is not properly url encoded 3) There are a lot of empty parameters.

   Removing those parameters for this example request would drop the length of the URL from 1328 to 1052 characters

   Note: We no longer parse this data as it was dropping the duplicated parameters causing lookup issues, so it's passed through to our OpenURL resolver as we receive it from the API (aside from prepending a parameter to return XML instead of HTML)

   Openurls generated could by Alma/Primo be shorted by:

   1. Not sending duplicate parameters.
   2. Not sending empty parameters.

   Background:

   We have noticed that OpenURLs produced by Alma/Primo (which are then sent on to our ILLiad server, which can require redirection to get the patron authenticated) can be VERY long. So long in fact, that they can produce errors for our ILLiad web server. The ILLiad server will end up reporting "Request header is too large", and the user is left with a HTTP Status 400 Bad request error.

   We believe the responsibility here is on the Alma/PRimo side as the urls… more

   16 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Closed  ·  AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

   Hello all,

   This idea has been closed as part of a cleanup process for ideas older than a year with fewer than 20 votes. This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the CERV process. We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

   Alma Product Team.

10. Add column to Patron service on the Loan-tab which shows that the item has been requested by another user

    Our fulfillment department often gets phone calls of patrons who do not understand why their loan can not be renewed. Now we have to click the View queue in Actions to check this, but it would be much more convenient to see in a blink of an eye that there are requests immediately on the loan tab.

    25 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Already Supported  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

    Two columns in the Manage Patron Services page display the most recent status and date for the item if any renewal has been attempted. See https://knowledge.exlibrisgroup.com/Alma/Release_Notes/0099_2017/100_March_2017/Alma_March_2017_Release_Notes/04Fulfillment_-_March_2017_Enhancements#Renewal_Enhancements_in_Manage_Patron_Services

11. Please add the feature „Chat between Institution Zones“ to the Metadata Editor

    Ex Libris should offer the option of creating a chat for each data record. This feature would facilitate communication between individual libraries regarding incorrect data records.
    Currently, communication concerning bibliographic records are sent by email via a mailing list. For a library that has many departments with numerous employees, it is difficult to develop a workflow for jointly processing these emails. In a chat, several people within an institution can communicate with each other without having to coordinate internally beforehand.
    But smaller libraries would also benefit from this chat function. When several emails are sent back and forth on a topic, it quickly becomes confusing.
    It is also more efficient and clearer if the communication about a data record can be found next to the data record itself.
    One way to integrate a chat function into individual records would be to add a “Chat between Institution Zones“ button to each record in the search view and/or in the Metadata Editor (see image Alma Chat 1.1 and Alma Chat 1.2).
    An editor should then open (a big window unlike the small window provided by the „Add Note“ option“), in which the written exchange between the libraries concerned can take place. One library sends a request to the other libraries, and the other libraries respond to it. The last library to respond, or the library that makes the final adjustments to the record, should change the status of the chat from “open” to “closed” This requires a drop-down menu within the chat editor (see image Alma Chat 2 + 3).
    All chats with the status „open“ in every Institution Zone should be searchable using the advanced search (see image Alma Chat 4). Chats with the status „closed“ could still be searched using the title or ID of the record via the simple search.

    Ex Libris should offer the option of creating a chat for each data record. This feature would facilitate communication between individual libraries regarding incorrect data records.
    Currently, communication concerning bibliographic records are sent by email via a mailing list. For a library that has many departments with numerous employees, it is difficult to develop a workflow for jointly processing these emails. In a chat, several people within an institution can communicate with each other without having to coordinate internally beforehand.
    But smaller libraries would also benefit from this chat function. When several emails are sent back and forth on a… more

    •  

    •  

    211 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    14 comments  ·  Resource Management - General  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Add a week key to dates eg request dates

    We would like to be able to look at physical item requests by week, but can only currently do it by month. Could a week key be added to analytics?

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Delete…  ·  Admin →
    Completed  ·  AdminYoel Kortick (Senior Librarian, Ex Libris) responded

    In the ideas exchange " Add a week key to dates eg request dates" You ask:
    We would like to be able to look at physical item requests by week, but can only currently do it by month. Could a week key be added to analytics?

    We answer:
    This can be done using the “Request Date Week Number” in the Requests Subject Area.
    This field did not exist in 2017 when you opened the ideas Exchange.

13. Significant Improvements to the 'Browse Shelf List' Function Needed

    The 'Browse Shelf List" function is essential for catalogers in our library and is extremely clunky and time-consuming to use. Proposing any (hopefully all) of the following changes:

    1. Ability to view more results surrounding the exact search request.
       Said in a different way, the ability to view the result in the middle of the results page, so as to be able to see a few of the results both before and after. This makes call number adjustment significantly easier, instead of always needing to click a back button and remember what the call number were on the page before.

    2. Ability to view shelf-list in Primo with one click.

    3. Ability to actually be able to see the entire call number in the call number field (see screen shot with blue arrow).

    If I need to type the call number by hand, or edit it at all, it is very difficult to see the entire thing or use this field if it cuts itself off.

    1. Removal of the need to click into the call number field to search the shelf listing.

    2. Ability to search the shelf list by call number that ignores sub-field labels.

    It appears to me that “Browse Shelf Listing” is done only against the 050 field in a bib record and only against the subfield “a” in that 050 field. This greatly limits the usefulness of this tool.

    Not to mention, call numbers can be found in 099 and 090 fields, requiring copy paste.

    Thus, the only way to search the shelf list accurately is to copy and paste the call number into that tiny, tiny box, then edit out the $$a, $$b, $$h and so on. This is a painful experience on 20+ books a day.

    The 'Browse Shelf List" function is essential for catalogers in our library and is extremely clunky and time-consuming to use. Proposing any (hopefully all) of the following changes:

    1. Ability to view more results surrounding the exact search request.
       Said in a different way, the ability to view the result in the middle of the results page, so as to be able to see a few of the results both before and after. This makes call number adjustment significantly easier, instead of always needing to click a back button and remember what the call number were on the page before.

    2. … more

    •  

    221 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    21 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
    Completed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    The Alma Browse Shelf Listing enhancements are completed.

    This includes the following:

    1. Author information will be displayed in the browse results, to assist in adding call number cutter for libraries that use author information for this.

    2. Call number auto-population will also work for local 09X fields.

    3. Read-only access was added, so that all users can now browse shelf listing (similar to browse bib and authority headings)

    For more information please refer to the online help for Browse Shelf Listing.

14. Add User Statistical Categories as a Parameter in Fulfillment Units Rules

    We would like the ability to add user statistical categories as input parameters when configuring Fulfillment Units. This will allow us to apply additional terms of use (TOUs) to certain subsets of User Groups.

    Right now, we are able to configure Fulfillment Unit rules based on User Groups (i.e. Student, Staff, Community Member, etc.). However, there are certain subsets of users within these groups (for example, a student that is part of a scholarship program, learning community, or major) that we would like to apply different TOUs to. We can identify these users with Statistical Categories and if we could configure input parameters for Fulfillment Unit loan and request rules with these Statistical Categories, we would be able to apply the desired TOU for those users.

    Please add user statistical categories as a parameter in fulfillment unit rules for loans, requests, and bookings.

    See attached images. One shows a mockup of editing a parameter with “Statistical Category” as the name option, and values derived from the User Statistical Categories Code Table. The other shows a mockup of an example fulfillment unit loan rule relying on statistical categories.

    We would like the ability to add user statistical categories as input parameters when configuring Fulfillment Units. This will allow us to apply additional terms of use (TOUs) to certain subsets of User Groups.

    Right now, we are able to configure Fulfillment Unit rules based on User Groups (i.e. Student, Staff, Community Member, etc.). However, there are certain subsets of users within these groups (for example, a student that is part of a scholarship program, learning community, or major) that we would like to apply different TOUs to. We can identify these users with Statistical Categories and if we could… more

    •  

    •  

    29 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    Completed  ·  1 comment  ·  Fulfillment - General  ·  Delete…  ·  Admin →

15. Pull requested page number from digitisation requests etc in Analytics

    It would be useful to have the ability in Alma analytics to create a report which pulls through the details of the page numbers entered during the digitisation request process.

    The digitisation request form in Primo has fields for "Required Pages - From/To"
    The "Approval Requests List" in the Fulfillment are in Alma also shows the required pages.

    It would be useful to pull this information into the Requests Subject area in Analytics.

    1 vote

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Analytics  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

16. Resource Sharing Partner: Contact Information and Parameters tab (multiple e-mail addresses)

    In the Alma documentation it is noted that the Contact tab of a Resource Sharing Partner is currently not functional:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/050Resource_Sharing/005Managing_Resource_Sharing_Partners/010Resource_Sharing_Partners
    "In the Contact Information tab, add address, phone number, and email information for the resource sharing partner (for informational purposes only; information for sending the resource sharing request is entered in the Parameters tab – see the following step). For instructions, see Adding User Contact Information."

    The options (Email types) on the tab correspond to those of an Acquisition supplier (on the Vendor level and the Account level), but have not yet been implemented functional for Resource Sharing Partners. However, there is a great need for it.

    We have several Partners with different e-mail addresses for e.g. ordering and claiming or sending queries.
    So we would be glad, to have the full functionality for all Email types (Order, Claim, Payment, Queries, Returns) on the Contact tab as it is already the fact for Vendors (Acquistion).

    Currently for all ILL letters Alma used the e-mail address from the Parameters tab only.
    An also on this tab an enhancement is needed. It would be fine if you could define two e-mail addresses:
    - one for Lending Requests
    - and the other for Borrowing Requests
    because some Partners use diffent e-mail addresses for Lending and Borrowing requests and this enhancement would prevent unnecessary e-mail forwarding to the Partner libraries.

    Thank you in advance!

    In the Alma documentation it is noted that the Contact tab of a Resource Sharing Partner is currently not functional:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/050Resource_Sharing/005Managing_Resource_Sharing_Partners/010Resource_Sharing_Partners
    "In the Contact Information tab, add address, phone number, and email information for the resource sharing partner (for informational purposes only; information for sending the resource sharing request is entered in the Parameters tab – see the following step). For instructions, see Adding User Contact Information."

    The options (Email types) on the tab correspond to those of an Acquisition supplier (on the Vendor level and the Account level), but have not yet been implemented functional for Resource Sharing Partners.… more

    30 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Enable us to display items in an "Unavailable" location type as Unavailable in Primo

    We need the ability to show items that are assigned to a location with Type = UNAVAILBLE to show as unavailable in Primo

    The primary use cases that prompt this idea are:
    1. A library is closed for renovation and the items are inaccessible to staff and patrons, but the items must still be discoverable so that patrons can be directed to Resource Sharing in Primo.
    2. Portions of a collection are temporarily inaccessible to staff and patrons, and the items are assigned to a temp location, but must still be discoverable so that patrons can be redirected to Resource Sharing in Primo.
    In both of these use cases, setting the Location(s) to type = UNAVAILABLE accomplishes both suppressing a link for local requesting, and allowing a Request for Resource sharing link to appear, without any other configuration changes

    Right now, items that are in a type=UNAVAILABLE location show in Primo with a prominent "Available" indicator in several places, and use the label for c.uresolver.getit2.item_list.status.ITEM_IN_PLACE in ViewIt, even though the items are not actually available. There is no way to use existing functionality to suppress this "Available" label or the "In library" (ITEM_IN_PLACE) label without an unreasonable amount of work (see info on the impracticability of using work orders below)

    What is needed:
    1. The calculated availability for items in a type=UNAVAILABLE location needs to be Unavailable/Not Available, when Alma might otherwise consider the items to be "in place" (not on loan, not in a process, etc)
    2. The ViewIt information for items in a type=UNAVAILABLE location needs to use a new label, and not the "c.uresolver.getit2.item_list.status.ITEM_IN_PLACE" label

    Why the suggestion on the closed Idea 46262368 "make location type 'unavailable' functional: items in these locations should be shown as unavailable in Alma and Primo" (see URL below) of using work orders to accomplish this is unworkable:
    1. Work orders cannot be removed in bulk. If there are 300000 items that needs to be set to UNAVAILABLE, removing 300000 work orders manually when they are available again is an enormous burden on staff, and is practicably impossible.
    2. Patrons find the Primo display of items in work orders to be confusing
    3. Items in work orders are requestable unless further changes are made to the items or to configurations. Using a type=UNAVAILABLE location accomplishes the un-requestability without needing to do any other configuration or data changes,

    SUMMARY:
    Give us the ability to show items in a type=UNAVALABLE location as unavailable in Primo
    - enabling clear and understandable display of an item's availability to our patrons
    - without onerous additional work

    Note: this is basically a repost of https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/46262368-make-location-type-unavailable-functional-items
    That idea was closed despite support for the idea, and despite the unworkability of the "just put them in a work order" response from Ex Libris

    We need the ability to show items that are assigned to a location with Type = UNAVAILBLE to show as unavailable in Primo

    The primary use cases that prompt this idea are:
    1. A library is closed for renovation and the items are inaccessible to staff and patrons, but the items must still be discoverable so that patrons can be directed to Resource Sharing in Primo.
    2. Portions of a collection are temporarily inaccessible to staff and patrons, and the items are assigned to a temp location, but must still be discoverable so that patrons can be redirected to Resource… more

    •  

    266 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    8 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating
    AdminTamar Fuches (Alma product manager, Ex Libris) responded

    Dear colleagues,

    Thank you for raising this idea.

    This was part of the CERV cycle in 2025, but did not make it to the final list.

    During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:

    Option 1: New dedicated process type

    • It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
    • Items marked as "unavailable" will be considered as "not in place"
    • The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules

    Option 2: Mark a location as "unavailable"

    • It will be possible to mark a location as "unavailable"
    • All items in this location will be considered as "not in place"
    • The difference from option 1 is that when an item is in an "unavailable" location, it can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
    • The existing options for location based configuration can be used

    Option 3: A new "unavailable" field in item level

    • It will be possible to mark specific items as "unavailable", similar to the availability status of portfolios
    • Items marked as "unavailable" will be considered as "not in place"
    • Similar to option 2, "unavailable" item can still be in a process such as loan, work order or any other process type. These are 2 separate attributes
    • As this is a new attribute, relevant configuration options will need to be enhanced to take this attribute into consideration. Further analysis will be needed here

    Although option 3 might give more flexibility, it is super complicated and would require huge effort. Therefore, the selected option is option 2: Mark a location as "unavailable".

    The description of this idea exchange sounds like this option, however in the comments I saw some references to option 3. Therefore I wanted to share with you the analysis and discussion - you can see it in: https://public.3.basecamp.com/p/ERLrkhNUHtTYerEiaQAsG2uT

    Please note that as this did not make it to the final list of the CERV selected items, there is no timeline for implementing this.

    Thanks,

    Tamar Fuches

    Alma product team

    Dear colleagues,

    Thank you for raising this idea.

    This was part of the CERV cycle in 2025, but did not make it to the final list.

    During the analysis, 3 possible approaches were discussed, each has a different estimation and effort:

    Option 1: New dedicated process type

    • It will be possible to mark specific items as "unavailable", similarly to the way it is possible to mark them as "missing"
    • Items marked as "unavailable" will be considered as "not in place"
    • The new "unavailable" option will appear as a possible process type in all the places where there is a list of process types, including configuration options such as Fulfillment Unit Rules

    Option 2: Mark a location as "unavailable"

    • It will be possible to mark a location as "unavailable"
    • All items in this location will be considered as "not in place"
    • The difference from option 1 is that when an item… more

18. Add the Lender's mailing address to the Resource Sharing Receive Slip Letter xml

    Adding this xml to the letter code would allow us to print the Lender mailing address on our Resource Sharing Receive Slip Letter. This would help us be more efficient by printing just this single letter at the time this item is received, as we normally would. Then, when our patron returns the item with the slip, we won't have to physically print out the mailing address, and can use the slip already enclosed in the book.

    For example, this xml info is included in the Ful Resource Sharing Request Slip letter in the following fields: "notificationdata/partnershippinginfolist/partnershippinginfo/address1" and address2, 3, 4, 5 etc. and /partnershippinginfo/city , state, and postal_code.

    With those lines, we created a mailing label for our outbound resource sharing requests to print on our pull slips, which has increased our efficiency. We're wanting to do the same with our receive letter.

    Adding this xml to the letter code would allow us to print the Lender mailing address on our Resource Sharing Receive Slip Letter. This would help us be more efficient by printing just this single letter at the time this item is received, as we normally would. Then, when our patron returns the item with the slip, we won't have to physically print out the mailing address, and can use the slip already enclosed in the book.

    For example, this xml info is included in the Ful Resource Sharing Request Slip letter in the following fields: "notificationdata/partnershippinginfo… more

    20 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Other  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

19. Cancellations - Need to specify more than "System"

    When a fulfillment request is cancelled, it should specify who cancelled it e.g. patron via Primo (incl. name), librarian, other and not just "System".

    5 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Fulfillment - General  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team

20. Enhancement request for New MDE > Editing Actions > Expand from Template

    Request for customizing the sorting and enable/disable the template options in the Choose Template dropdown list
    The current sorting is starting from public ones followed by private ones, in alphanumeric order respectively.
    We hope for being able to toggle enable/disable and customize the ordering of the template options

    For achieving the above feature, refer to New MDE > New > Templates display configuration
    A similar toggle button for each template, similar to the Display in Menu toggle button here, is desired.
    And allowing manually sorting the order of the templates would be appreciated as well.

    0 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Resource Management - Physical  ·  Delete…  ·  Admin →
    Closed  ·  AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello All,

    This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.

    This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.

    We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.

    Alma Product Team