1984 results found

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

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

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

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

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

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

   •  

   102 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

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

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

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

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

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

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

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

   Since different subfields… more

   •  

   159 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Add "Which coverage statement will be applied?" option to "Change Electronic portfolio information" job

   The "Change Electronic portfolio information" job includes the task "Remove local coverage" which removes local coverage from all the portfolios in a set so the only coverage remaining is global coverage. I run this in cases where the global coverage was once poor, so we loaded local coverage, but now the global coverage has been fixed and is good, so now we want to remove our local coverage and use the good global coverage. However, "Remove local coverage" does not also change the "Which coverage statement will be applied?" radio button from "Only local" to "Only global."

   It is important that this switch be made so the global coverage will appear in Alma Analytics in the "coverage statement combined" field, which only displays the coverage statement indicated by the "Which coverage statement will be applied?" radio button. Currently, my only way to switch the radio button to "Only global" in a batch is to use the portfolio loader. This is an extra step that removes the convenience of using the "Change Electronic portfolio information" job--now that I have to use the portfolio loader, I could have just made my coverage date changes using the portfolio loader.

   When I asked Ex Libris Support about why "Remove local coverage" doesn't also switch "Which Coverage statement will be applied?" to Global," they said this behavior by design because some customers might not want "Which coverage statement will be applied?" to change to "Only Global."

   Thus, in this idea, I suggest that the Ex Libris added a "Which coverage statement will be applied?" option to the "Change Electronic portfolio information" job. That way, customers with my same use case will be able to switch this field to "Only global" when they remove local coverage, and customers who want to choose a different "Which coverage statement will be applied" option will be able to do so.

   I attached a mockup showing what this option would look like in the Change Electronic Portfolio Information job screen. A user could check the box next to this field, and there is a dropdown box where the user could choose between the 4 options (which match the options we can choose within the portfolio editor): Only local, Global and local, Global or local, or Only global.

   The "Change Electronic portfolio information" job includes the task "Remove local coverage" which removes local coverage from all the portfolios in a set so the only coverage remaining is global coverage. I run this in cases where the global coverage was once poor, so we loaded local coverage, but now the global coverage has been fixed and is good, so now we want to remove our local coverage and use the good global coverage. However, "Remove local coverage" does not also change the "Which coverage statement will be applied?" radio button from "Only local" to "Only global."

   It is important… more

   •  

   44 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

5. Search for ISBN with hyphens

   Previously, it was possible to search for ISBNs with hyphens (e.g., 978-82-693905-0-6) using the "All titles – keywords" search in Alma. However, this functionality no longer works with the release of the new title search.

   While the search still works if you manually switch from "keywords" to "ISBN," it would be much more convenient if ISBNs with hyphens were recognized in the keyword search as well. As it stands, users are forced to repeatedly switch search types, resulting in unnecessary clicks and a less efficient workflow.

   76 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 - 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. Allow for an authority file to be addressed by different codes in $2 of various BIB fields

   In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

   In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2, while the terms are, as the code suggests, actually a subset of our integrated authority file “gnd”. The same goes for notated music terms in BIB field 348. These too are a subset of our integrated authority file and are marked by the official LoC /MARC code “gnd-music” in $2.

   Alma currently does not allow to link the above mentioned terms to said authority file, because the content of $2 does not exactly match the code for the authority file, which is “gnd”. This problem could be solved by allowing for different codes in $2 to address one and the same authority file.

   In Alma the authority file, a subject or term stems from, is defined by the content of $2 in various 6XX fields. This code controls the F3 functionality, as well as the linking process and the various jobs like PTC. Each and every authority file is addressed by one specific code.

   In the German speaking countries we use an integrated authority file (GND), which amongst names and subjects, also includes genre/form terms. For historical reasons the genre/form terms in BIB field 655 are marked with the official LoC /MARC Genre/Form Code and Term Source Codes “gnd-content” and “gnd-carrier” in $2,… more

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

7. Securing Alma access by two factor authentication (2FA) in combination with time-based one-time passwords (TOTP)

   2FA and TOTP are common and standard methods for securing access to IT systems. These concepts should be implemented in order to secure access to Alma also. A respective implementation should replace the multi-factor authentication currently implemented in Alma since it lacks security for at least the following reasons:
   - Sending a link by email is insecure since email hardly can be viewed as a secure transport medium.
   - Using email for transferring a second factor hardly allows to keep the second factor as being independent from the device on which Alma access takes place.
   - The link which is used as second factor for Alma authentication works independent from the password authenticated session and therefore can be used on any device anywhere in the world to gain access to Alma (within one hour).

   2FA and TOTP are common and standard methods for securing access to IT systems. These concepts should be implemented in order to secure access to Alma also. A respective implementation should replace the multi-factor authentication currently implemented in Alma since it lacks security for at least the following reasons:
   - Sending a link by email is insecure since email hardly can be viewed as a secure transport medium.
   - Using email for transferring a second factor hardly allows to keep the second factor as being independent from the device on which Alma access takes place.
   - The link which is… more

   154 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

8. Improve Alma Analytics to allow for more straightforward and accurate COUNTER usage data and Cost Per Use reporting.

   Improve Alma Analytics to allow for more straightforward and accurate COUNTER usage data and Cost Per Use reporting. To address the following:

   1. Simplify CPU Calculation: Improve the system to allow straightforward calculation of Cost Per Use (CPU) by including financial data in the usage subject area, eliminating the need for SQL joins.

   2. Increase Data Update Frequency: Increase the frequency of usage data updates in the e-inventory subject area and fix the date of the job, as the current monthly updates, which have variable dates, cause scheduling issues.

   3. Enhance Data Accuracy: Address inaccuracies and missing data due to limited match points (title and ISSN). Examples include:
      a/. Titles with only print ISSN in the Counter file.
      b/. Title changes by users, leading to mismatches.
      c/. Inability to link usage to CPU due to mismatched ISSN or titles, resulting in incorrect CPU calculations.

   Improve Alma Analytics to allow for more straightforward and accurate COUNTER usage data and Cost Per Use reporting. To address the following:

   1. Simplify CPU Calculation: Improve the system to allow straightforward calculation of Cost Per Use (CPU) by including financial data in the usage subject area, eliminating the need for SQL joins.

   2. Increase Data Update Frequency: Increase the frequency of usage data updates in the e-inventory subject area and fix the date of the job, as the current monthly updates, which have variable dates, cause scheduling issues.

   3. Enhance Data Accuracy: Address inaccuracies and missing data due to limited match points… more

   124 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

9. Allow a NR to run with the PTC job

   TL;DR:
   We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

   Background:
   In November 2024 Ex-Libris added a new functionality to the PTC job:
   MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

   Problem:
   The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
   in all other cases, the existing indicators remain.
   We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not a bug.
   I understand that other institutions have different reasons for having a NR run whenever the PTC changes a record.

   Request:
   We would like to have the option to add a normalization task to the PTC in the configuration menu, that way we will be able to fix problems that arise from this job.

   TL;DR:
   We would like to have the ability to run a normalization rule whenever the PTC modifies a record.

   Background:
   In November 2024 Ex-Libris added a new functionality to the PTC job:
   MARC 21 Preferred Term Correction Can Flip Headings with Cross-Reference in Different Field
   https://knowledge.exlibrisgroup.com/Alma/Release_Notes/2024/Alma_2024_Release_Notes?mon=202411

   Problem:
   The PTC job only changes the first indicator correctly when the PTC job changes a field into 630.
   in all other cases, the existing indicators remain.
   We opened a case and spoke directly with Ex-Libris, but were told that the PTC job runs as intended, and that not handling the indicators is not… more

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

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

    36 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  ·  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. Add and improve audit logging and system event tracking for changes to Alma configuration

    Many institutions have needs and requirements to be able to track when Alma configurations change, and who changed them.

    This is especially true because many Alma "administrator" roles combine complex librarian tasks with systems configuration abilities. For example, Catalog Administrator or General Systems Administrator is required to create new metadata import profiles - a task that catalogers need to do regularly. But, both roles also grant additional abilities to configure Alma behavior for resource management,
    integrations and the like.

    Use cases include:

    • Monitoring changes as part of standard internal audit review. For example, an institution may identify that even though electronic resources staff need Fulfillment Administrator in order to manage general electronic services, none of those electronic resources staff should be changing other areas of fulfillment configuration. Because Alma's roles do not separate those duties, the secondary requirement would then become to monitor changes in the fulfillment configuration areas outside Discovery Interface Display Logic to know which staff members are changing them and when. We would want a regular report that logged information like the name of the logged in user, the name of the table, the date/time the change occurred, what row(s) changed, and what the prior and new values were in those rows.

    • Troubleshooting unexpected Alma behavior. For example, suppose that custom linking for a set of CDI databases begins to behave unexpectedly. Configuration for those database links is handled in Configuration > Discovery. A staff member hears about the database issue, goes in and attempts to fix it,
      but can't. The issue then gets reported to a systems staff member. At that point, the systems staff member can only see the last updated by and timestamp. They need to be able to see who edited that table, and when, to help figure out what
      might have happened.

    Analytics currently has a subject area called "System Events" that does a poor job of capturing this information. For example, there is a system event type 6141 - Mapping table updated. However, the information captured there is internal tracking information and not actually relevant to mapping table updates, according to Ex Libris support.

    Improving how this data is kept and tracked would go a long way towards reducing risk of Alma not functioning as expected, and making it easier for institutions to manage audit requirements and troubleshooting needs for Alma users.

    Many institutions have needs and requirements to be able to track when Alma configurations change, and who changed them.

    This is especially true because many Alma "administrator" roles combine complex librarian tasks with systems configuration abilities. For example, Catalog Administrator or General Systems Administrator is required to create new metadata import profiles - a task that catalogers need to do regularly. But, both roles also grant additional abilities to configure Alma behavior for resource management,
    integrations and the like.

    Use cases include:

    • Monitoring changes as part of standard internal audit review. For example, an institution may identify that even though… more

    138 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

12. separate work orders from patron requests

    On the results from a physical titles search, each title shows the number of requests pending for that title. This number includes both patron physical item requests and internal work orders. In order to see what requests fall into which category, you have to click on the Requests link and wait for the information to load in the slider pane (this can take some time if the number of requests is large). Then you can filter by request/process type.
    It would be useful for these two categories of requests to be separated from each other. For example, we circulate laptops for the term and allow requesting when all items in a record are unavailable. We also use work orders to track machines that go out for maintenance. I may want to know how many patrons are waiting for a machine at a glance, such as when I'm working with a patron and they are trying to decide if they want to get on the request list. If I go by the number displayed on the title record, I don't know how many of those "requests" are actually work orders.
    In the images, you can see that our MacBook Airs show 28 requests. Of those, 7 are work orders.

    On the results from a physical titles search, each title shows the number of requests pending for that title. This number includes both patron physical item requests and internal work orders. In order to see what requests fall into which category, you have to click on the Requests link and wait for the information to load in the slider pane (this can take some time if the number of requests is large). Then you can filter by request/process type.
    It would be useful for these two categories of requests to be separated from each other. For example, we circulate laptops… more

    •  

    •  

    52 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

13. Overdue Fine in different periods

    After changing the "Overdue Fine" parameter, the entire fee is recalculated with the new value.
    According to the law, the fee should be counted up to the change with the old value and after the change with the new value.
    E.g. until 2024-12-31 parameter=0.2, then parameter=0.4
    This is especially important in public libraries.

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

14. Block when overdue: add a "days per overdue days" unit of measurement option

    Hello everyone,
    when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
    There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first one, "days...", generates larger block periods, but they are over in a shorter time; on the other hand, when using the second one, "open days...", the block periods are smaller but they take more time to be fulfilled.
    https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/030Fulfillment/080Configuring_Fulfillment/Configuring_User_Blocks#Configuring_User_Blocks_Due_to_Overdue_Loans
    So, I guess that the "perfect" option for us would be something in between, an "Days per open overdue days" which does not currently exist in Alma.
    Would it be possible to add this "Days per open overdue days" option and, as its opposite, an "Open days per overdue days"?
    Thanks a lot in advance and best regards.

    Hello everyone,
    when defining user loan blocks, there are several options available to be used as "units of measurement" in order to calculate the loan block period: we are in doubt about which option fits best for us, as we want to set up this option in the most convenient way for our patrons.
    There are lots of options, both "discrete" and "cumulative" (we have chosen "cumulative), but in our opinion, we think that the most appropriate ones are "days per overdue days" and "open days per open overdue days", although they both have their pros and cons: the first… more

    57 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

15. Manage Deleted Repository--ability to select and restore a group of records

    Manage Deleted Repository is a helpful feature helps us restore records that were mistakenly deleted. However, it only allows us to restore records one at a time by clicking a "Restore" button next to each record. This is not workable when a large number of records need to be restored. We need functionality that will allow us to select and restore groups of records.

    The Restoring Records Removed or Changed by Jobs functionality (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/020Manual_Jobs_on_Defined_Sets#Restoring_Records_Removed_or_Changed_by_Jobs) does not sufficiently address this need, as it can only restore repository content deleted by a job, not records deleted manually. Also, even in cases where records were mistakenly deleted by a job, it is possible that much of the rest of the job was correct (such as a CZ sync job) so we do not want to restore the whole job; we want to restore just some of the deleted repository content.

    This Idea suggests that, in the Manage Deleted Repository, there should be checkboxes, like in the Community Zone Updates Task List and the Authority Control Task List, that allow us to select individual items or select all items on the page. There should also be options to Restore Selected or Restore All. I have attached a mockup (based on CZ Updates Task List and Authority Control Task List) showing how this would look. For example, in the interface shown in the mockup, I could:

    1) Check individual checkboxes next to records 1, 2, and 3 and then click "Restore Selected" to restore the 3 pieces of content.
    2) Check the "Select All" button to select all 50 records on the page and then click "Restore Selected" to restore all 50 pieces of content.
    3) Select "Restore All" to restore all 305 pieces of content retrieved by my current search criteria.

    Manage Deleted Repository is a helpful feature helps us restore records that were mistakenly deleted. However, it only allows us to restore records one at a time by clicking a "Restore" button next to each record. This is not workable when a large number of records need to be restored. We need functionality that will allow us to select and restore groups of records.

    The Restoring Records Removed or Changed by Jobs functionality (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/050Administration/070Managing_Jobs/020Manual_Jobs_on_Defined_Sets#Restoring_Records_Removed_or_Changed_by_Jobs) does not sufficiently address this need, as it can only restore repository content deleted by a job, not records deleted manually. Also, even in… 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…)
    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

16. Alma collections: Allow to add multiple titles from network zone

    We very much appreciate that the idea Alma collections: Allow to add from network zone (https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/44841430-alma-collections-allow-to-add-from-network-zone), which allows to add NZ records to IZ collections, could be developed. However, we think the usefulness of this feature would be greatly improved if it was possible to add more than one record at a time, for example via sets.

    41 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  ·  Collaborative Networks  ·  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. Allow for Almost Arbitrary Conditions in General Electronic Services

    Currently for a general electronic service we can only create conditions based on metadata already contained in the given BIB record. Please provide a way to let the link resolver check any condition which is computable within a reasonable short amount of time!

    Example Use Case:
    Our library network offers a web service taking any given ISBN, ISSN or Union Catalog ID and returning 'true' if there is a BIB record for the corresponding resource in the union catalog and at least one of the network's libraries has an item of this resource available for ILL. Otherwise the web service returns 'false'. If we were able to let the Alma link resolver check a given ISBN, ISSN or Union Catalog ID against that web service we could offer an ILL service if and only if there is a pretty good chance that there is an item available via ILL.

    Instead the only general electronic service we can offer currently is a context-insensitive "check whether ILL might be an option" link which resolves to our library network's SFX service menu(!) where an ILL service shows up if and only if there is a pretty good chance that there is an item available via ILL. (Yes, SFX is able to perform such "magic" thanks to so called "plugin thresholds". Their implementation in SFX as an arbitrary local script that evaluates the desired condition does not fit into a cloud environment, of course, but letting a web service evaluate the desired condition and return 'true' or 'false' does.)

    Please note that this enhancement request has also been submitted to the CERV portal: https://enhancements.exlibrisusers.org/ideas/AENH-I-36524

    Currently for a general electronic service we can only create conditions based on metadata already contained in the given BIB record. Please provide a way to let the link resolver check any condition which is computable within a reasonable short amount of time!

    Example Use Case:
    Our library network offers a web service taking any given ISBN, ISSN or Union Catalog ID and returning 'true' if there is a BIB record for the corresponding resource in the union catalog and at least one of the network's libraries has an item of this resource available for ILL. Otherwise the web service… more

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

18. Simplify item scanning when processing is complete

    Operators would benefit from not having to choose a Work Order Type and Status when the treatment is complete. It is not always easy to find out which cataloguing or repair operation has been carried out on an item. And above all, it's not useful if Done =“No” is selected.

    Couldn't you put this last line at the beginning of the form, and open the Work Order Type and Status boxes only if "Yes" has been ticked, rather than the other way round?

    Thank you and thank you for supporting this modest proposal.

    Nicolas

    84 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

19. Better information design for pop-ups in the New Circ UI

    When managing return items in Alma: information in the pop-up on subsequent steps in the process is difficult to read due to a small typeface. Also, not all information is relevant or, strictly speaking, correct (e.g. "item is not on loan" even when there is an active request).

    We would like to see a larger font in general, or, if this is not feasible, at least the requester's name in bold typeface. This would add a much needed visual cue for staff processing returns.

    The bullet point about the item not being on loan could be supressed as it offers no relevant information at this stage.

    Similar ideas:
    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/49531262-usability-issues-with-the-new-circ-ui?
    https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/49843755-configure-return-pop-up-notes

    When managing return items in Alma: information in the pop-up on subsequent steps in the process is difficult to read due to a small typeface. Also, not all information is relevant or, strictly speaking, correct (e.g. "item is not on loan" even when there is an active request).

    We would like to see a larger font in general, or, if this is not feasible, at least the requester's name in bold typeface. This would add a much needed visual cue for staff processing returns.

    The bullet point about the item not being on loan could be supressed as it offers… more

    •  

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Feature Requests for the NZ Fulfillment Network

    1. Access to Borrowing History Across NZ Institutions
       • Feature Request:
       Enable librarians to view the borrowing history of their university patrons at other NZ institutions.
       • Current Situation:
       a. On Network Activity tab, it only displays current FN loans and current FN requests.
       b. Librarians cannot directly access the borrowing history or detailed transfer records when their patron borrows books from another NZ institution.
       c. Assistance from librarians at the other institution is required, which delays service and limits the ability to provide comprehensive patron support.

    2. Show more information on Network Activity tab
       • Feature Request:
       On Network Activity tab, allow librarians to see (1) the pickup location selected by patrons (2) request queue of that item (3) loan time of patron loan in the format MM/DD/YYYY HH:MM
       • Current Situation:
       a. Patrons occasionally overlook the correct pickup location and arbitrarily select a library, causing confusion at service desks.
       b. Service desks cannot retrieve the patron’s selected pickup location in the system, as this information is only displayed in the patron’s email.
       c. Being able to see the request queue of that item and loan time can make the librarian's workflow smoother.
       d. Additional details are provided in the attached document.

    Many thanks.

    1. Access to Borrowing History Across NZ Institutions
       • Feature Request:
       Enable librarians to view the borrowing history of their university patrons at other NZ institutions.
       • Current Situation:
       a. On Network Activity tab, it only displays current FN loans and current FN requests.
       b. Librarians cannot directly access the borrowing history or detailed transfer records when their patron borrows books from another NZ institution.
       c. Assistance from librarians at the other institution is required, which delays service and limits the ability to provide comprehensive patron support.

    2. Show more information on Network Activity tab
       • Feature Request:
       On Network Activity tab,… more

    •  

    •  

    128 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  ·  Collaborative Networks  ·  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