1903 results found

1. Use Online Ordering to preference ebook multi-user licenses over single user licenses.

   We would like ebook links with unlimited or multi-user licenses to be preferenced (display first) over single user license ebooks in discovery configuration. We would like this to be an option in Configuration > Fulfillment > Discovery Interface Display Logic > Online Services Order

   7 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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

2. Automated linking a NZ record to the IZ based on the existence of a parent 773 link

   As a system librarian, I have a problem with linking large amounts of bibliographic records from Network Zone to the Institution Zone. Those are recods that are related to other bib records by the 773 field with $w – links using the record control number and/or with $x – links using the ISSN of the bibliographic record. Those linking records, usually monographic component parts, are created and saved in the Network Zone, and are not automatically linked to their related records in the IZ, every institution has to link them one by one from the NZ to IZ.
   It would be really beneficial for all of the NZ members to save time and not have to do that job manually. If the linking record contains 773 field with $w and/or $x subfields, it should be linked automatically to all of the institutions that have the related records in the IZ.

   As a system librarian, I have a problem with linking large amounts of bibliographic records from Network Zone to the Institution Zone. Those are recods that are related to other bib records by the 773 field with $w – links using the record control number and/or with $x – links using the ISSN of the bibliographic record. Those linking records, usually monographic component parts, are created and saved in the Network Zone, and are not automatically linked to their related records in the IZ, every institution has to link them one by one from the NZ to IZ.
   It would… more

   7 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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

3. Improve cookies on Alma and other Clarivate sites

   Alma-specific:
   * Re-configure the OneTrust settings so that performance cookies default to off
   * Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
   * Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)

   Clarivate-wide:
   * Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off, remove unnecessary cookies (ie social media cookies and especially targeting cookies), and make more Clarivate sites respect user preferences as expressed on other Clarivate sites.

   Background - current situation:
   Clarivate has a vast range of library/research related websites. They all use OneTrust to manage cookies, but are almost all configured separately (so even after you've set your preferences on one site, other sites don't apply the same preferences) and differently (so some sites default to optional cookies off while others default to on).

   The best site is ProQuest Support. This has a lot of cookies (Functional, Targeting, Social Media, and Performance) but they all default to off, so you can open it up and quickly confirm that. Moreover if you then go to ProQuest Central, it appears to remember and respect those same preferences.

   Primo (both VE and NDE) doesn't have a cookie banner at all. I hope this means that it doesn't use cookies? (Though if Primo can manage without cookies I wonder why the other sites can't.)

   Other sites default to having cookies on: IdeaExchange only has Performance cookies, while Knowledge Centre, Developer Network, Alma, Leganto, and Web of Science all have both Performance Cookies and Targeting Cookies.

   This means that if, for example, you've cleared your browser cache for some reason, then when you open Alma, Leganto, Knowledge Centre, Developer Network, ProQuest Support, and IdeaExchange, every single one of these sites separately wants you to manage your cookies. Also if you start on ProQuest Support where cookies default to 'off' you may assume the same is true on the other sites, and try to save time by clicking 'confirm my choices' without clicking every individual tab first, not realising that this is actually setting them to 'on'.

   Alma-specific:
   * Re-configure the OneTrust settings so that performance cookies default to off
   * Targeting cookies should not be present at all (my Alma usage is useless to advertisers and if it's not then that's really concerning!) but if you must have them then these should also default to off.
   * Leganto and other systems that are configured in Alma should respect any opt-out settings the user has already specified on the Alma site (and vice versa)

   Clarivate-wide:
   * Someone should have a thorough review of OneTrust configurations across the whole conglomerate to make all optional cookies default to off,… more

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

4. Expand the character limit for Inventory number field

   The Inventory number field for physical items in Alma is currently limited to 20 characters. We are using RFID tags to track some of our items, and would like to store them in the Inventory number field. Because these codes are generally about 25 characters long, it'd be helpful if the size of the field could be extended to 30 or (preferably) 50 characters.

   20 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

5. Contributed collections - a Report to Contributor instead of Report to Ex Libris

   There are many collections now that are contributed by the community. Sometimes there are errors within them and as it is now, there is no way to report that and get the linking problem (for an example) fixed and the issues can be so many that a deactivation is necessary, but then the collection becomes dead and just clutter KB. My suggestion is that when a institution contributes a collection, a mandatory field is added to the workflow of contributing. This field contains an email address. That email address is then incorporated into a button so you can report to Contributor instead of the button that is there now Report to ExLibris.

   This idea has been put forward before: Email CZ Contributor ... but it's a growing problem.

   There are many collections now that are contributed by the community. Sometimes there are errors within them and as it is now, there is no way to report that and get the linking problem (for an example) fixed and the issues can be so many that a deactivation is necessary, but then the collection becomes dead and just clutter KB. My suggestion is that when a institution contributes a collection, a mandatory field is added to the workflow of contributing. This field contains an email address. That email address is then incorporated into a button so you can report to… more

   127 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

6. Reactivate deferred order POLs in bulk

   For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.

   We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a REST API process to update the POLs and ensure the records are consistent and ready for processing.

   At this point, however, reactivation can only be performed manually through the Alma UI, requiring staff to reactivate each POL individually. Having to move from a largely automated, bulk workflow to a one-by-one manual process is time-consuming and inefficient.

   Could Ex Libris provide a supported way to reactivate deferred POLs in bulk, either through an existing job, a new workflow option, or a public API? This would allow institutions to return deferred POLs to In Review and continue them through the standard acquisitions workflow without requiring manual intervention for each individual record.

   For Legal Deposit we create deferred PO Lines (POLs) linked to pre-publication information supplied by publishers. When the deferral reminder date is reached and the publication has not yet been received, staff reactivate the POL. Functionally, this returns the POL to In Review, where it is validated and, if there are no issues with the POL or vendor record, a publication request is sent to the publisher.

   We typically reactivate 100-150 deferred POLs per month. Before reactivation, the relevant POLs are gathered and exported to a spreadsheet, where metadata is reviewed and any issues are resolved. We then use a… more

   12 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Allow customers to select multiple retention reasons for Item records.

   Allow customers to select multiple retention reasons for Item records.

   As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

   Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff workflows, respectively:

   1. Blocking withdrawal/weeding at the institutional (IZ) or consortial (NZ) level by collection development staff

   2. Generate a report that can be used to populate a display shelf highlighting local research at our campus

   3. Identification of materials that should be prioritized for preservation treatment

   4. Block withdrawal/weeding and select for inclusion in data integration/sharing with partners

   5. Identification of materials that are good candidates for off-site high density storage

   Absent the ability to assign multiple values in a dropdown, which will provide a kind of authority control for approved statuses, we would be dependent on cramming all of this information into the free text Retention Note field. Obviously, this would be more error prone as it would require 100% consistency to achieve the same level of data reporting as the dropdown menu options would have. Additionally, parsing a free text field to find specific substrings in an Alma Analytics report is a much more sophisticated and therefore difficult task to accomplish. This would therefore have the effect of limiting the number of staff who are capable of effectively querying for all retention reasons.

   Allow customers to select multiple retention reasons for Item records.

   As an institution that is very enthusiastic about using the new Retention Information data fields for item records in Alma, we would like to request an enhancement that enables a user to assign multiple values to the Retention Reason field. For example, a single item could easily have all of the following statuses applied:

   1. Institutional last copy

   2. Faculty publication

   3. Rare

   4. Committed to some Shared Print program

   5. Digitized material

   Each of these retention reasons may correspond to different library staff workflow. For example, these retention reasons could support the following staff… more

   76 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

8. Color coded pop-ups

   It would be great if the various pop-ups in Alma on return or scan in would be color coded for additional indication of what needs to happen to an item.

   Example - Transit item could be a green box, and a fulfillment note could be yellow.

   3 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  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

9. Add Resource Sharing Partner Setting for ILLiad Cleared Status

   When a library creates a resource sharing partner for ILLiad and checks the Create User in ILLiad box, Alma does not pass a Cleared value in the CreateUser ILLiad API call. This means all ILLiad user records created by Alma need to be manually cleared. Please add a new setting to the ILLiad resource sharing partner type that allows libraries to select a Cleared value of either "No" or "New".

   34 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 Sharing  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

10. Allow merge rules for authority import profiles

    It would be very useful allowing custom merge rules in Alma authority import profiles for ensure controlled, automated updates of authority records,
    especially in a cooperative cataloguing environment.
    Configuring these rules to selectively merge, keep, or add specific MARC fields during import, would ensure enhancing data quality for both local
    and network zones.

    21 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

11. Expand SIP2 message support to include patron birth date

    Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.

    For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).

    We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age

    This enhancement would enable safer and more autonomous self-service environments, particularly in low-staffed libraries, while ensuring compliance with age-based borrowing restrictions and institutional policies.

    Currently, Alma’s implementation of the SIP2 protocol uses only a limited subset of the available data fields. This restricts the potential of SIP2 integrations with self-check machines and other automated systems.

    For example, patron age or birth date information is not transmitted via SIP2 messages. As a result, self-check units cannot automatically block the checkout of restricted materials (e.g., DVDs or other items not permitted for users under 16).

    We propose that Alma extend its SIP2 message support to include additional patron details such as birth date and/or age

    This enhancement would enable safer and more autonomous self-service environments, particularly… 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…)
    0 comments  ·  APIs and Integrations  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

12. Clearer terminology for loan and copy requests on ILL request form

    Enable libraries to customise or replace terminology in Rapido request forms and request tiles so users can select services using plain language, such as "Loan" and "Digital Copy".

    Current gap: The blank request form requires users requesting a loan to select Citation Type "Book" and Format Type "Physical". Rapido request tiles similarly use the term "Physical Copy". Nowhere in these workflows is the term "Loan" used. Users must interpret system terminology to understand which option will provide a borrowed item. Similarly, users requesting a scanned reproduction must select "Digital", which does not clearly communicate that they are requesting a copy of part of a work.

    Impact: Users may be uncertain which option to select, increasing the likelihood of incorrect requests and creating additional support work for staff. Using clearer, service-based language such as "Loan" and "Digital Copy" would better align with user expectations and improve the request experience.

    This enhancement would support plain language and accessibility principles by reducing the need for users to interpret library system terminology. It would also create greater consistency between Rapido request forms, request tiles, and the service terminology commonly used by libraries when communicating with users.

    Enable libraries to customise or replace terminology in Rapido request forms and request tiles so users can select services using plain language, such as "Loan" and "Digital Copy".

    Current gap: The blank request form requires users requesting a loan to select Citation Type "Book" and Format Type "Physical". Rapido request tiles similarly use the term "Physical Copy". Nowhere in these workflows is the term "Loan" used. Users must interpret system terminology to understand which option will provide a borrowed item. Similarly, users requesting a scanned reproduction must select "Digital", which does not clearly communicate that they are requesting a copy… more

    8 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

13. Rapido – Popup warning when local/consortium copy exists

    We have more than 4 millions documents in our consortia, and a Rapido service. Sometimes patrons order a document via Rapido while this document is available locally. This can be choice or an error. To avoid errors, Rapido should display a configurable popup whenever a patron submits a Rapido request for an item that is available in our consortium. The popup would warn the user that a free local loan exists and ask for explicit confirmation before sending a paid ILL request, for example: “One or more copies are available from your library network for free loan. Would you still like to proceed with your interlibrary loan request, a paid service charged according to the fees in the link?” This feature would reduce unnecessary Rapido/ILL costs, promote use of local and consortial holdings, and improve transparency for patrons while preserving their freedom of choice.

    We have more than 4 millions documents in our consortia, and a Rapido service. Sometimes patrons order a document via Rapido while this document is available locally. This can be choice or an error. To avoid errors, Rapido should display a configurable popup whenever a patron submits a Rapido request for an item that is available in our consortium. The popup would warn the user that a free local loan exists and ask for explicit confirmation before sending a paid ILL request, for example: “One or more copies are available from your library network for free loan. Would you still… more

    42 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 Sharing  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Increase the number of available facets for all POL searching

    All aspects of the POL should be available as facets, assuming they appear sufficiently frequently in a set of results. Most notably, all 5 reporting code fields should be available as facets.
    Additionally, other sources of POL lists, such as the Alma Vendor Record should offer all of the same faceting functionality, including the ability to customize which facets are visible.

    49 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Acquisition - PO & POLine  ·  Delete…  ·  Admin →
    How important is this to you?

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

15. Improve locate process to accurately determine an article’s availability based on the partner’s portfolio coverage

    Currently, when a digital resource sharing request include only the publication date year, the system interprets the publication date as January 1 of that year. If the partner’s portfolio coverage includes only volume/issue, the availability is calculated based on the volume/issue information in the request. However, if the portfolio coverage includes both year and month, then the availability is calculated based on dates only. Even if the coverage also includes volume/issue, the volume/issue data in the request is ignored, and the link resolver does not estimate dates based on volume/issue. The locate process then checks if there is an embargo set in the lender’s portfolio and calculates the embargo from today’s date going one year backwards. The volume/issue information is ignored and the link resolves does not estimate dates based on volume/issue. This leads to many requests being located even when an article falls outside of the partner’s journal coverage.
    We would like the precision of the locate process to the improved by incorporating all of the information provided in the request form (ISSN, date, volume, issue, article title, author) and the partner’s portfolio coverage when determining the availability of an article as seen in the flowchart attached.

    Currently, when a digital resource sharing request include only the publication date year, the system interprets the publication date as January 1 of that year. If the partner’s portfolio coverage includes only volume/issue, the availability is calculated based on the volume/issue information in the request. However, if the portfolio coverage includes both year and month, then the availability is calculated based on dates only. Even if the coverage also includes volume/issue, the volume/issue data in the request is ignored, and the link resolver does not estimate dates based on volume/issue. The locate process then checks if there is an embargo… more

    •  

    14 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

16. Limit title level request fulfillment to items from holding records without descriptions or items without descriptions

    Current Problematic Functionality: Physical item requests (holds) are placed at the title level (any item from any holding record attached to the bibliographic record will be used to fill the hold) when a holding record has no items with descriptions. Requests are placed at the item level (the exact item requested will be used to fill the hold) when a holding record has one or more items with a description. As a result, if a user places a request on an item attached to a holding record with no description, but there exists on the bibliographic record a second holding record with items with descriptions, the items with descriptions may be selected to fill the request. As a result a user may request a monograph, but receive a supplement to that monograph instead.

    Example (https://search.library.ualberta.ca/permalink/01UOA_INST/doujli/alma991033437399709116
    ): See the attached screenshot for an example of this issue. In this example the user may place a title level request (hold) on the Cameron Science and Engineering Library item and receive the Research and Collections Resource Facility item with the description suppl.

    Desired functionality: When a request (hold) is placed at the title level, only items from holding records without item descriptions are considered for filling the hold OR only items without descriptions are considered for filling the hold.

    Rationale: The user should be able to confidently request an item and receive the item they've requested. Cataloguing practice requires the addition of descriptions to monographic items when the items are supplementary. This is standard practice for supplements, as described in Classification and Shelflisting Manual G 155 (sec. 2) (https://www.loc.gov/aba/publications/FreeCSM/G155.pdf). Because of the shift of materials between libraries, supplementary material may be split from base volumes, causing there to be holding records with items with descriptions, and holding records with items without descriptions.

    Current Problematic Functionality: Physical item requests (holds) are placed at the title level (any item from any holding record attached to the bibliographic record will be used to fill the hold) when a holding record has no items with descriptions. Requests are placed at the item level (the exact item requested will be used to fill the hold) when a holding record has one or more items with a description. As a result, if a user places a request on an item attached to a holding record with no description, but there exists on the bibliographic record a second holding… more

    •  

    18 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

17. Admin - Create a set - how many records are in my set without opening the set

    Why cant we see on the list of sets pages how many records are in each list?
    Surely that can be shown without having to open endless sets...

    7 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  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

18. Predicted Items - Add columns in Metadata overview

    When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.

    Currently, the following columns are shown:
    - Description
    - Status
    - Expected arrival date

    Please add:
    - First level of enumeration (= Enumeration A in the physical item editor)
    - Second level of enumeration (= Enumeration B)
    - First level of chonology (= Chronology I)
    - Second level of chronology (= Chronology J)

    This addition would make it easier to verify whether all relevant fields are correctly filled by the pattern used in MARC 853.

    Thank you

    When opening predicted items in the Metadata Editor, the "Predicted Items" pop-up window appears. It would be very useful if the following columns could be added to the overview presented in this window.

    Currently, the following columns are shown:
    - Description
    - Status
    - Expected arrival date

    Please add:
    - First level of enumeration (= Enumeration A in the physical item editor)
    - Second level of enumeration (= Enumeration B)
    - First level of chonology (= Chronology I)
    - Second level of chronology (= Chronology J)

    This addition would make it easier to verify whether all relevant fields are correctly… more

    •  

    60 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  ·  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
    AdminLiza Voloshin (Product Owner, Alma Resource Management, Ex Libris) responded

    Hi all,

    Please note that this idea was mistakenly closed. It has now been reopened, and we apologize for any inconvenience caused.

19. Title: Allow Custom Scheduling Options for the Fines Transfer (Bursar Integration) Job

    Title: Allow Custom Scheduling Options for the Fines Transfer (Bursar Integration) Job

    We would like the ability to define custom schedules for the Alma Fines Transfer (Bursar Integration) job, rather than being limited to the predefined scheduling options currently available.

    At present, this integration profile does not support the flexible Edit Scheduling functionality that is available for many other Alma jobs. Institutions can only select from a small set of fixed schedule options, which do not always align with local business processes or external finance system requirements.

    For example, our institution needs to run the Fines Transfer on the 21st of each month at 10:00 AM, but this schedule cannot be configured. As a result, staff must manually run the job each month, introducing unnecessary operational overhead and increasing the risk of delays or human error.

    Requested Enhancement

    Please enable one of the following:

    Allow the Fines Transfer (Bursar Integration) job to use the standard Edit Scheduling functionality available for other Alma jobs, enabling fully flexible scheduling.
    Alternatively, add support for additional configurable scheduling options (such as custom day-of-month and time combinations) for this profile type.

    Benefits
    Allow Custom Scheduling Options for the Fines Transfer
    Eliminates the need for manual monthly execution.
    Supports integration with institutional finance and bursar systems that operate on fixed business schedules.
    Reduces operational risk and administrative effort.
    Provides consistency with the scheduling capabilities already available for other Alma jobs

    Title: Allow Custom Scheduling Options for the Fines Transfer (Bursar Integration) Job

    We would like the ability to define custom schedules for the Alma Fines Transfer (Bursar Integration) job, rather than being limited to the predefined scheduling options currently available.

    At present, this integration profile does not support the flexible Edit Scheduling functionality that is available for many other Alma jobs. Institutions can only select from a small set of fixed schedule options, which do not always align with local business processes or external finance system requirements.

    For example, our institution needs to run the Fines Transfer on the 21st… more

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

20. Add "Open Access" Electronic Access Type

    Please add "open access" as an electronic access type (like perpetual, current, current and perpetual) at both the portfolio and collection levels. With more resources being open access, it would be helpful to be able to mark them as such.

    7 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  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