2003 results found

1. Please add 3xx field support in Bibliographic Details dimension of Alma Analytics

   Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
   We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
   Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these for other important field data, and it’s not reasonable to take up more than a dozen of these just with 3xx fields.
   These fields do not generally have many characters, so it is not anticipated that this would add much to the performance load for the ETL to hardcode add to the Bibliographic Details dimension for all customers.
   This idea would be fulfilled by each of these mentioned 3xx fields being added to Alma Analytics as a standalone field ie not all in one field, to support bibliographic data management, maintenance, updating projects, and reporting.

   https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/080Analytics/080Shared_Dimensions/010Bibliographic_Details

   Currently there are many fields in the 3xx range which are not supported OTB in the Bibliographic Details dimension of Alma Analytics.
   We have mapped 300 to a Local Param several years ago, but we are stymied in our work updating to RDA consistently as the desired foundation for then considering LOD work in BIBFRAME, given this is a key area with many 3xx fields utilised such as 334, 335, 336, 337, 338, 340, 344, 345, 346, 347, 380 and 382.
   Although the number of Local Params increased in 2024 finally from 10 to 30 we use many of these… more

   32 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Enable 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

   •  

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

3. Usability issues with the New Circ UI

   1. When processing items from a cart, if they are scanned at Return items and the item is a Ship physically item, the new UI just brings up the item and in small letters says Next Step - System - and the library its to go to. It also says not on loan (which in this case is not helpful, because there is an active request). The system "ships" the item, but doesn't tell you that it did and in order to print the shipping slip staff have to go back to the lending queue and find it.
   2. We believe if the system wants to help you and ship the item because there is a request, it should a) Say clearly that it shipped the item b) Provide a quick way to print the slip c) Make that Route to next step message the main pop-up so the person processing knows there is a request on it and routes it to the right place.

   1. When processing items from a cart, if they are scanned at Return items and the item is a Ship physically item, the new UI just brings up the item and in small letters says Next Step - System - and the library its to go to. It also says not on loan (which in this case is not helpful, because there is an active request). The system "ships" the item, but doesn't tell you that it did and in order to print the shipping slip staff have to go back to the lending queue and find it.
   2. We believe if… more
   11 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  ·  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

4. Improve "Select all" search results selection

   When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.

   However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or at least we should have an additional option that would specifically select results visible on that page.

   When running a search within Alma, we have the option to "Select All", at which point we can accomplish various tasks like "Push selected to MDE" (for a Physical Titles search), "Add to Itemized Set" and "Create Itemized Set" (for a Physical Items search), etc.

   However, when clicking "Select All", this only selects the results on that page of results, which is capped at 50. If you create a search with many pages of results, you would have to take action on each page individually. Clicking "Select All" should actually select all results, not just the results on that page--or… more

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

5. Add a "Pick up location" line under the "Pick Up Requested Resources" columns

   For institutions with multiple campuses that share items, there is no way to see what the pick-up location for an item is on the Pickup Requested Resources page. you must export the data to excel, print it out, process the hold, or search for the item's request separately. This creates a lot of unnecessary steps for such simple information and makes it difficult for institutions that track item movement between campuses. My suggestion is to add a line in the columns under each request that states what the pick-up location is. View files to see example. Thank you

   •  

   18 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Daily quota of ISO-ILL Lending requests

   We would like to determine a daily quota of ISO-ILL Lending requests, like with RapidILL.
   Ideally, Alma would automatically reject requests beyond the quota and send them to other ISO Partners.

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

7. Include more than 30 or an unlimited number of local parameters in Alma Analytics

   We find Analytics to be very powerful, but we are hampered by its limitation to only selected MARC and a limit of 30 local parameters.

   We hope ExLibris will include more or an unlimited number of local parameters in the future.

   When we signed up for Alma, our team expected all MARC bib codes would be available in Analytics and they are not. In addition, we have defined several local fields and must assign them a local parameter to be able to output them in Analytics. We have been rationing the 30-alloted local parameters ever since.

   31 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

8. Folders in "Manage sets"

   We would like the option to make folders in "manage sets". This would make it easier for different depatmants to navigate through the public sets of the institution.

   8 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

9. Missing Padding Option for Accession Number Sequences in Call Number Generation

   Currently, Alma does not support padding (adding leading zeros to reach a fixed number of digits) for accession number sequences used in the automatic generation of call numbers (e.g., via the "Generate" / "Calculate" button in the item editor). If the next sequence value is set to "0003," the leading zeros are removed upon saving. Even if the next sequence remains "0003" in the sequence configuration, the zeros are still automatically stripped when generating the next call number in the item editor.

   Institutions that use custom call number schemes requiring padding can therefore only use Alma’s "Generate" or "Calculate" button as a basis for their call numbers, requiring manual addition of the missing zeros each time.

   This process is prone to errors and unnecessarily time-consuming, especially since the padding function is already implemented for other item sequences (inventory, receiving, and weeding numbers).

   We would therefore like to request the same padding functionality for accession number sequences.

   Currently, Alma does not support padding (adding leading zeros to reach a fixed number of digits) for accession number sequences used in the automatic generation of call numbers (e.g., via the "Generate" / "Calculate" button in the item editor). If the next sequence value is set to "0003," the leading zeros are removed upon saving. Even if the next sequence remains "0003" in the sequence configuration, the zeros are still automatically stripped when generating the next call number in the item editor.

   Institutions that use custom call number schemes requiring padding can therefore only use Alma’s "Generate" or "Calculate" button… more

   9 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

10. Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)

    Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)

    1) Add Vendor Type: Example: I want to analyze the vendor file based on vendors that are only Access Providers/Licensors and not Material Suppliers, or just Material Suppliers.

    2) Add Vendor Accounts as output, including options to output Payment Methods. Example: we recently had a campus financial system migration, and I want to isolate those vendors who pass through the ERP export vs. Credit Card vendors. Similar to Bank Transfers - if my campus has a change in policy that needs communication, I want to be able to pull these vendors together.

    3) From Contact Information, Preferred Address - be able to break out State and Country fields separately from the Address Details. Example: I want to run a report of my US-based vendors and my non-US-based vendors. Output as currently programmed is only Preferred Address as a whole string where I would have to break that out.

    Include Address Type as option (Billing, Claim, Order, Payment, Returns, Shipping)

    Add/modify fields from Vendor Record for Analytics (including Account, Contact Information/Preferred Address)

    1) Add Vendor Type: Example: I want to analyze the vendor file based on vendors that are only Access Providers/Licensors and not Material Suppliers, or just Material Suppliers.

    2) Add Vendor Accounts as output, including options to output Payment Methods. Example: we recently had a campus financial system migration, and I want to isolate those vendors who pass through the ERP export vs. Credit Card vendors. Similar to Bank Transfers - if my campus has a change in policy that needs communication, I want to be able to… more

    26 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

11. FUND / Ledger facet missing from PO Line user interface

    All PO Lines has multiple facets but FUND or Ledger is not one of them.

    Funds, both allocated & summary, are fundamental to purchasing and we'd like to be able to filter the PO Line display by these variables.

    Please add a facet in the All PO Lines user interface for FUND.

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

12. Search possibilities as "Received X weeks ago" or "Available X weeks ago"

    Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for the Collection Discovery feature, for example with a view to promoting that content. Using Analytics is not necessarily the best way of doing things like this.

    On the other hand, Rialto offers powerful search indexes such as "Added X weeks ago", "Available X weeks ago" or "Published X years ago" and operators "Less than or equal to", "Equal to" and "Greater than or equal to". Combining the two creates relevant logical sets that are updated automatically.

    It should be possible to search the Alma Repository using an approach similar to that used in Rialto.

    Libraries sometimes wish to build logical sets from constantly changing data. For example, a logical set of items received in the last 30 days or a logical set of ebook portfolios activated in the last 15 days. The "Receiving date" (Physical items) and "Activation Date" (Electronic portfolios) search indexes only accept a specific date (selectable from a calendar) and only allow the operators "Equals", "Not Equals", "Before", "After", "Is Empty", and "Is Not Empty". It is therefore not possible to build 100% logical sets based on items received in the last 3 weeks and associate them with a collection for… more

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

13. Allow EOD to generate multiple items (multi-volume sets) via Import Profiles

    Currently, importing Embedded Order Data to generate POLs with a New Order Import Profile creates a single item per quantity ordered in the POL. Similarly, Update Inventory imports can't update more than one item. Unfortunately, when ordering multi-volume sets, this means volumes 2-n are left off the POL and must be added manually. This creates significant manual work for acquisitions teams, for both approval plans and firm orders. Being able to specify Quantity ordered AND Number of Items (per set) would disambiguate how many volumes we expect to receive, and allow for code that could specify barcode/enumeration on each of the expected volumes.

    Currently, importing Embedded Order Data to generate POLs with a New Order Import Profile creates a single item per quantity ordered in the POL. Similarly, Update Inventory imports can't update more than one item. Unfortunately, when ordering multi-volume sets, this means volumes 2-n are left off the POL and must be added manually. This creates significant manual work for acquisitions teams, for both approval plans and firm orders. Being able to specify Quantity ordered AND Number of Items (per set) would disambiguate how many volumes we expect to receive, and allow for code that could specify barcode/enumeration on each of… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

14. Support Processing System Control Number (035) Updates in Imported Authority Record Updates

    Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.

    This was clarified by Ex Libris in a support ticket (case 07255325). According to that explanation, the workflow for updating automatically bibliographic records based on updated authority records (in case of ID-based authority linking and local authority records) - https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/060Working_with_Authority_Records#Updating_the_Authority_Record_ID_Automatically_in_Bibliographic_Records - only applies when the imported record is new to Alma, but not when an update to an existing authority record is concerned.

    This is a severe limitation of the current design in Alma that prevents the automatic handling of authority record merges, which involve, in the authority record, the addition of 035 $z (canceled system control number) and in the bib record the replacement of $0 in authority-controlled fields and the update of those authority-controlled fields based on the updated $0.

    One possible workaround is to manually modify tag 035 in the authority record after the imported authority record update, e.g. by adding "035 $a0", so that authority-control jobs will process the tag anew. An alternative workaround is to delete the existing authority record in Alma before the import, allowing the updated record to be treated as new and processed by Alma's authority-control jobs. However, both workarounds require manual intervention, which undermines the idea of library automation.

    We request that Alma processes updates to tag 035 even when the incoming authority record is an update rather than a new record. This enhancement reduces the need for manual intervention and improves the efficiency of authority control in Alma.

    Currently, Alma's authority-control jobs do not process updates to MARC21 authority tag 035 (System Control Number) when the update occurs via an authority import profile as the update of an existing record, i.e. there is a match between the existing authority record in Alma and the incoming authority record via the authority import profile. In contrast, the update is processed when there is no match with an existing record, i.e. the record is new to Alma, or, when the authority record has been updated manually via the MDE.

    This was clarified by Ex Libris in a support ticket (case 07255325).… more

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

15. When creating a new local portfolio generates a new bib record, the portfolio's material type should determine the bib's material type.

    ExL documentation states, "When creating a new bibliographic record, the portfolio material is not taken into account. Thus, when you add a local portfolio and set a specific electronic material type, a bibliographic record is also created, but with 'Book' as the material, regardless of the portfolio's material. When adding ISSN, the material remains to be 'Book'. "

    This is imprecise and creates issues for discovery: when I create a new portfolio for a Kanopy video and select Electronic Material Type=Streaming Video, the bib record is encoded for a book. So in Primo, the video's Resource Type shows as book, and that facet will not work properly for users limiting to "Video/Film." I believe this would be fixed if the new bib was given a value "g" (projected medium) in LDR 06 if Electronic Mat Type=Streaming Video, rather than a value of "a" (language material).

    Please consider mapping material type in the bib record/leader to the Electronic Material Type chosen during local portfolio creation.

    ExL documentation states, "When creating a new bibliographic record, the portfolio material is not taken into account. Thus, when you add a local portfolio and set a specific electronic material type, a bibliographic record is also created, but with 'Book' as the material, regardless of the portfolio's material. When adding ISSN, the material remains to be 'Book'. "

    This is imprecise and creates issues for discovery: when I create a new portfolio for a Kanopy video and select Electronic Material Type=Streaming Video, the bib record is encoded for a book. So in Primo, the video's Resource Type shows as book,… more

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

16. Allow option to only send scheduled report from Analytics object if report has results

    We want to set up reports to help us monitor for data inconsistencies and other issues that need addressing. We have noticed that we can set up reports as analytics objects and users can subscribe to them, but the report is sent even if there are no results.

    We should have the option to not send empty reports, and only send if the report brought back one or more records.

    22 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

17. Auto Populated Copy ID Number Added to New Item Records

    I'd like to propose streamlining the Alma item record creation process by enabling automatic population of the Copy ID field with "1" for new items. The system should also allow for easy modification of this default value for subsequent copies (2, 3, 4, etc.).

    Currently, the manual entry of "1" is often missed, leading to errors and requiring time-consuming batch corrections. Implementing this auto-population feature would significantly reduce data entry time and the need for monthly clean-up reports, ultimately improving efficiency and data accuracy.

    This idea was previously suggested by Leona Hughes on June 24, 2020, but was closed: (Automatic Designated Copy ID Number Added to New Item Records: https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/40743703-automatic-designated-copy-id-number-added-to-new-i).

    Given the ongoing impact of this issue, I believe revisiting this idea would be highly beneficial.

    Thank you for your time and consideration.

    I'd like to propose streamlining the Alma item record creation process by enabling automatic population of the Copy ID field with "1" for new items. The system should also allow for easy modification of this default value for subsequent copies (2, 3, 4, etc.).

    Currently, the manual entry of "1" is often missed, leading to errors and requiring time-consuming batch corrections. Implementing this auto-population feature would significantly reduce data entry time and the need for monthly clean-up reports, ultimately improving efficiency and data accuracy.

    This idea was previously suggested by Leona Hughes on June 24, 2020, but was closed: (Automatic… more

    7 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

18. Autoload collections – Better identification

    Autoload collections are not always clearly identified in Alma. The default name of the collection does not always mention this information and there is no specific tag which can be searched or displayed in the CZ releases reports. This can be the source of useless changes by EIO or creation of cases.
    We do not want to add terms like ‘AutoHoldings’ or ‘Autoload’ in the public name of the collection as this is not an useful information for end-users on Primo.

    It would thus be very useful to tag these collections with the mention ”Autoload” in the Alma collection search results, in the CZ releases reports and to allow the search on collections concerned by this functionality.

    Autoload collections are not always clearly identified in Alma. The default name of the collection does not always mention this information and there is no specific tag which can be searched or displayed in the CZ releases reports. This can be the source of useless changes by EIO or creation of cases.
    We do not want to add terms like ‘AutoHoldings’ or ‘Autoload’ in the public name of the collection as this is not an useful information for end-users on Primo.

    It would thus be very useful to tag these collections with the mention ”Autoload” in the Alma collection search… more

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

19. Add a Public Note to all representations at the collection level

    This function, that exist in the configuration of an electronic collection, doesn't exist in a digital collection, so there is no other way to add a text to all records that will be shown in Primo.

    32 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    2 comments  ·  Resource Management - Digital  ·  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 an ability to change the "owning library" at acquisitions level

    Organizational mergers or splits of libraries can occur at any time, necessitating the management of changes in the library landscape even after the migration process.

    They involve the transfer of collections and data between libraries. While Alma supports the transfers of holding and item information between libraries, there are currently (as of Dec‘24) technical limitations when it comes to moving acquisitions data. This functionality is not yet supported by Alma.

    We therefore propose implementing a solution that facilitates the seamless transfer of purchase orders, invoices, as well as linked vendor data and budget transactions between (owning) libraries within Alma. There should also be a support for various acquisition types (e.g., gifts, exchanges)

    For detailed information and considerations, see the appendixes.

    See also CERV Enhancement AENH-I-36404

    Organizational mergers or splits of libraries can occur at any time, necessitating the management of changes in the library landscape even after the migration process.

    They involve the transfer of collections and data between libraries. While Alma supports the transfers of holding and item information between libraries, there are currently (as of Dec‘24) technical limitations when it comes to moving acquisitions data. This functionality is not yet supported by Alma.

    We therefore propose implementing a solution that facilitates the seamless transfer of purchase orders, invoices, as well as linked vendor data and budget transactions between (owning) libraries within Alma. There… more

    • 

    • 

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating