1903 results found

1. Open / Closed Stacks Request Possibilities Priority

   Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

   In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

   We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item from Discovery, request being placed on the closed stack item.
   For more technical information: SF Case 06737777.

   Thank you very much in advance, best regards,
   Renaud Arlettaz for SLSP

   Currently, when a library owns a title in several copies, and that some of these copies are dispatched between physical locations attached to both closed and open stacks fulfillment unit, all copies behave like open stacks.

   In other terms: if we have two items, one in open-stacks and one in closed-stacks, title-level requesting is blocked as long as the open-stacks item is available. Hence, open stacks configuration takes precedence over the closed one.

   We would like that whenever an available item is stored in a closed stacks location alongside other open stacks available items, users still can request the item… more

   67 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…)
   7 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. Improvements to Pick From Shelf list needed

   Currently our staff spend too much time managing requests. Improvements to the interface for Pick From Shelf would help in some of these cases. We would like to see:

   1. A search box.

   Very often we need to target a particular request, a task made more difficult by less than ideal facets (see #2). Search functionality exists under Monitor Requests & Item Processes, but not all options for handling requests are available in that view (such as "Skip Location").

   1. Better facets.

   Two of the facets available in the Monitor Requests & Item Processes view would be great for Pick from Shelf: "Request/Process Type" and "Pick-up Location". Currently we have a need to facet out temporary move requests in order to view only the patron physical item requests. To do so in Pick from Shelf we use the "Destination" facet, which is still not ideal because we cannot see individual library hold shelves or whether an item is for office delivery. "Request/Process Type" would allow us to separate the two types of requests very easily. The facet "Pick-up Location" from Monitor Requests and Item Processes would then allow us to see which hold shelf an item is routing to or whether it is for Office Delivery. Adding these two facets would allow us to prioritize our requests more efficiently.

   Currently our staff spend too much time managing requests. Improvements to the interface for Pick From Shelf would help in some of these cases. We would like to see:

   1. A search box.

   Very often we need to target a particular request, a task made more difficult by less than ideal facets (see #2). Search functionality exists under Monitor Requests & Item Processes, but not all options for handling requests are available in that view (such as "Skip Location").

   1. Better facets.

   Two of the facets available in the Monitor Requests & Item Processes view would be great for Pick from Shelf:… more

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

3. Encumbered Balance Amounts only link to unpaid purchase order lines

   In the Summary Details of an allocated fund code, there are hyperlinked amounts listed next to Expended Balance and Encumbered Balance. We want the Encumbered Balance amount to link through to only purchase order lines that make up the total balance amount listed in the hyperlink.

   Currently it links through to any purchase order line that had an encumbrance placed on it with this allocated fund code. Regardless of whether the purchase order line has already been expended and disencumbered or still has an outstanding encumbrance waiting to expend on it.

   This would be helpful as it would give us an easy method to review which purchase order lines we still have outstanding expected expenditures on in the current fiscal year for each allocated fund code. Which helps us to determine more accurately the funds we will still need to spend before the end of the current fiscal year.

   In the Summary Details of an allocated fund code, there are hyperlinked amounts listed next to Expended Balance and Encumbered Balance. We want the Encumbered Balance amount to link through to only purchase order lines that make up the total balance amount listed in the hyperlink.

   Currently it links through to any purchase order line that had an encumbrance placed on it with this allocated fund code. Regardless of whether the purchase order line has already been expended and disencumbered or still has an outstanding encumbrance waiting to expend on it.

   This would be helpful as it would give us… more

   67 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…)
   3 comments  ·  Acquisition - Funds  ·  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. Brief Record - Quick Cataloging Template

   Boston College would like to see the contents of the linking tab of Electronic Portfolio Editor added to the Brief Record, Quick Cataloging template for electronic articles.

   This will enable us to edit the URL and enable the proxy as we catalog and would save us the step of going in later to edit the linking information. It would also enable us to test the link before posting it, rather than using the "view it" function afterwards.

   • 

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

5. Alma User Role for Editing/Deleting only Quick-Cataloged Records

   Scenario:
   Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.

   Problem:
   Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:

   Some institutions have given their non-cataloging staff full cataloging permissions to mitigate the inability of Reserves and ILL staff roles to delete and edit bibs. Those non-cataloging staff then have privileges that allow editing of full records, Network Zone records, etc. These activities should be restricted to staff trained in cataloging.

   At other institutions, cataloging privileges are only extended to staff in technical services. This requires an inefficient workflow between access services and technical services to correct mistakes or delete records created in error.

   Request:
   We would like to request an Alma user role that allows the deletion and update of Quick-Cataloged records only.

   This new role would reduce the number of users with full cataloging privileges and increase both data security and compliance with auditing requirements for institutions that give circulation staff cataloging roles so that they can edit these Quick-Cataloged records.

   For institutions that restrict cataloging roles to trained catalogers, having such a role would allow them to streamline workflows for editing Quick-Cataloged records, and free up the time of their cataloging staff to focus on more specialized materials.

   Scenario:
   Library staff frequently need to create records for resources using the Quick Cataloging feature. Often, those records need to be edited after creation, due to mismatching resource types, updated information, operator input errors, etc. Most of the staff using the Quick Cataloging feature are not trained as catalogers, and do not have cataloging roles in Alma.

   Problem:
   Quick-Cataloged records are not editable by staff without cataloging roles in Alma - who are frequently the creators/managers of these records. This has led to several different workarounds at various institutions:

   Some institutions have given their non-cataloging staff full cataloging permissions to… more

   66 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  ·  Resource Management - General  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Limit fine/fee payment to specific library

   One of our satellite libraries would like restrict payment of fines/fees for their materials to them -- we have separate accounting and budgets.

   66 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  ·  Fulfillment - Fines &Fees  ·  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. Seasonal Serials Prediction Patterns only work when beginning with Spring.

   Area of concern: Serials Prediction in Alma.

   Currently, when creating 853 predictive patterns, there are limitations to titles with a seasonal frequency. Attempting to create seasonal prediction patterns, whose enumerations begin with anything but Spring (21) results in errors, such as skipped issues, or improper numbering.

   This limitation means that many journals with seasonal patterns cannot have their issues correctly predicted out through Alma’s automated process. Staff members are stuck manually creating/receiving issues for these titles. This decreases efficiency, increases the likelihood of human error, and prevents Alma’s claiming process from working correctly.

   What should be changed: As Serials Processors, we would like to have the option for a seasonal prediction pattern to begin enumeration with any season. This would benefit our workflow by allowing these titles to be predicted and eliminating the need to receive them manually.

   Area of concern: Serials Prediction in Alma.

   Currently, when creating 853 predictive patterns, there are limitations to titles with a seasonal frequency. Attempting to create seasonal prediction patterns, whose enumerations begin with anything but Spring (21) results in errors, such as skipped issues, or improper numbering.

   This limitation means that many journals with seasonal patterns cannot have their issues correctly predicted out through Alma’s automated process. Staff members are stuck manually creating/receiving issues for these titles. This decreases efficiency, increases the likelihood of human error, and prevents Alma’s claiming process from working correctly.

   What should be changed: As Serials Processors,… more

   66 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…)
   3 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

8. Update All Relevant Indicators When Correcting Preferred Terms Linked via Cross-References

   The recent enhancement to Preferred Term Correction correctly updates bibliographic headings when the preferred and non-preferred terms are in different authority fields (for example, 410 → 130), and changes the bibliographic field tag accordingly (e.g., 610 → 630).
   However, the current implementation does not fully synchronize MARC indicators between authority and bibliographic records.

   The enhancement documentation states:
   "When a bibliographic field is updated to an X30 field, the non-filing indicators in the bibliographic record will be adjusted based on the linked authority record. According to MARC21 standards, the 1st indicator of authority field 130 (Nonfiling characters) will be copied to the 2nd indicator of the X30 bibliographic field."
   This is not accurate. In MARC21 authority format, the 1st indicator of field 130 is undefined (#), and the 2nd indicator represents the number of nonfiling characters.
   Specifically:

   1. In cases involving authority field 130:
      o MARC21 defines the 2nd indicator of authority field 130 as the number of nonfiling characters.
      o In bibliographic X30 fields (130/630/730/830), the number of nonfiling characters is recorded in the 1st indicator.
      o Therefore, the system should correctly transfer the nonfiling value from the 2nd indicator of authority field 130 to the 1st indicator of the corresponding bibliographic X30 field.
      o In addition, the 2nd indicator of the bibliographic X30 field should not be modified as part of this process.

   2. In all other controlled access points (1XX, 6XX, 7XX, 8XX):
      o Whenever a bibliographic heading is linked to an authority record, the 1st indicator of the bibliographic field should be automatically synchronized with the 1st indicator of the corresponding authority 1XX field.
      o If indicators differ, they should be updated to ensure full consistency.
      Without this synchronization, inconsistencies remain between authority data and bibliographic headings, generating additional manual maintenance and undermining the integrity of authority control.

   Proposed Enhancement

   Extend Preferred Term Correction to include automatic indicator alignment between authority records and all linked controlled bibliographic access points, in full compliance with MARC21 specifications.

   The recent enhancement to Preferred Term Correction correctly updates bibliographic headings when the preferred and non-preferred terms are in different authority fields (for example, 410 → 130), and changes the bibliographic field tag accordingly (e.g., 610 → 630).
   However, the current implementation does not fully synchronize MARC indicators between authority and bibliographic records.

   The enhancement documentation states:
   "When a bibliographic field is updated to an X30 field, the non-filing indicators in the bibliographic record will be adjusted based on the linked authority record. According to MARC21 standards, the 1st indicator of authority field 130 (Nonfiling characters) will be copied to… more

   66 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  ·  Resource Management - General  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Establish system to ensure complete coverage of LC classifications

   Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative system with LC for updating their coverage. The outcome would be that Analytics users would be confident that very few valid classifications would come up as "Unknown" in Alma Analytics, and those that did would be added within a reasonable time frame without the need to file support tickets.

   Alma Analytics includes LC Classification code data, but frequently valid classification codes come up as "Unknown." Ex Libris currently has no reliable way of keeping up with changes in LC classification. They rely upon the "Library of Congress Classification Outline", which is not complete. They will add classifications upon customer request, though this process takes months or years and puts significant burden upon institutions. Ex Libris should develop a system to reliably update its LC classification coverage. This could take the form of e.g. establishing its own access to Classification Web, subscribing to LC updates, and/or setting up some alternative… more

   •  

   66 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

10. Add General Electronic Services information to Analytics

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would allow for the simultaneous viewing of a lot of information.

    Please add the General Electronic Services to Analytics, with all fields:
    Active
    Service Code
    Service Name
    Service Description
    Public Name
    Public Note
    DD/ILL Service
    Display Location
    URL Template
    Enable without login
    Disable Service
    All Service Availability Rules

    Thank you for considering!

    In General Electronic Services, we have four different services for article requests, four different services for book requests, and five different services for book chapter requests, all developed over the years to address provider idiosyncrasies. Each group of services provides the same link to the user, e.g. the article request links all display "Get this PDF".

    Our Interlibrary Services unit has the product delivery statistics, but I would really find it helpful to know how many clicks each of our General Electronic Services gets. It would help with service and link maintenance and I expect with troubleshooting, since it would… more

    66 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…)
    2 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

11. We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them o

    This is about allowing Course Reserves course and reading lists to be able to be managed in sets and deleted in bulk.

    We would like the ability to manage course reserves reading lists and courses in bulk. Currently, it appears that we can only delete them one at a time and have thousands of old outdated ones. This could either be done in the Mange Fulfillment Sets or just Manage Sets and then we would want a way to delete them too with a job.

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

12. Indication rule that checks if subfields are in the same field

    Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:

    Record 1:
    690 $$a mercury $$b venus

    Record 2:
    690 $$a mercury $$b mars
    690 $$a earth $$b venus

    I'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field. We need this quite often for our local fields, as our data reflects different classifications via subfield 2.

    Currently it is not possible to write an indication rule which checks the subfield a and b of a field only when both subfields are in the same field and not in repeated fields of the same record. Both of the following records are treated the same when looking for a subfield a "mercury" and subfield b "venus" in the 690 field:

    Record 1:
    690 $$a mercury $$b venus

    Record 2:
    690 $$a mercury $$b mars
    690 $$a earth $$b venus

    I'd appreciate an option to distinguish if I'm looking for subfields in different fields or in the same field.… more

    65 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  ·  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 (Product Manager, Ex Libris) responded

    I recommend applying XSL normalization rules with the required logic and integrating them into the Upon Save normalization process.

13. Add 245 subfield n to the letter XML node for title

    Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.

    We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
    245 10 |a Prisma Physik |n 1
    245 10 |a Deutsch |n Drei
    245 00 |a Prisma |n 1
    245 10 |a <<Die>> Sprachstarken |n 2 |b Deutsch für die Primarschule
    Currently, it is not possible to display the title including the subfield n.

    We would like to add the 245 subfield n right after the subfield a in the XML node notificationdata/physitem_display/title in letters. If the XML structure is different in each letter and you would have to adapt each letter, then please prioritize the On Hold Shelf Letter.

    Many letters display the name of the title using the node notificationdata / physitem_display / title. This field contains a subset of subfields from the MARC field 245 to display the title of the work.

    We receive complains from our users regarding missing book title number in mostly textbooks. The missing number is available in the MARC field 245 subfield n and is an important part of the title. For example:
    245 10 |a Prisma Physik |n 1
    245 10 |a Deutsch |n Drei
    245 00 |a Prisma |n 1
    245 10 |a <<Die>> Sprachstarken |n 2 |b… more

    65 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 - 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. Automate Cleanup of Electronic Resource Activation Tasks

    When electronic resources are ordered in Alma, an activation task is often generated on the Electronic Resource Activation Task List. However, many resources are later activated outside that workflow.

    When this happens, the resource is active and discoverable, but the activation task remains open until staff manually find and close it. Over time, this creates unnecessary clutter and makes the task list less useful for identifying resources that still require action.

    Proposed Solution:

    Add functionality to automatically close activation tasks when the associated portfolio or collection is already active.

    Possible approaches include:

    A scheduled job that reviews open activation tasks and automatically marks tasks as complete when the linked resource is active.

    An optional configuration setting that automatically closes any open activation task when a portfolio or collection is activated, regardless of where the activation occurs.

    This enhancement would reduce manual cleanup, improve task list accuracy, and better align activation workflows with actual resource status in Alma.

    When electronic resources are ordered in Alma, an activation task is often generated on the Electronic Resource Activation Task List. However, many resources are later activated outside that workflow.

    When this happens, the resource is active and discoverable, but the activation task remains open until staff manually find and close it. Over time, this creates unnecessary clutter and makes the task list less useful for identifying resources that still require action.

    Proposed Solution:

    Add functionality to automatically close activation tasks when the associated portfolio or collection is already active.

    Possible approaches include:

    A scheduled job that reviews open activation tasks… more

    65 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…)
    3 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

15. Colour/shade gradients to tell the different between license statuses (Active, Retired, Deleted)

    In the list of licenses it would be useful to have a colour/shading gradient difference between active and inactive licenses.
    For example, when you delete a license it still remains in Alma, it is just given the status deleted. This is fine as it provides a history, however, as the deleted licenses in the list look exactly the same as active licenses, apart from the status note it can often be difficult to tell the active and deleted licences apart, especially at a glance.

    It would be useful to change the colouring/shading gradient, for example, grey out the text, for the deleted licences to make the Active licenses prominent, so you can quickly determine the correct license to link to a collection etc.

    A similar thing for the retired licenses would also be great.

    In the list of licenses it would be useful to have a colour/shading gradient difference between active and inactive licenses.
    For example, when you delete a license it still remains in Alma, it is just given the status deleted. This is fine as it provides a history, however, as the deleted licenses in the list look exactly the same as active licenses, apart from the status note it can often be difficult to tell the active and deleted licences apart, especially at a glance.

    It would be useful to change the colouring/shading gradient, for example, grey out the text, for… more

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

16. Update 863/864/865 when items are withdrawn

    There is a crucial step missing in the Automatic Generation of the Summary Holdings Statement Based on Items process. The process is documented here:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/020Navigating_the_MD_Editor_Page?uxp=true#Automatic_Generation_of_the_Summary_Holdings_Statement_Based_on_Items

    When items which are linked to the Holdings record are withdrawn, there is no process to update the Holdings record 863/864/865 fields to create an updated 866/867/868 field. When items are withdrawn, the user has to manually edit the Holdings records.

    Since the creation of the 863/864/865 field is now automated based on received items being linked to the holdings record, there is a need for the 863/864/865 to be automatically re-created when the linked items are withdrawn.

    There is a crucial step missing in the Automatic Generation of the Summary Holdings Statement Based on Items process. The process is documented here:
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/040Resource_Management/040Metadata_Management/020Navigating_the_MD_Editor_Page?uxp=true#Automatic_Generation_of_the_Summary_Holdings_Statement_Based_on_Items

    When items which are linked to the Holdings record are withdrawn, there is no process to update the Holdings record 863/864/865 fields to create an updated 866/867/868 field. When items are withdrawn, the user has to manually edit the Holdings records.

    Since the creation of the 863/864/865 field is now automated based on received items being linked to the holdings record, there is a need for the 863/864/865 to be automatically re-created when the linked… more

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

17. Vendor Interface > Contact Information > Email addresses

    The default display for Vendor Interface > Contact Information > Email addresses, does not include an option to display the "description" field on the main page. The fields available for display are: Preferred, email address, created by, creation date, and type.

    Since most correspondence with vendors and sales representatives happen by email now, it would be useful to be able to see the description on the main page without having to click on .... and Edit for each email listed to see who is the correct contact.
    Some email addresses do not contain the person's full name, and if you have different contacts from the same vendor for different purposes, it would be one less click to view the description that explains who to contact for what specific purpose.

    I'd rather remove "created by" and "creation date" as display options and replace them with "description" in the display options on the Vendor Interfac > Contact Information > Email addresses main screen.

    Using the Vendor Interface > Contact information is preferred because Vendor > Contact People creates internal users - and we do not want to create internal users out of our vendor sales and support contacts - especially since those contacts may change frequently.

    Thanks for considering. Sandra.

    The default display for Vendor Interface > Contact Information > Email addresses, does not include an option to display the "description" field on the main page. The fields available for display are: Preferred, email address, created by, creation date, and type.

    Since most correspondence with vendors and sales representatives happen by email now, it would be useful to be able to see the description on the main page without having to click on .... and Edit for each email listed to see who is the correct contact.
    Some email addresses do not contain the person's full name, and if you… more

    64 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…)
    2 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. Display logic rules should work on Primo users NOT logged in

    Display logic rules currently only work if a user logs in Primo. Also, the rules only work to hide a service (not show a service). Also, Primo New UI does not allow forcing users to log in.

    So, we have a scenario where we want CCC Get It Now articles to display only for our Faculty user group. However, the article links are displaying to everyone (guest) - until the user logs in and then the links are hidden for everyone except our faculty. Because everyone starts out in Primo as guest, this defeats the purpose of the rule.

    Another scenario is that a college that we are in a consortium with wants to hide EBSCO links if Gale links exist. They can create a display logic rule to do this, but the rule will not work for guest, only for logged in users.

    Another fix for this issue would be to allow a display logic rule that will basically only SHOW a service if it is a certain user group. This would allow us to show the CCC Get It Now interface if the user group is faculty. However the display logic rules do not allow this type of logic.

    Display logic rules currently only work if a user logs in Primo. Also, the rules only work to hide a service (not show a service). Also, Primo New UI does not allow forcing users to log in.

    So, we have a scenario where we want CCC Get It Now articles to display only for our Faculty user group. However, the article links are displaying to everyone (guest) - until the user logs in and then the links are hidden for everyone except our faculty. Because everyone starts out in Primo as guest, this defeats the purpose of the rule.

    Another… more

    64 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  ·  Link Resolver  ·  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. Allow Alma users to choose the match routine when using the ‘Link to Community’ tool to link portfolios to a community zone collection.

    The ‘Link to Community’ match routine for matching local portfolios to the CZ is too restrictive. We would like to be able to use our local bibliographic records and have them link to portfolios in the CZ, however, the match rate is dependent on what metadata is available in the CZ records, which are often brief and do not contain the ISSN/ISBN match point that Ex Libris has selected for that collection in the CZ.
    Alma users should be able to choose the match routine when using the ‘Link to Community’ tool, similar to how we can choose the match profile when managing an import profile. At minimum the ability to choose between ISSN/ISBN or 035 Other Identifier would be an improvement. This would allow us to analyze the CZ vs Local records to find the best match point to use when linking our full records to CZ portfolios attached to brief CZ records.

    The ‘Link to Community’ match routine for matching local portfolios to the CZ is too restrictive. We would like to be able to use our local bibliographic records and have them link to portfolios in the CZ, however, the match rate is dependent on what metadata is available in the CZ records, which are often brief and do not contain the ISSN/ISBN match point that Ex Libris has selected for that collection in the CZ.
    Alma users should be able to choose the match routine when using the ‘Link to Community’ tool, similar to how we can choose the match… more

    64 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…)
    2 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

20. The line separator in Analytics outputs is normally a semicolon, but should not be ambiguous

    In various exports from Analytics, it was noticed that the characters present in Alma are output as follows:

    • sharp bracket < present in Alma is put out by Analytics as & l t ;
    • sharp bracket > in the Alma (bibliographic data) material is put out by Analytics as & g t ;
    • ampersand & as & a m p ;

    This is likely due to HTML being used as the export format in Analytics. However, for the further processing of large amounts of data, it is disruptive that a semicolon is used for coding here. The semicolon appears both within individual data cells in Alma (e.g. in BIB data fields) as part of the data content or as a formal description character and also as a line separator in results from Analytics (every time a BIB category is repeated).
    It would be beneficial if the ambiguous use of the semicolon in Analytics were flanked in such a way that the line separator is represented by a character that does not additionally appear in running texts or through the HTML conversion of sharp brackets or the ampersand.

    We were referred to idea exchange.

    In various exports from Analytics, it was noticed that the characters present in Alma are output as follows:

    • sharp bracket < present in Alma is put out by Analytics as & l t ;
    • sharp bracket > in the Alma (bibliographic data) material is put out by Analytics as & g t ;
    • ampersand & as & a m p ;

    This is likely due to HTML being used as the export format in Analytics. However, for the further processing of large amounts of data, it is disruptive that a semicolon is used for coding here. The semicolon appears both… more

    64 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