1750 results found

1. Ful Resource Request Slip Letter split in two

   We would like the Ful Resource Request Slip Letter printout to split in two: one letter for staff when picking material from stacks, and one for use on the hold shelf for end users to see. These two functions are difficult to combine since staff need to know who the requester is at the same time as GDPR makes anonymization of the hold shelf slip necessary.

   We currently try to solve this by using the Ful Hold Shelf Request Slip Letter as the hold shelf slip. But this printout is meant only for staff and so is printed in the interface language of the staff. We have users in many languages and need both Swedish and English printouts.

   An extra complication occurred when we tried to stop the system from printing the Ful Resource Request Slip Letter for certain locations. We found “Request Pickup Configuration” and the “Show in 'Pick From Shelf' list parameter”. When trying it out it seemed to do what we wanted, the requests did not show up in the ‘Pick from shelf’ list. But when we tried this live in Alma, the “Ful Resource Request Slip Letter” was printed. The “Show in 'Pick From Shelf' list” parameter only does half of the job, the request is not shown in the list but the printout is generated.

   We asked support and the answer was that “the printing is expected unless you deactivate the slip. The request does not go into a pick from shelf status, but the slip is expected to be used not only for pick from shelf but also as a hold shelf slip".

   We would like the Ful Resource Request Slip Letter printout to split in two: one letter for staff when picking material from stacks, and one for use on the hold shelf for end users to see. These two functions are difficult to combine since staff need to know who the requester is at the same time as GDPR makes anonymization of the hold shelf slip necessary.

   We currently try to solve this by using the Ful Hold Shelf Request Slip Letter as the hold shelf slip. But this printout is meant only for staff and so is printed in the… more

   4 votes

   Vote 0 votes 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. Enhance the comprehensiveness of Analytics of usage analysis

   For some vendors, it may have sub-databases in the subscriptions and collect usage for a particular database and the titles within seems not possible currently by Analytics. Though there’s a “Platform” field in Analytics, it did not separate the figures between different databases for a single vendor. It's strongly recommended to enhance the comprehensiveness of Analytics and enhance the functionality of usage analysis.

   24 votes

   Vote 0 votes 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  ·  Analytics  ·  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. Flag individual articles in Alma as being unavailable.

   ExLibris cannot verify accuracy between supplied metadata and a referenced database. As a result, there are times when an article is listed in Primo as available online; However, when the patron tries to retrieve the article, the database returns a not found error. This has been frustrating for our patrons.
   Currently there is no way to flag an individual article as being unavailable. As a result, this becomes a recurring error for our patrons; with no option to correct.
   Suggest providing a way to:
   1. flag individual articles as available / not available by database
   2. date and notes on why the article was flagged
   3. ability to delete the flag when no longer needed.

   ExLibris cannot verify accuracy between supplied metadata and a referenced database. As a result, there are times when an article is listed in Primo as available online; However, when the patron tries to retrieve the article, the database returns a not found error. This has been frustrating for our patrons.
   Currently there is no way to flag an individual article as being unavailable. As a result, this becomes a recurring error for our patrons; with no option to correct.
   Suggest providing a way to:
   1. flag individual articles as available / not available by database
   2. date and notes on… more

   3 votes

   Vote 0 votes 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 - 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

4. More options to limit access to private patron information for student employees

   Some libraries hire students as part-time staff at the circulation desks or helpdesks. Per the institution or library policies, for privacy reasons, student employees may not be allowed to search for Alma users or to view the contact details of staff members or other student users.

   Currently, access to contact details and searching for users are by default possible to any Alma user with Fulfillment roles. Disabling the ALLOW-USERS-SEARCH privilege can prevent access to users list in Manage Patron Services and auto-complete search in same page, but it does not affect the persistent search for users or access to Admin > Manage Users.

   We would like more flexibility here and to be able to limit information accessible to student employees. We would like to prevent them (1) to search for users and access to Admin > Manage Users; (2) view the contact details, including in the Contact Information Pop-Up, like postal addresses, email addresses, and phone numbers.

   This could be achieved with additional privileges, similar to ALLOW-USERS-SEARCH, that each library could disable, or via new configuration options via User Management > General >Manage Operator Details Visibility.

   Some libraries hire students as part-time staff at the circulation desks or helpdesks. Per the institution or library policies, for privacy reasons, student employees may not be allowed to search for Alma users or to view the contact details of staff members or other student users.

   Currently, access to contact details and searching for users are by default possible to any Alma user with Fulfillment roles. Disabling the ALLOW-USERS-SEARCH privilege can prevent access to users list in Manage Patron Services and auto-complete search in same page, but it does not affect the persistent search for users or access to Admin… more

   86 votes

   Vote 0 votes 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  ·  User 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

5. Add Purchase Requests to blocked actions

   We would like to prevent blocked users from submitting Purchase Requests. Although it is possible to ask Ex Libris to configure a blocked action for Resource Sharing Requests, it is not possible to do this for Purchase Requests. It would be useful to have a blocked action for Purchase Requests that we could use in Block Definitions.

   5 votes

   Vote 0 votes 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

6. Choose start month in Alma Analytics schedule

   Alma Analytics has been improved by a lot in ways of scheduling reports. But I am still missing a way to choose a start month when scheduling a quarterly or bimonthly report.

   You can choose a recurrence pattern (eg. monthly, recur every nth month), but there is no way to choose a month for the next run. Each change in recipients or touching the analytics object may start a new interval.

   When choosing a weekly interval, you can also choose a weekday. An option for choosing a month should be added for monthly schedules.

   7 votes

   Vote 0 votes 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  ·  Analytics  ·  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. Allow to add a fund to PO Lines for donated or free items

   We must add a fund to each order line for accounting reasons, even if the items are free of charge.

   We use a workaround similar to the workflow described in the following article.
   https://knowledge.exlibrisgroup.com/Alma/Knowledge_Articles/How_to_associate_PO_Lines_for_donated_or_free_items_with_a_fund

   It would be very helpful to be able to add a budget even if the price is zero.

   8 votes

   Vote 0 votes 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 - Purchase 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

8. Export funds from a PO Line

   Allow the funds codes, amounts, and percentages, on a specific order to be exportable.
   We often need to communicate these amounts with selectors, and this ensures no errors. The old interface allowed copy/paste into a table, and this has been lost with the new interface

   4 votes

   Vote 0 votes 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 - 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

9. Add interested user to order template

   We would like to add the ability to save interested users to the ordering templates. This will save us a lot of time and clicks.

   3 votes

   Vote 0 votes 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 - PO & POLine  ·  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

10. Streamline PO Line Renewals &

    For PO lines for subscriptions that will be renewed, currently the funding, date, and cost information fields need to be manually changed for each term of the subscription. It would be helpful to be able to duplicate/indicate the new information for each year/term period and retain the old info for analytics/reporting, calculating increases, etc. If rollover functionality were to be added for the funds(s) and dates based on the term details, that would also be fantastic.

    0 votes

    Vote 0 votes 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 - PO & POLine  ·  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. Ability to change barcodes directly from the list of items (under Receive – One time / Continuous - Manage items)

    In the list of items in the receive screen it looks as though barcodes are editable directly from the list, this is not the case, as you manually must edit each item to change the barcode. It would mean less clicks if you could edit the barcode directly from the list, it would also be less confusing since it in the current design looks as if you should be able to do this. In the current design you can edit the text in the barcode field in the list, but any changes are not saved.

    If the ability to change barcodes directly from the list were to be implemented it would have to also include a check for duplicate barcodes, like it does in the item editor.

    In the list of items in the receive screen it looks as though barcodes are editable directly from the list, this is not the case, as you manually must edit each item to change the barcode. It would mean less clicks if you could edit the barcode directly from the list, it would also be less confusing since it in the current design looks as if you should be able to do this. In the current design you can edit the text in the barcode field in the list, but any changes are not saved.

    If the ability to change… more

    •  

    28 votes

    Vote 0 votes 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 - Receiving  ·  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. Creating expected items in status acquisition without using prediction pattern

    In the current workflow for periodicals, when using predicted items, there is no easy way to add just one predicted item. This means that if we make a mistake or there is a change in the publication pattern, for example we receive the wrong item/delete the wrong item, or that a periodical is published as a combined issue (ex: issue 2 and 3 together, as number 2/3 2023), there is no easy way to fix it. We must then create predicted items for that whole year again which involves editing “next predicted item information” in the metadata editor, opening and saving the predicted items, and then deleting the duplicate predicted items which are then created. This is particularly cumbersome and time-consuming when the title has a high number of predicted items. This adds to the already complicated and time-consuming process of creating predicted items in Alma.

    One solution to this could be to add an option like “Add item”, which is found under “holding – view items” in the repository search, but then to have the item be created with the process type “Acquisition”. It would also have to be connected to a POL so that it would be possible to claim, for periodicals this would be solved since the POL is on the holding level.

    This option should be available both in the list of items on the bibliographic record (repository search), and if possible in the receive screen (Acquisition – receive – continuous – manage items).

    In the current workflow for periodicals, when using predicted items, there is no easy way to add just one predicted item. This means that if we make a mistake or there is a change in the publication pattern, for example we receive the wrong item/delete the wrong item, or that a periodical is published as a combined issue (ex: issue 2 and 3 together, as number 2/3 2023), there is no easy way to fix it. We must then create predicted items for that whole year again which involves editing “next predicted item information” in the metadata editor, opening and… more

    40 votes

    Vote 0 votes 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 - Receiving  ·  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

13. Ability to aggregate claims to one vendor should be made available for Legal deposit

    For the acquisition method “Purchase” the letter “PO line claim letter” is used, for the acquisition method “Legal deposit” and “Legal deposit - without letter” the “Legal deposit claim letter” is used. For the “Purchase” acquisition method an additional claim letter is available “PO Line Aggregated Claim Letter”, which in the event of there being more than one claim to the same vendor aggregates these into one letter. The same is not available for legal deposit. This means that when we have one large vendor (ex: supplier delivering on behalf of many different publishers), which is common for legal deposit, they receive one e-mail per claim. We want an aggregated claim letter to also be created for legal deposit orders.

    For the acquisition method “Purchase” the letter “PO line claim letter” is used, for the acquisition method “Legal deposit” and “Legal deposit - without letter” the “Legal deposit claim letter” is used. For the “Purchase” acquisition method an additional claim letter is available “PO Line Aggregated Claim Letter”, which in the event of there being more than one claim to the same vendor aggregates these into one letter. The same is not available for legal deposit. This means that when we have one large vendor (ex: supplier delivering on behalf of many different publishers), which is common for legal deposit,… more

    32 votes

    Vote 0 votes 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. Add filter for presence of POL to electronic collections portfolio lists

    Currently, the only way to determine which portfolios in an electronic collection have an attached POL is to export the portfolio list and check column Z "Orders" in the Excel file. You must then search each portfolio individually to act upon its POL. A filter in the portfolio list for "POL attached" would be much more efficient.

    1 vote

    Vote 0 votes 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 - Electronic  ·  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

15. Add sync option to Alma sandbox environment

    Could we add a 'Sync' button on each configuration page to apply changes from the sandbox environment to the production environment?

    This would be beneficial for modifications like CSS changes, terms of use, fulfillment rules, mapping, etc., and it would reduce the risk of human error during the transition.

    Also, having a sync option from the production environment into the sandbox environment would be great for troubleshooting possible issues.

    Thanks.

    8 votes

    Vote 0 votes 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

16. Add support for System for Cross-domain Identity Management (SCIM) standard

    System for Cross-domain Identity Management (SCIM) is a standard for automating the exchange of user identity information between identity domains, or IT systems. Supporting this standard would allow for better automation and SIS integration for institutions using Alma.

    https://en.wikipedia.org/wiki/System_for_Cross-domain_Identity_Management

    7 votes

    Vote 0 votes 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

17. Monitor Requests & Item Processes - Library Independence

    It is possible to cancel processes at libraries that you do not have any role at using the Monitor Requests & Item Processes screen. A cancel button appears next to every request.

    Patron physical item requests are correctly only visible based on your role but other processes such as work orders are visible and cancellable by all staff with access to the Monitor Requests & Item Processes page.

    Visibility is not a problem as the data isn't private, but the ability to cancel a process should be limited by the scope of the role.

    1 vote

    Vote 0 votes 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  ·  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

18. Digital Marketing Agency

    N2N Systems is a leading digital marketing agency that focuses on innovation and results. They understand the ever-evolving digital landscape and offer customized solutions to help businesses boost their online presence, increase brand awareness, and drive conversions. N2N Systems uses data-driven insights to adapt strategies in real-time for optimal performance. Their comprehensive suite of services includes SEO, social media marketing, PPC advertising, and content creation. They believe in collaboration and building lasting partnerships with clients. N2N Systems is the go-to partner for businesses aspiring to thrive in the digital age. More Info: https://www.n2nsystems.co.in/ppc-management/

    3 votes

    Vote 0 votes 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 →
    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. 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 0 votes 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

20. Change e-mail sender address for Collection Contribution Letter

    We have observed that Alma sends a “Collection Contribution Status Letter” for CZ contributions, which is different from the ones we can configure in our IZ letter administration. The letter that Alma sends comes from the “Alma Community Zone”, which prevents us from modifying any labels, HTML or sender addresses for these letters. This causes an issue for us because the e-mail sender is set to the Ex Libris’ default non-valid e-mail address “your.department@organization.com”. This sender address is flagged and filtered by our campus wide spam detection software.

    We do not require a personalized or customizable sender address, but we do need a valid one to avoid the spam detection. The domain “organization.com” is clearly not suitable for any production environment.

    We have observed that Alma sends a “Collection Contribution Status Letter” for CZ contributions, which is different from the ones we can configure in our IZ letter administration. The letter that Alma sends comes from the “Alma Community Zone”, which prevents us from modifying any labels, HTML or sender addresses for these letters. This causes an issue for us because the e-mail sender is set to the Ex Libris’ default non-valid e-mail address “your.department@organization.com”. This sender address is flagged and filtered by our campus wide spam detection software.

    We do not require a personalized or customizable sender address,… more

    14 votes

    Vote 0 votes 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