1773 results found

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

   46 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

2. Fulfilment find patron

   Fulfilment - enter patron name & select from list - should not have to additionally click 'Go'/enter to display record

   45 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  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. Exclude expired users from bursar integration job

   Our bursar is not currently able to collect charges from users who are no longer at the university. So we want to be able to able to exclude these patrons from the reports that are sent to the bursar with bursar integration. The fact that this doesn’t exist now has prevented us from implementing integration.
   We would like this functionality to be an additional filter in the bursar integration settings that would exclude users whose expiration date is in the past. If it could specify an actual or relative date, this would be an additional improvement.

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

4. Making Copy to Community / Network / Institution configurable

   When searching for authoritiy records, there are options to copy an authority to Network or to Community or even to the Institution zone.

   We understand there may be institutions and consortia administrating different kind of vocabularies at different levels, but this is not the case for all. We see in our consortium too many mistakes due to catalogers selecting the wrong button when importing a record. We therefore strongly suggest making all these options configurable, so that it will be possible to hide the buttons.

   •  

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

5. Add Electronic Service Information Update Job

   Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.

   Job Name: Change Electronic service information
   Job Description: Update Electronic service information for a set of Electronic services
   Job Content Type: Electronic Service
   Job Type: Information Update

   Use Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time to add the same CLIENTID value in the Linking Parser Parameters section of the Linking tab.

   Desired Workflow: Create a set of all affected electronic services. Run the Change Electronic service information job to edit the linking parser parameter in bulk by specifying both the parameter name (CLIENTID) and value (e.g., 12345). The job systematically updates the value of the CLIENTID parameter for each electronic service in the set.

   Electronic Portfolios and Electronic Collections each have an Information Update job in Alma. Electronic services need the same functionality because they are also affected in bulk by changes.

   Job Name: Change Electronic service information
   Job Description: Update Electronic service information for a set of Electronic services
   Job Content Type: Electronic Service
   Job Type: Information Update

   Use Case: ProQuest began requiring a value for the CLIENTID parameter in the Linking Parser Parameters section of all ProQuest electronic services. With over 50 ProQuest electronic collections activated, that meant that over 50 electronic services had to be manually edited one at a time… more

   45 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Resource Management - Electronic  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. Add Associated PO Line field to New Order Import Profile & Update PO Lines job

   Alma lacks the functionality for batch adding an Additional PO Line to a group of PO Lines. Because Alma lacks this functionality, a great deal of manual work is required.

   Here is the use case: we made a large prepayment (the parent POL), and now we are creating technical orders (the child POLs) for all the items we chose to purchase with that pre-payment. We need each of the child POLs to have the parent POL as its Associated PO Line. We can create the child POLs in a batch using a New Order Import Profile. However, we have no way to batch-assign the Associated PO Line to all the child POLs. The New Order Import Profile does not have an Additional PO Line field, and the PO Line jobs in Alma do not include the ability to add or update an Associated PO Line. So, there is no way to add an Associated PO Line aside from manually editing each individual PO Line. This is a lot of manual work. We suggest this problem should be addressed in two ways:

   1) We need to be able to add an Associated PO Line as part of the New Order Import Profile. This should be one of the options in the PO Line Information tab.

   2) Associated PO Line should be one of the fields that is updatable in the Update PO Lines Information job. This will ensure we can batch-add an Associated PO Line to PO Lines that are already in Alma.

   Alma lacks the functionality for batch adding an Additional PO Line to a group of PO Lines. Because Alma lacks this functionality, a great deal of manual work is required.

   Here is the use case: we made a large prepayment (the parent POL), and now we are creating technical orders (the child POLs) for all the items we chose to purchase with that pre-payment. We need each of the child POLs to have the parent POL as its Associated PO Line. We can create the child POLs in a batch using a New Order Import Profile. However, we have no… more

   45 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  ·  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. Add Item‑Level Usage Option to Deselection & Retention Project Scopes

   When determining eligibility for Deselection/Retention Projects, Alma is currently only evaluating title‑level usage rather than item‑level. This means that loans of Lost or Withdrawn items are being considered and the project is actively excluding items that have not circulated for years (because a now lost/withdrawn copy circulated more recently). Further to this, this information is not readily available without going into Alma Analytics.

   Proposal: add an option within the Scope configuration that allows institutions to choose whether usage should be evaluated at:

   Title Level (current behaviour)
   OR
   Item Level (requested enhancement)

   This enhancement would:

   • Improve accuracy of deselection lists
   • Prevent historical usage from withdrawn/lost items from skewing scope
   • Increase trust in the tool’s output
   • Better support libraries that rely on item‑specific evaluation for weeding

   When determining eligibility for Deselection/Retention Projects, Alma is currently only evaluating title‑level usage rather than item‑level. This means that loans of Lost or Withdrawn items are being considered and the project is actively excluding items that have not circulated for years (because a now lost/withdrawn copy circulated more recently). Further to this, this information is not readily available without going into Alma Analytics.

   Proposal: add an option within the Scope configuration that allows institutions to choose whether usage should be evaluated at:

   Title Level (current behaviour)
   OR
   Item Level (requested enhancement)

   This enhancement would:

   • Improve accuracy of deselection lists
   • Prevent… more
   45 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

8. Allow more than 50 POLs on a PO via manual packaging

   Right now, in the Purchase Order - Package screen, you can only package 50 POLs onto one PO. The "PO lines to package" screen will only display 50 POLs max, and if you select all, then go to the next screen, it removes everything from the first screen that you selected. This means only 50 POLs max can be put on a PO. This is frustrating when we put in an order for more than 50 items and have to create multiple POs for a single order. I think the easy fix would be to have those POLs remain checked when you went to the next screen.

   Right now, in the Purchase Order - Package screen, you can only package 50 POLs onto one PO. The "PO lines to package" screen will only display 50 POLs max, and if you select all, then go to the next screen, it removes everything from the first screen that you selected. This means only 50 POLs max can be put on a PO. This is frustrating when we put in an order for more than 50 items and have to create multiple POs for a single order. I think the easy fix would be to have those POLs remain checked… more

   45 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

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

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

   45 votes

   Vote 0 votes Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  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. Link to next higher level when Alma can't match to article or chapter

    When Alma cannot successfully link to an article because of no exact match is found, it would be helpful for Alma to use alternative metadata, such as the page number, to target. It would also be useful to users to be taken to the next higher level of the publication, e.g., the journal issue page. If there is uncertainty about the issue, then users should be taken to the journal page.
    This problem frequently arises for short pieces and book reviews. For example, some journals publish book reviews in a section entitled, "Book Reviews", rather than as separate articles. In such cases, Alma's link resolver returns an error and no useful information for the user.

    When Alma cannot successfully link to an article because of no exact match is found, it would be helpful for Alma to use alternative metadata, such as the page number, to target. It would also be useful to users to be taken to the next higher level of the publication, e.g., the journal issue page. If there is uncertainty about the issue, then users should be taken to the journal page.
    This problem frequently arises for short pieces and book reviews. For example, some journals publish book reviews in a section entitled, "Book Reviews", rather than as separate articles. In… more

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

11. Ability to remove default suppressed filter from resource locate

    When using resource locate within reading lists to link a citation to a title the default search filters out suppressed title records.

    This could be changed by adding mms_tagSuppressed to the Locate Citation By Fields table (Fulfillment Configuration > Courses > Locate Citation By Fields). Allowing it to be disabled.

    This would be useful for us as we regularly use suppressed records where the physical item is not held but a representation of a chapter or article is and the representation will not be discoverable by primo. This prevents a title with no holdings appearing.

    • 

    44 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

12. Always add newly implemented fields to API and Analytics

    We have repeatedly run into issues with the following: Things implemented in the Alma UI are not automatically available via API and/or Analytics.

    Recent examples include:
    * June 2020 "Can't edit restricted users" - Ex Libris offered to add this to the API, but not to Analytics
    * CDI Search activation status - as of now it is not clear whether we will have access to this via API

    To be honest: I am not willing to open an idea or NERS every time Ex Libris thinks it's nice to have something in the Alma UI, but do not care to implement for the API and/or Analytics. And I thought: Maybe neither are you.

    There might be cases where it actually makes sense to add a field to only one of the three systems. But these systems are interlinked and Ex Libris should handle them as such. Only in very rare cases such fields should only be available in Alma UI and there must be information included in the release notes why exactly something was not added to the API and/or Analytics.

    We have repeatedly run into issues with the following: Things implemented in the Alma UI are not automatically available via API and/or Analytics.

    Recent examples include:
    * June 2020 "Can't edit restricted users" - Ex Libris offered to add this to the API, but not to Analytics
    * CDI Search activation status - as of now it is not clear whether we will have access to this via API

    To be honest: I am not willing to open an idea or NERS every time Ex Libris thinks it's nice to have something in the Alma UI, but do not care… more

    44 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

13. Better flexibility / more weekly options when scheduling Fulfillment Job (i.e. Fees/Fines Notification Job)

    Hello,

    we would like to be more flexible, to have more options to choose from when scheduling the Fees/Fines Notifications Job (or even better: all Fulfillment Jobs).

    Currently, we are using the only weekly option available (every Tuesday at 11:00), but since some of our legally relevant Fees/Fines Notification Profiles are set to printed letters, the offered time slot could not be much worse.

    When we have signed and sealed the letters, there is no chance at all to get them out by the same day's post.

    Please add at least another weekly time slot in the early morning hours, like 6:00, 7:00 or 8:00. We are not to choosy as the weekday is concerned.

    Thank you so much for considering and/our supporting our plea.

    Eva-Maria Horita, FHB Aachen

    Hello,

    we would like to be more flexible, to have more options to choose from when scheduling the Fees/Fines Notifications Job (or even better: all Fulfillment Jobs).

    Currently, we are using the only weekly option available (every Tuesday at 11:00), but since some of our legally relevant Fees/Fines Notification Profiles are set to printed letters, the offered time slot could not be much worse.

    When we have signed and sealed the letters, there is no chance at all to get them out by the same day's post.

    Please add at least another weekly time slot in the early morning hours,… more

    •  

    44 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

14. Improve po_line_remove_interested_users_job

    The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.

    We request that:
    A. Institutions have the ability to set a delay on the job based on the date the PO line was closed. (E.g., the job runs weekly, but only deletes Interested Users in PO lines that were closed X number of days ago);
    B. The job is designed to run on PO lines that are closed but no longer in the department or in a work order (eliminating the risk that Interested Users will be deleted from a closed PO line before the item has left the department);
    C. Interested Users that are deleted in PO lines are also scrubbed from Analytics.

    The polineremoveinterestedusers job allows institutions to delete Interested Users from PO lines that have closed. However, there are many times when a PO line is closed before the item has left the department; consequently, running the polineremoveinterestedusers job means that interested users may be deleted before the item becomes available. Additionally, while the job removes the Interested Users from Alma, it does not remove the information from Analytics.

    We request that:
    A. Institutions have the ability to set a delay on the job based on the date the PO line was closed.… more

    44 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  ·  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. Add option to close library for borrowing or lending requests based on format of request

    A library can close for borrowing or lending requests and include dates when the library can't process borrowing or lending requests. It would be helpful and provide more efficient processing of borrowing and lending requests if requests could be deflected by format.

    As a borrowing library, there are times when a patron's article requests could be processed and sent to a lending library, but a physical request can't be processed.

    Borrowing physical requests may not be possible because the physical library building is closed, and the item can't be delivered to the location.

    It would be helpful to have the addition of format, physical and digital, to "Temporarily Inactive for borrowing" with an "Inactive dates range" for physical format and an "Inactive dates range" for digital format. This allows patrons to continue to enter requests for formats that can be filled.

    As a lending library, there are times when a library can supply physical items but not be able to process digital requests. This may because of staff expertise in handling digital requests.

    It would be helpful to have the addition of format, physical and digital, to "Temporary Inactive for lending" with an "Inactive dates range for physical format and an "Inactive dates range" for digital format. The ability to deflect lending requests for formats the library can't fill quickly provides better service to the borrowing library.

    A library can close for borrowing or lending requests and include dates when the library can't process borrowing or lending requests. It would be helpful and provide more efficient processing of borrowing and lending requests if requests could be deflected by format.

    As a borrowing library, there are times when a patron's article requests could be processed and sent to a lending library, but a physical request can't be processed.

    Borrowing physical requests may not be possible because the physical library building is closed, and the item can't be delivered to the location.

    It would be helpful to have the… more

    44 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 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. Display “Service unavailability display message” at Collection Level in Primo

    Currently, the “Service unavailability display message” is only shown at the Journal and article level in Primo. It would be highly beneficial to extend this functionality to the collection level as well. This enhancement would provide users with clearer information about service availability, improving their overall experience and reducing confusion when accessing collections.

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

17. Ignore call number prefix ($$k) in BROWSE SHELFLIST in Alma

    Alma's Browse Shelflist function includes the call number prefix (holdings record field 852 $$k) when generating the browse list. At the University at Buffalo, we use that prefix for oversize volumes, and for a variety of other sub-locations, designations and shelving areas.

    As a result, any holdings with a prefix ($$k) does not show up alongside holdings in the same call number range, essentially hiding many titles from staff who seek to browse the shelf list.

    An advanced search for specific library holdings, permanent call number type, and permanent call number does not remedy this issue, as it does not enable us to truly browse the shelflist.

    Please reconfigure Alma's browse search to ignore (but, ideally, still display) the call number prefix when generating this index.

    It seems that this was done for Primo, and we would like to see this functionality mirrored in Alma.

    Alma's Browse Shelflist function includes the call number prefix (holdings record field 852 $$k) when generating the browse list. At the University at Buffalo, we use that prefix for oversize volumes, and for a variety of other sub-locations, designations and shelving areas.

    As a result, any holdings with a prefix ($$k) does not show up alongside holdings in the same call number range, essentially hiding many titles from staff who seek to browse the shelf list.

    An advanced search for specific library holdings, permanent call number type, and permanent call number does not remedy this issue, as it does not… more

    44 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

18. Display all assigned PO lines in task list

    With the introduction of the new PO line layout, it became possible to manually assign PO lines, regardless of their status. However, the Alma task list (tasks requiring your attention) still only displays assigned PO lines, when they are in review. Assigned PO lines with different statuses tend to be overlooked.

    It would be very useful for ACQ staff to be able to see all PO lines assigned to them in the task list. This could also encourage more use of the "Assign To" function.

    44 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

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

    44 votes

    Vote 0 votes Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

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

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Submit Rating

20. Compare All Institutions in the NZ

    The Network Zone can be made more useful if it were possible to use it to quickly compare institutions by setting. A common time consuming task is to check to see which institutions have one setting or another configured and which do not. To accomplish this currently, it is necessary to either log in to each institution and click around or log in to the NZ and then using the drop down to choose an institution and click around. Either way, staff need to open up all the institutions.

    Alternatively, it would be great if, for configurations that lend themselves to this, there was a button to "Compare all institutions" that would open a table listing all the institutions and the value of the chosen configuration. Making this table exportable would also be useful.

    For example, the configuration, "AI Usage Profile" under Configuration -> General -> AI Features could have a "Compare all institutions" button next to Cancel and Save.

    Another example, any of the "Other Settings" tables under Configuration -> Fulfillment/General/User Management/etc -> General Configuration could have a "Compare all institutions" option in the ellipse next to each row.

    Having a spreadsheet that shows what value is configured at each institutions would allow consortial staff to quickly know which institutions need to be updated without having to open every institution.

    The Network Zone can be made more useful if it were possible to use it to quickly compare institutions by setting. A common time consuming task is to check to see which institutions have one setting or another configured and which do not. To accomplish this currently, it is necessary to either log in to each institution and click around or log in to the NZ and then using the drop down to choose an institution and click around. Either way, staff need to open up all the institutions.

    Alternatively, it would be great if, for configurations that lend themselves… more

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