1663 results found

1. Display related holdings for monographs only for the 773 $w relation and not for the 8xx $w relation

   When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.

   What we wish to achieve is the following:

   When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of the record linked via 773 $w is displayed.

   When records contain a series link (8xx $w) or a related record (76x/77x/78x $w - exception: 773), we do wish to display a link to the related record (via system number), but not the related holding.

   Right now, the configuration does not offer the needed flexibility.

   When filtering to a certain location via facets, you often get results from other locations too, which is unexpected from patrons perspective in many cases. This is caused by the current related records setting which is also taking locations with related records into account. The display is correct for analytical records without inventory (book chapters and articles), but not for the other monographical resources.

   What we wish to achieve is the following:

   When the record of a book chapter, journal issue or journal article (i.e. a record containing a 773 field with $w) is viewed in Primo, the holding of… more

   665 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…)
   26 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
   AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello all,

   We want to let you know that this request is currently under analysis by the Alma team. We understand its importance and are carefully reviewing the details to determine the best path forward. We will share an update with you as soon as a decision has been made. Thank you for your patience and continued engagement.

   Erez

2. Better management of serial prediction when publication frequency changes

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if Alma could change the description (number, date, …) only for the items that are impacted by a new publication during the year. We would just have to fill the « Next prediction item’s information » with the new frequency.
   This enhancement would save a lot of time to catalogers.

   Sometimes providers change a journal’s publication frequency throughout the year. So, the prediction’s pattern selected / elaborated at the beginning of the year doesn’t work anymore in Alma. One part of predictions (date of receipt) will be ok until the change but all other predicted items will be false. Now, we can revise the prediction during the year but we must erase the items already received. We can also leave the prediction defined at the beginning of the year and edit manually the false items from the time of the prediction change.

   It would save a lot of time if… more

   421 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…)
   13 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

   Thank you for the suggested idea.

   After reading it carefully, I understand that the main pain point here is the removal/fix of items already received.

   To be more specific, the description of already received items should be updated to reflect the new pattern.

   
   

   1. Is this understanding correct?
   2. How often such change happens?
   3. Can you please add examples of the existing description and the needed update?
   4. Can the 'Update items using Excel load' CloudApp be utilized for fixing the description? see https://developers.exlibrisgroup.com/appcenter/item-updater-by-excel/

   
   

   Thanks for the collaboration,

   Tamar Fuches

   Alma product

3. Reminder when opening hours are expiring

   When you add standard opening hourse into the Library / Institution calendar it defaults to setting the expiry for the hours 3 years ahead. This is good but it would be useful to get a reminder to move them on when it's getting close to the expiry date.

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

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

   •  

   256 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

5. Save certain subfields from being overwritten via F3 and PTC

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields might be used for various types of additional information, based on the field number and the cataloguing tradition and/or authority file linked to, it would be sensible to allow to define specific subfields to be exempt based on the field number, but also the authority file in use ($2).

   When linking names, subjects etc. from authority files in various BIB fields, some cataloguing conventions require giving additional information in certain cases.

   One example for such a requirement, stemming from the German speaking countries, is to add the time and place of an auction when linking to the genre/form term “auction catalogs” in BIB field 655 (see attached screenshot). This additional information is, of course, specific for each BIB record and must not be overwritten or deleted, if at a later point in time either PTC processes said BIB record or a colleague invokes the F3 functionality.

   Since different subfields… more

   •  

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

6. Indication that shows I edited an open record

   Icons in MD-Editor only show if a record has been saved or not. I would like to have an indication to see if the record has been edited by me after I opened it.

   238 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…)
   7 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
   AdminErez Shabo (Senior Product Owner, Ex Libris) responded

   Hello all,

   We are currently reviewing it to assess its technical feasibility and implications. We’ll follow up once we have more clarity.

7. Allow batch deletion of user notes

   It's possible to add notes to user records in batch using the "Update/Notify Users" job on a set of users. It would be helpful if we could also batch delete notes on user records.

   There are occasions when we have subsets of users who receive special permissions to check out subsets of materials (e.g. students in a specific class who are the only people allowed to use specific equipment or reserve items, collections/materials where we require a signed agreement on file from the user to allow access). In these situations, we add notes to the user record to indicate whether a specific user may use a specific physical resource during a set period of time, such as an academic term. We would like to be able to delete these notes in batch, rather than having to manually edit individual user records-- of which there may be several hundred-- to remove the note that is no longer applicable.

   Ideally, the job would allow operators to delete only those user notes that contain text specified by the operator. (e.g. Delete user notes that contain the phrase "Fall 2016" or delete user notes that contain the word "approved")

   It's possible to add notes to user records in batch using the "Update/Notify Users" job on a set of users. It would be helpful if we could also batch delete notes on user records.

   There are occasions when we have subsets of users who receive special permissions to check out subsets of materials (e.g. students in a specific class who are the only people allowed to use specific equipment or reserve items, collections/materials where we require a signed agreement on file from the user to allow access). In these situations, we add notes to the user record to indicate whether… more

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

8. Stop the practice of showing funds for 'in review' invoices as expenditure.

   Current Alma practice is that EDI invoices automatically load into Alma and expend from a fund whilst still 'in review' and before the 'approval' stage.

   Below are some examples where the practice of expending a fund whilst the invoice is still 'in review' is causing us issues:

   1. We have full end-to-end invoice integration from our suppliers, via Alma and into Agresso. We don't send through manual invoices for payment. Our invoice data is automatically transferred through to Agresso every evening once an invoice has been approved. Only those invoices that have moved out of review are included in the export. Any invoices 'in review' will not be in the export but will be showing as expended on our system. This means that Agresso and Alma will always be out of step whilst we have invoices 'in review'. This makes it impossible to reconcile Alma and Agresso.

   2. Some invoices have over 200 lines and it may take us some days to work through each transaction. There may be issues with incomplete or inaccurate data. We have to make a few manual amendments in order to ensure that the Agresso transfer completes successfully. Only once all of that is done do we 'approve'. Whilst this is happening our Alma and Agresso systems are out of sync. What is the point of the approval step?

   3. We are working with IT on enabling the accrual accounting functionality so that our Finance Team don't have to maintain a separate spreadsheet of prepayments and meet monthly to reconcile. There is little benefit to be gained from working on this functionality if, once again, the two systems are always out of sync. We can't reliably turn up to meetings to discuss our accounts when the Alma reported expenditure includes invoices that aren't yet paid.

   4. If an invoice arrives that doesn't have an Alma PO number on it, the transaction amount is expended but because there is no PO to match to the amount remains encumbered too.

   Any 'in review' invoices should remain as 'encumbrance' until they have been 'approved' or have another 'pending expenditure' type invoice status.

   Current Alma practice is that EDI invoices automatically load into Alma and expend from a fund whilst still 'in review' and before the 'approval' stage.

   Below are some examples where the practice of expending a fund whilst the invoice is still 'in review' is causing us issues:

   1. We have full end-to-end invoice integration from our suppliers, via Alma and into Agresso. We don't send through manual invoices for payment. Our invoice data is automatically transferred through to Agresso every evening once an invoice has been approved. Only those invoices that have moved out of review are included in the export.… more

   213 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…)
   13 comments  ·  Acquisition - Invoices  ·  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,

   Thanks you for suggesting this idea.

   After reading it carefully, my understanding is that the need is for a new “entity” which will serve as a “bridge” between encumbrance and expenditure. This bridge will be named “Pending invoices”.

   Any POL which is invoiced will be disencumbered and the amount will be added to the “pending invoices balance”. When an invoice is approved, the amount should be reduced from the “pending invoices balance” and added as an expenditure.

   
   

   1. Is this understanding correct?
   2. Do you think that the definition of using this "bridge" should be in institution level, or might be different from invoice to invoice?

   
   

   Please note that this is a complicated addition. We will need to define the behavior in rollover, and in any place that changes balances etc.

   
   

   Thanks for your collaboration,

   Tamar Fuches

   Alma product team

9. Add more flexibility in Request TOU Pickup Locations policy

   We’d like more flexibility in Request TOU Pickup Locations policy.

   We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between some libraries.

   Currently, we cannot achieve the above requirement in Alma. If more options are added to the Pickup Locations policy, libraries in the similar situation will also benefit.

   For example, it would be more flexible if there are “In List (where we can select one or more libraries in our Institution)”, “In other Campus”, or “In other Libraries” options in the Request TOU Pickup Locations policy.

   Another idea is to allow staff to override pickup locations and deliver-to relationship policies so that they can place any pickup request on behalf of patrons when appropriate. It will also be beneficial for those who need special assistance.

   We’d like more flexibility in Request TOU Pickup Locations policy.

   We have more than 20 libraries and most of them are located within walking distance. Therefore, we want our patrons to go directly to those libraries instead of placing pickup requests and limit the patrons who can place such requests. Otherwise, the number of requests will become too large to handle and logistics and management cost will become enormous. Moreover, it’s not time efficient. If users go directly, they can borrow immediately, but it may take 1-2 days to deliver since there is no direct route between some libraries.

   Currently,… more

   212 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…)
   18 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

10. ORCID iD Integration in Info Card for Contributor Page in Alma

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the person.
    • Wikidata cache is updated in Alma on a weekly basis.

    Enhancement Request: We propose an additional feature to further enrich the Info Card functionality. Specifically, we request that when an ORCID iD in the form of a URI is present in either the LC name authority record or Wikidata for the author, the following should occur:

    • Display the ORCID iD URI: The ORCID iD URI should be prominently displayed in the Info Card.
    • Make the ORCID iD URI Resolvable: The URI should be clickable and resolvable directly within the Info Card in both Alma and Primo.

    Benefits: Integrating ORCID iD URIs will enhance the discoverability of author contributions and facilitate seamless access to their research profiles, thereby improving the overall user experience.

    Thank you for considering this enhancement to the Info Card feature. We believe this addition will greatly benefit users and contribute to the ongoing development of Alma and Primo.

    Background: In August, ExLibris implemented the Info Card feature for contributor pages in Alma, which appears under specific conditions related to linked authority records. This enhancement has significantly improved the visibility of contributor information.

    Current Conditions for Info Card Display:

    • A person is linked to an LC Names authority for a personal name.
    • A person is linked to a Name authority that exists in VIAF and can be linked to an LC Name authority for a personal name.
    • Information on the person exists in LC Names and Wikidata, with at least two fields containing information beyond the name of the… more
    204 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  ·  Linked Data  ·  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
    AdminAdina Marciano (Admin, Ex Libris) responded

    Thank you for the suggested idea. We see its value and will consider it in the future. This development requires integration with third-party providers, and we will need to investigate the possibility of this development.

11. Make it possible to add Vendor Interface fields and customize field value options for existing fields

    In Alma, Vendor Interfaces in Vendor records are the place designed to hold e-resources administrative information, such as contact information, administrative details, and usage statistics details. However, the fields available to libraries were developed several years ago, are not customizable, and do not reflect the complexity of modern e-resources management. Different types of institutions have different needs and want to record different types of information, so adding a few new fields for all libraries isn't an ideal solution.

    Instead, this request is for libraries to have the ability to add and manage Vendor Interface fields. Libraries should be able to create new fields to reflect their own local needs, and these new fields should all be viewable in analytics. For example, we'd like to store accessibility information and COUNTER version information for each vendor interface, but there is no fields dedicated to this type of information (other libraries might wish to store other types of information). Also, for both new and existing fields, libraries should be able to manage their own controlled field values lists. For example, for the field "Implemented Authorization Method," the select list of controlled values is currently not customizable does not include modern authentication methods such as Shibboleth, SSO, or OpenAthens. We would like to be able to add the field values we need for these and other fields.

    This will make it possible to e-resources librarians to flexibly respond to new developments in the field and track the information they need in Alma (instead of relying on external shadow systems and spreadsheets). This functionality is already in place in Alma for licenses (see https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/020Acquisitions/040Configuring_Acquisitions/170Managing_License_Terms). Like License terms, we should be able to add new terms, choose the term type (including free text, yes/no, or controlled vocabulary, and then we can create the controlled vocabulary) and choose the Vendor Interface record section in which the term will appear. I will attach a mockup of what the Add Vendor Interface Term form should look like (based on the Add License Term form).

    In Alma, Vendor Interfaces in Vendor records are the place designed to hold e-resources administrative information, such as contact information, administrative details, and usage statistics details. However, the fields available to libraries were developed several years ago, are not customizable, and do not reflect the complexity of modern e-resources management. Different types of institutions have different needs and want to record different types of information, so adding a few new fields for all libraries isn't an ideal solution.

    Instead, this request is for libraries to have the ability to add and manage Vendor Interface fields. Libraries should be able to… more

    •  

    203 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…)
    6 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
    AdminTamar Fuches (Alma product manager, Ex Libris) responded

    Hi Elizabeth, Katie, and everyone,

    Thanks so much for sharing this idea!

    From what I understand, it includes two main parts:

    1. Allowing institutions to edit the list of values in various fields, with a specific example being the “Implemented Authorization Method” field.
    2. Adding more fields and making them reportable in Analytics, along with a request for a flexible mechanism to support this.

    Regarding the second point — adding a flexible mechanism is quite a complex change and could impact the timeline.

    If you can point out around three specific fields that are most important to add first, it might be easier.

    
    

    Looking forward to hearing your thoughts!

    Thanks again,

    Tamar

12. Sorting Authority Task List

    It would be highly helpful to have a sorting filter in the Authority Task List that would allow us to sort the list by Fields (e.g. 100's,600's, 700's, 830's,): Personal Names, Corporations/Conferences, Subject, Title, Uniform Titles, and Series. This way work loads can be created and assigned for these specific areas. As things are now, all items are mixed together and it takes far too much time to find/create a single list.

    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…)
    4 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
    AdminErez Shabo (Senior Product Owner, Ex Libris) responded

    Hello all,

    We are currently reviewing it to assess its technical feasibility and implications. We’ll follow up once we have more clarity.

    
    

13. 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 the… 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

14. Separate the ability to delete holdings and items so they depend on different privileges and roles.

    Currently, the ability to delete holdings with no inventory and to withdraw items is controlled by the same user role and privilege. 'Physical Inventory Operator Extended' role, 'Physical Inventory Delete' privelege.

    This idea proposes to separate those functions into 2 roles:
    one will be able to delete empty holdings records (and may be assigned to a broader population of users)
    and the other (the 'extended' role) will be able to withdraw items - which is considered a more sensitive action.

    ---

    This idea was edited by the Alma product team for clarity, see original phrasing below

    Dear all
    The 'Delete Holdings' link in the 'List of Holdings' page, which was formerly visible to users with the 'Physical Inventory Operator' role, is now visible only to users who have the 'Physical Inventory Operator Extended' role.

    This change is a problem because not all the operators can have the physical Inventory Operator Extended role: this role allows operators to delete copies and it is quite dangerous.
    It would be better for us that operators with the physical inventory role keep the permission to move copies from an holding to another and then delete the empty holding. (let’s think of a correction of call numbers)
    We propose the creation of a second Physical Inventory Operators’ role :
    One without the possibility of delete empty holdings
    and another one with the possibility of delete them.
    So that, according to the job that operators have to do, they could keep doing the work deleting empty holdings

    Currently, the ability to delete holdings with no inventory and to withdraw items is controlled by the same user role and privilege. 'Physical Inventory Operator Extended' role, 'Physical Inventory Delete' privelege.

    This idea proposes to separate those functions into 2 roles:
    one will be able to delete empty holdings records (and may be assigned to a broader population of users)
    and the other (the 'extended' role) will be able to withdraw items - which is considered a more sensitive action.

    ---

    This idea was edited by the Alma product team for clarity, see original phrasing below

    Dear all
    The 'Delete Holdings'… more

    181 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 - 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 community,

    The title and description of this idea were updated to better reflect the need. Please let us know if you have comments on this.

    
    

    Thanks,

    Tamar Fuches,

    Alma development team

15. Provide multiple hold pickup options within a single Alma library

    We'd like to provide, within a single Alma library, the following pickup location/delivery options to our users: locker, circulation desk, or mail to home. At present, this is only possible through the creation of additional libraries.

    179 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…)
    9 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

16. Enable bulk due date changes based on a set of items listed by barcode

    We've had occasions where it would have been useful to be able to create a set of items, for example, in Alma Analytics. Then to take that set of items, e.g. a CSV or Excel file listing the barcodes, and then to update the due dates of all those items, to a new fixed value.

    This is similar to the current Bulk Due Date Change functionality, but with the addition of uploading a list of items to change.

    Regards,

    Ciaran

    The University of Manchester Library

    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…)
    9 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

17. Request letter

    We would like to be able to send a user a notification about a request immediately after placing the request. The notice would give basic information about the status of the request. Something along the lines of the "interested in" letter. Running a request report once a day is insufficient for our operations.

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

18. Add a tab "re-loan" to Patron Services to return and re-loan items in one step

    An additional tab (e.g. "re-loan" or "Wiederausleihe" in German) would be a valuable improvement to the Patron Services page.
    The goal of this tab is the returning and re-loaning of an item to the patron in one step, with a pop-up warning if there are requests present in the request queue.
    The option of a re-loan tab would be a big help in cases where large amounts of items are reloaned to the same person when the items reach the maximum amount of renewals. The additional tab would make the process easier, less error-prone and especially faster.

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

19. Interested In Letter – improvement to the usability

    When working on a purchase request, you can tick a box if you would like to notify the patron upon receiving/activation, and upon cancellation.

    OTB the Interested In Letter sends the same message when the request is received or cancelled. The letter in use does not seem designed for the cancellation message.

    This creates a discrepancy between what we choose to notify the patron of, and what we are actually able to communicate.

    Since we neither have access to the message table used as an input to this letter, or the opportunity to differentiate by using labels, we are forced to hard code most of the editing. This applies to both different messages, and different languages. This is tiresome work, and hard to maintain.

    We would like a subject line that accurately reflects the content of the email (e.g., "Library Order Cancelled" or “Item received/activated”).

    The same issue applies for the message to the patron (label = Youwerespecify). We need to differ between each possible use of the letter.

    One solution would be to add labels in the table. For instance:
    Subjectactivated
    Subjectreceived
    Subject_cancelled

    In addition to the Youwerespecify label, we would also like:
    Messageactivated
    Messagereceived
    Message_cancelled

    The XSL must then be enriched to integrate these new labels.

    A labels table designed for all three scenarios would also make it easier to edit all languages in use.

    When working on a purchase request, you can tick a box if you would like to notify the patron upon receiving/activation, and upon cancellation.

    OTB the Interested In Letter sends the same message when the request is received or cancelled. The letter in use does not seem designed for the cancellation message.

    This creates a discrepancy between what we choose to notify the patron of, and what we are actually able to communicate.

    Since we neither have access to the message table used as an input to this letter, or the opportunity to differentiate by using labels, we are forced… more

    174 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
    AdminTamar Fuches (Alma product manager, Ex Libris) responded

    Hi Heidi and all,

    Thanks for sharing this idea!

    I have read it carefully, and would like to make sure that I understand it:

    
    

    Current situation:

    Currently there are one "Subject" label and one "Message" label that can be configured. However, the letter is used in multiple use cases, for each a separate subject and message are needed.

    
    

    Desired outcome

    Need to have separate labels, according to the use case:

    Subject_activated

    Subject_received

    Subject_cancelled

    Message_activated

    Message_received

    Message_cancelled

    This way the letter wording can reflect the actual use case.

    
    

    Please let me know if this understanding is correct.

    
    

    Thanks,

    Tamar Fuches

    Alma product team

20. Ability to create a chosen quantity of predictions

    As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.

    It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at times to find the item you are looking for. Also, due to variations in publishing schedules and the general inconsistent nature of periodicals, creating weekly predictions a year in advance often results in inaccurate predictions which will need to be modified later.

    As someone who manages serial subscriptions, I would like the ability to choose the quantity of predictions I create for any given holdings record. This would allow for quicker navigation of list of items, and reduce the number of inaccurate predictions.

    It is not always desired to predict an entire year’s worth of predictions (which currently is the only option). Depending on the publishing frequency and the number of copies of a subscription, we can have 11 pages of predictions in a list of items, in addition to the received items. This greatly increases the amount of clicking needed at… more

    171 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 →
    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