1015 results found

1. Allow prioritization of item requests based on library proximity and capacity

   In our consortium, several libraries are linked through relationships. However, these libraries differ in distance, staffing levels, and delivery times.
   We would like Alma to provide a way to prioritize the fulfillment of requests based on configurable criteria such as library proximity, staff availability, or delivery speed (as actual transit time rules are not efficient enough).
   This enhancement would enable the system to route requests for multiple available items to the most suitable library — ideally the closest or best staffed — thereby streamlining daily operations and improving service efficiency across the consortium.

   17 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 - Requests  ·  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. Enable desk operators to select from a predetermined list of loan periods.

   We would like desk operators to have the option of selecting from a list of predetermined check out periods for items in certain collections.

   Boston College Libraries currently provide approximately 80 laptops to community members, which can be borrowed for a fixed loan period. For many patrons this static loan period is either too short or too long, adding some loan period choices would enable us to easily meet the needs of more patrons.
   Currently in Alma, offering a variety of loan periods would require the creation of additional locations and terms of use. Doing so would enable us to move subsets of our inventory to each location, however, this is an inherently a rigid way of inventory control. What we are looking for is a more flexible system that enables our entire laptop inventory to circulate for a variety of loan periods.

   The imagined workflow:

   1. Patron comes to borrow a laptop.
   2. The laptop is loaned in Alma
   3. The operator is presented with a dialog box with a series of loan period options (configured at the library level) - for example (4 Hours, 1 Day, 4 Days, 7 Days).
   4. The operator asks the patron which loan period meets the need and makes the selection in Alma to complete the loan.

   Thank you for considering this request.

   We would like desk operators to have the option of selecting from a list of predetermined check out periods for items in certain collections.

   Boston College Libraries currently provide approximately 80 laptops to community members, which can be borrowed for a fixed loan period. For many patrons this static loan period is either too short or too long, adding some loan period choices would enable us to easily meet the needs of more patrons.
   Currently in Alma, offering a variety of loan periods would require the creation of additional locations and terms of use. Doing so would enable us to… more

   180 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 - Loans  ·  Delete…  ·  Admin →
   Closed  ·  AdminMoshe Shechter (Alma Senior Product Manager, Ex Libris) responded

   Adding more than one policy to a TOU would add a lot of complexity to TOU and loan rules management. Perhaps it is simpler to change a due date manually at loan time

3. Electronic portfolios in an electronic collection/packages should inherit data displays from the collection's service

   Data elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
   While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down to the individual portfolio display in Alma either. Currently, the only service level information that appears in a portfolio is the Service Parse Params. Request: Data elements that are set at an electronic collection's service level (specifically, proxy settings and public/authentication notes) should cascade down to the portfolio level display. Staff shouldn't have to check two places to see the correct setting

   Data elements that are set at a Electronic collection service level should cascade down and be applied/display at the electronic portfolio level.
   While portfolios that are part of an electronic collection/package inherit the properties that are set at the service level, those inherited properties do not display in Alma in the individual portfolios. For example, the proxy value in the individual portfolios will always display in Alma as "No" even when the true value inherited from the electronic collection's service is "Yes." Similarly, a public or authentication note entered at the electronic collection or service level does not cascade down… more

   43 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  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   Completed  ·  Dana Moshkovits responded

   As part of Alma June release Advanced search query options were expanded to include Not Contains Keywords, Is Empty and Is Not Empty for electronic resources indexes.
   For more information please see:
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2020/Alma_2020_Release_Notes

4. Display Number of Renewals information under ‘Other Details’ of a Physical item

   To enhance the circulation service and provide convenient access to usage information, we suggest displaying the renewal information including ‘number of renewals’ and ‘last renewal date’ under the ‘Other details’ section of a physical item in Alma. The number of renewals records how many times the due date of a loaned item was extended before the ‘maximum renewal period’. This figure is often essential to measure the usage and understand patron’s intention to continuously keep the loaned item.

   In current release of Alma, the information under ‘Other details’ of a physical item shows usage information for circulation such as loans, request, etc, but it does not have ‘renewals’ information (please see the attachment). Library staff is advised to create an Analytics report to retrieve ‘renewals’ information on Analytics platform.

   To streamline the process and provide faster access to information, it would be beneficial to have ‘number of renewals’ and ‘last renewal date’ to be displayed directly under ‘Other details’ of a physical item in Alma. This would enrich the display of usage information under ‘Other details’ and further improve the circulation service."

   We kindly request considering this suggestion to enhance the functionality of Alma and provide library staff with more efficient access to valuable usage information. Thank you!

   To enhance the circulation service and provide convenient access to usage information, we suggest displaying the renewal information including ‘number of renewals’ and ‘last renewal date’ under the ‘Other details’ section of a physical item in Alma. The number of renewals records how many times the due date of a loaned item was extended before the ‘maximum renewal period’. This figure is often essential to measure the usage and understand patron’s intention to continuously keep the loaned item.

   In current release of Alma, the information under ‘Other details’ of a physical item shows usage information for circulation such as loans, … 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…)
   0 comments  ·  Fulfillment - Loans  ·  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

5. Add call number information to Borrowing Requests subject area

   This would allow us to do collection development based on the topics our users are interested in and in which our collections may be lacking. Reasons would include locate failed, unavailable at all holding libraries, and all the reasons that can be selected when a request is rejected.

   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  ·  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

6. Job for copying the configuration from the production environment into the Standard Sandbox

   Making testing and training in an Alma Standard Sandbox based on Ex Libris provided configuration is very difficult since this configuration may be very different from the one in the customer's production environment.

   Currently Ex Libris is offering two types of Sandboxes for Alma:
   (1) "Standard" - by default included in Alma subscription pricing. This sandbox contains Ex Libris provided data and configuration
   (2) "Premium" – for addition subscription fee – this sandbox includes a full copy of the customer's data and configuration

   Refresh of the Alma sandbox environment is possible up to once a quarter, upon request. In the case of a Premium Sandbox, Ex Libris updates the customer’s Premium Sandbox with the most recent data and configuration copied from the production environment. In the case of Standard Sandbox, Ex Libris resets the Sandbox data and configuration to the original copy.

   We would like Ex Libris to propose an improved Standard Sandbox so that customers can export the configuration from the production environment with a job in order to import it in the Standard Sandbox. This Standard Sandbox would still contain Ex Libris provided data, only configuration would be copied from prod to sandbox. A Standard sandbox containing the customer's configuration would be very useful for staff training, testing of setup scenarios, new enhancements, integration with other systems, etc. This service is already proposed for Primo!

   Making testing and training in an Alma Standard Sandbox based on Ex Libris provided configuration is very difficult since this configuration may be very different from the one in the customer's production environment.

   Currently Ex Libris is offering two types of Sandboxes for Alma:
   (1) "Standard" - by default included in Alma subscription pricing. This sandbox contains Ex Libris provided data and configuration
   (2) "Premium" – for addition subscription fee – this sandbox includes a full copy of the customer's data and configuration

   Refresh of the Alma sandbox environment is possible up to once a quarter, upon request. In… more

   188 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…)
   5 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

7. Use article galaxy add-on to support resource sharing requests in Alma

   At a recent Ex Libris event I was made aware of the Article Galaxy add-on https://developers.exlibrisgroup.com/appcenter/article-galaxy-add-on/

   The information provide on the page suggests that this is only used with Rapido however we would be interested in using this feature as part of the regular Alma resource sharing process.

   Currently we make most of our document delivery requests through Reprints desk but the user process means that library staff are alerted to a resource sharing request coming in from the user via Primo, they then manage this in Alma but have to then go to reprints desk separately to make the request so it would be good if these systems could be connected in some way through the article galaxy add-on cloud app.

   What would also be helpful is if this could interrogate our electronic collections so library staff are not making requests for articles we also subscribe to which sometimes happens.

   Overall this would provide an integrated and improved resource sharing process

   At a recent Ex Libris event I was made aware of the Article Galaxy add-on https://developers.exlibrisgroup.com/appcenter/article-galaxy-add-on/

   The information provide on the page suggests that this is only used with Rapido however we would be interested in using this feature as part of the regular Alma resource sharing process.

   Currently we make most of our document delivery requests through Reprints desk but the user process means that library staff are alerted to a resource sharing request coming in from the user via Primo, they then manage this in Alma but have to then go to reprints desk separately to make… more

   4 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

8. Add Job Category as an input parameter for the Borrowing Resource Sharing rule

   Why this is desirable:
   To facilitate personal delivery for a subset of a user group (online or distance learners, for example), Alma needs an additional input parameter in the Borrowing Resource Sharing rule. Due to additional cost implications for these patrons and the delivery of their requested items, we do not want to offer this service to all users with a certain user group. Giving these patrons a separate user group, where all other loan, request, etc. rules are identical other than the personal delivery setting adds an undesirable level of complexity to the existing fulfillment rules and patron groupings. By using a job category, we can easily identify users across user groups that are eligible for special delivery services.

   In the main fulfillment unit rules for Request rules, we can already use Job Category as an input parameter to identify a special group of users to use a special TOU for just those users with that job category. We can use that rule to set pickup options to allow personal or office delivery for those users for items owned locally (patron physical item requests).

   For resource sharing requests, we have a very limited list of input parameters available to determine borrowing and delivery options, and cannot use the same kind of identifying data in the patron record as we can for local requests. We would like to be able to offer the same pickup and delivery options for both locally held items and for resource sharing requested items.

   Desired behavior:
   
   Patrons with a special job category that allows personal delivery for both local requests (patron physical item requests) and resource sharing requests will have the same delivery and pickup options that the library will define in the applicable TOUs. Resource Sharing requests will be sent to the patron’s Resource Sharing Library as defined in their patron record. The requests will follow the existing workflow for personal delivery that exists if we use User Group as the input parameter, currently. The borrowing library will intercept the requested materials and mail them to the user, as appropriate.

   Why this is desirable:
   To facilitate personal delivery for a subset of a user group (online or distance learners, for example), Alma needs an additional input parameter in the Borrowing Resource Sharing rule. Due to additional cost implications for these patrons and the delivery of their requested items, we do not want to offer this service to all users with a certain user group. Giving these patrons a separate user group, where all other loan, request, etc. rules are identical other than the personal delivery setting adds an undesirable level of complexity to the existing fulfillment rules and… more

   • 

   19 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 →
   Completed  ·  Dana Moshkovits responded

   Completed as part of the February release.

   Alma has enhanced its borrowing resource sharing rules to include Job Category

   For more information please see Release Notes

9. Ability to Bulk reassign RS requests

   We would like the ability to bulk reassign requests in Alma RS, in terms of assigning a group of requests to one staff member to process rather than having to reassign individually.

   9 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  ·  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

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

11. Allow a NR to run with the PTC job

    TL;DR:
    We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

    Background:
    In November 2024 Ex-Libris added a new functionality to the PTC job:
    MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

    Problem:
    The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
    in all other cases, the existing indicators remain.
    We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not a bug.
    I understand that other institutions have different reasons for having a NR run whenever the PTC changes a record.

    Request:
    We would like to have the option to add a normalization task to the PTC in the configuration menu, that way we will be able to fix problems that arise from this job.

    TL;DR:
    We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

    Background:
    In November 2024 Ex-Libris added a new functionality to the PTC job:
    MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
    https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

    Problem:
    The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
    in all other cases, the existing indicators remain.
    We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not… more

    46 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  ·  Metadata Management  ·  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 Counter5 - IR_A1 - Journal Article Requests to Alma/Analytics

    We suggest to add a support to the report Counter5 - IR_A1 - Journal Article Requests.
    We want to be able to harvest it via Sushi and also to be able to build reports in Analytics based on it.

    17 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  ·  Analytics  ·  Delete…  ·  Admin →
    Completed  ·  AdminNoam Fass (Product Manager, Ex Libris) responded

    In December 2020, Alma introduced support for SUSHI harvesting of multimedia reports, IR_A1 included.

    Alma product management team.

13. Allow harvesting of reports with the non-standard SN:Total_Chapter_Request metric

    I noticed that some vendors - Taylor and Francis and Springer- are adding this non-standard metric - SN:TotalChapterRequest - to their TR Master Reports. These are 2 big vendors, and these TR master reports won't load into Alma with this nonstandard metric in them.. I was hoping there is a way to accommodate them and allow them to load.

    21 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  ·  Acquisitions - 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

14. Multiple Quick-Cataloging Templates

    Scenario:
    There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.

    Problem:
    Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature, it is essential that staff are able to quickly complete record creation tasks without having to “fix” the records later because the current “Book” and “Article” templates don’t contain the correct coding.

    This lack of proper templates leads to the need for libraries to educate non-cataloging staff on why records look/work the way they do, and to create “cheat sheets” for their use in editing quick-cataloged records to match their resource type. These fixes and workarounds add a considerable amount of time to the “Quick” Cataloging workflow.

    Request:
    The ability to configure multiple Quick Cataloging templates would more effectively meet libraries’ needs. For each template, staff should be able to configure the template’s default fields and mandatory fields. The templates, once configured, should appear in a drop-down selection list alongside the existing book and article record types when the Quick Cataloging feature is used.

    Scenario:
    There are multiple workflows and purposes for which the Quick Cataloging interface is used. For example, in course reserves, staff frequently need to create records for different resource formats beyond book and article. Staff at the circulation desks need to create records any time an item brought to the desk is not found in Alma, and these resources can take any form - from sound recordings on CD to equipment like laptop chargers.

    Problem:
    Not all of these materials fit the current “book” and “article” templates provided for Quick Cataloging. To enable efficient use of the Quick Cataloging feature,… more

    165 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…)
    4 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

15. Allow for greater variety in the scheduling of export invoices.

    Currently, there are only a handful of pre-defined choices for scheduling the invoice export. None of them fit the time our accounting department set aside to work with our invoices specifically. Please allow greater flexibility when selecting a time to export/import invoices, ex> 1500 hrs on Wednesdays.

    This request comes as a result of Salesforce case #00574513.

    10 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  ·  Other  ·  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. Establishment of stronger passwords for the creation of internal ALMA/Primo users

    As an universities consortium from Galicia, CISUG, we are representing three member universities. Our univesrities have a security problem in the management the keys for internal users in Alma.

    Alma's internal authentication system allows the user can create complex passwords, but this should be a requirement, not the user's responsibility as to whether they are secure or not.

    Our request is that:

    1.  ALMA enforce passwords to be at least 8 characters long, and allow the system administrator to increase that minimum. 
       

    2.  ALMA allows to force mixed case, numbers, and special characters to créate paswords. 
       

    3.  Alma checks that the password is not composed of user data (e.g. name, surname, email, etc.) that can be easily guessed or obtained. 
       

    4.  Alma checks that the password is not the same as any of the last passwords used, nor is it formed by a concatenation of them.. 
       

    5.  Alma validates the new password against a “blacklist” of passwords that are unacceptable due to being widely used, deductible or compromised (e.g. “aaaaaaaa”, “1234abcd”, etc.). 
       

    In addition, Alma shall audit the password validation process and:

    1.  Limit the number of unsuccessful access attempts, applying an incremental delay after several failed attempts (e.g. 1 minute delay after 3 failed attempts and +10 minutes for the following ones) to make it more difficult to use bot attacks.  
       

    2.  It must be able to block the system in case of reaching a set number (e.g. blocking the user after 10 failed attempts).  
       

    And as additional methods to ensure security:

    1.  Alma shall allow to automate a forced process of periodic password change (for example yearly, semi-annually, etc).  
       

    2.  Alma shall have a mechanism that allows the administrator to request a change of passwords if there is evidence that they have been compromised.  
       

    We understand that it is more complex, we believe it would be advisable that Alma allow the user to have a security method of authentication based on two-factor authentication (2FA), as offered today by most information systems (Google, Microsoft, etc.).

    With the implementation of these requirements, users would have their personal data more secure (both in terms of access to the system itself, as well as in anticipation of it serving as an entry vector for other tools), and the institutions would thus comply with the precepts of the ENS Spanish "National Security Scheme" in terms of minimum cybersecurity requirements.

    As an universities consortium from Galicia, CISUG, we are representing three member universities. Our univesrities have a security problem in the management the keys for internal users in Alma.

    Alma's internal authentication system allows the user can create complex passwords, but this should be a requirement, not the user's responsibility as to whether they are secure or not.

    Our request is that:

    1.  ALMA enforce passwords to be at least 8 characters long, and allow the system administrator to increase that minimum. 
       

    2.  ALMA allows to force mixed case, numbers, and special characters to créate paswords. 
       

    3.  Alma checks that the password is

       … more
    52 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

17. SUSHI harvesting for JSTOR

    I noticed that our SUSHI harvesting for JSTOR hadn't worked successfully since May 2023. The requests for reports were coming back with this message:

    {"Code": 1011, "Severity": "Warning", "Message": "Report Queued for Processing", "Help_URL": "https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview", "Data": "Successful request. You must re-request this report to receive data. Please allow 1 hour for processing before retrying."}

    So I reviewed the information here:
    https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview

    This page makes it clear that this is expected behaviour.

    I ran a custom harvest for June-Sept 2023 and it failed (as expected).
    I ran a second custom harvest an hour later and it succeeded.

    I'm not aware of any way to set this up in a scheduled way for this specific vendor, but it sure would be nice.

    I noticed that our SUSHI harvesting for JSTOR hadn't worked successfully since May 2023. The requests for reports were coming back with this message:

    {"Code": 1011, "Severity": "Warning", "Message": "Report Queued for Processing", "Help_URL": "https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview", "Data": "Successful request. You must re-request this report to receive data. Please allow 1 hour for processing before retrying."}

    So I reviewed the information here:
    https://support.jstor.org/hc/en-us/articles/360015483214-SUSHI-reports-COUNTER-5-overview

    This page makes it clear that this is expected behaviour.

    I ran a custom harvest for June-Sept 2023 and it failed (as expected).
    I ran a second custom harvest an hour later and it… more

    10 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  ·  Acquisition - Vendors  ·  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

18. Conditional Status and Email Message for Non-ISO Partners

    We would like for to be able to send Conditional Messages by Email and for the Request Status to automatically change to Conditional when working with Non-ISO partners: see Jan. 2019 Release for ISO partners

    7 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  ·  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

19. Improve po_line_remove_interested_users_job

    The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.

    We request that:
    A. Institutions have the ability to set a delay on the job based on the date the PO line was closed. (E.g., the job runs weekly, but only deletes Interested Users in PO lines that were closed X number of days ago);
    B. The job is designed to run on PO lines that are closed but no longer in the department or in a work order (eliminating the risk that Interested Users will be deleted from a closed PO line before the item has left the department);
    C. Interested Users that are deleted in PO lines are also scrubbed from Analytics.

    The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.

    We request that:
    A. Institutions have the ability to set a delay on the job based on the date the PO line was closed.… more

    44 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  ·  Acquisition - PO & POLine  ·  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

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