1880 results found

1. Provide DOI agency integrations for Alma Digital

   There is now a handle integration for Alma Digital as well as Esploro - great.

   There are Crossref and DataCite DOI integrations for Esploro (https://knowledge.exlibrisgroup.com/Esploro/Product_Documentation/Esploro_Online_Help_(English)/Esploro_Integration/Configuring_External_Systems_in_Esploro), but not for Alma D.

   Please consider adapting these for Alma Digital resources. This would support institutions who might be hosting student theses and other scholarly comms in Alma D, and complement the handle integration.

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

2. PDA import profiles for electronic titles - limit matching to specific electronic collection

   The ability to limit matching of imported MARC record against existing records with portfolios in a selected electronic collection was release for repository import profiles in the Feb 2024 release in response to a previous Ideas Exchange submission:
   https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/15312516-repository-import-profiles-for-electronic-titles

   Echoing the comments added to that Ideas Exchange post following the release, it would be really helpful if the same functionality could be release for PDA import profiles too, for the same reasons originally stated.

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

3. Add Block for Resource Sharing Shipping from Scan-In Items

   Alma allows an institution to set rsallowactionsonscan_in to false. When a staff person tries to Receive or Ship a resource sharing request from Scan-In, the staff person sees a pop-up message advising them to use Alma Receiving or Shipping.

   When Scan-in Items is used on a lending request that should be shipped, a pop up message displays that “Shipping is required to be done from the dedicated screen, Are you sure you want to continue?” There is a “Cancel” or “Confirm” option. If the staff person chooses “Confirm” and scans the item barcode again then another pop up displays asking if they want to continue with the message “Scanning in item (scanned barcode provided) will complete lending resource sharing request (external identifier provided). Are you sure you want to perform this action?” The staff person is given the option to “Cancel” or “Confirm”. If the staff person selects “Confirm” the request is completed for the lending and the borrowing library.

   This enhancement request is to add block preferences for Ship of a lending request using Scan-In that are similar to the options available for Receive of a borrowing request. If staff are blocked from using Scan-In Items for lending requests this will prevent the accidental closing of a lending and borrowing request.

   There is an option to block the Receive of a borrowing request using Scan-In https://knowledge.exlibrisgroup.com/Alma/Release_Notes/030_2016/07June_2016/Alma_June_2016_Release_Notes/05Resource_Sharing_-_June_2016_Enhancements

   We would like a block preference to be added for Ship of a lending request similar to the block on Receive of borrowing requests.

   Possible settings for block of Ship of lending request from Scan-In Items:

   · Block- The pop-up warning appears and the Ship may not be carried out.

   · Override by Manager- The pop-up warning appears and may be overridden by users with manager roles.

   · Handle Automatically- The pop-up warning does not appear and the Ship action will be carried out automatically, with the appropriate actions taken to handle the resource sharing request. This is the default option.

   If the block is overridden, the following actions take place:

   · The lending request status is updated to Shipped Physically.

   · The Ship ISO message is sent.

   · The item is placed in a temporary location.

   Alma allows an institution to set rsallowactionsonscan_in to false. When a staff person tries to Receive or Ship a resource sharing request from Scan-In, the staff person sees a pop-up message advising them to use Alma Receiving or Shipping.

   When Scan-in Items is used on a lending request that should be shipped, a pop up message displays that “Shipping is required to be done from the dedicated screen, Are you sure you want to continue?” There is a “Cancel” or “Confirm” option. If the staff person chooses “Confirm” and scans the item barcode again then another… 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 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

4. Add Bursar Transaction ID dimension to Fines and Fees Subject Area in Analytics

   Bursar Transaction ID is a critical data element when an institution uses a Bursar integration profile to export fines/fees and import payments. We recently implemented this integration and are looking at ways to reconcile Alma transactions with data extracted from our bursar. If Bursar Transaction ID were present as a dimension in Analytics, this would be much easier. It should be added.

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

5. Display of the 1,000 most recent linked data records in Alma and Primo

   It is not possible to display all linked data records since the number is limited to 1’000. For better user convenience, at least the 1’000 most recent records should be displayed and not the 1’000 oldest or randomly selected records.
   Especially in the case of journals and monographic series that have been published for a long time, 1,000 linked records are not uncommon and the most recent ones are usually of interest.

   12 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

6. Resource Sharing Loan Due Date

   It would be ideal if a Loan Due Date could be a standardized length. Currently Loan Due Date= Due Date minus transit time and holdshelf. Often this results in an inconsistent length of time. This is most evident when loan periods are short. For example, if an item has a 14 day loan policy according to the Loan TOU, and the Lending Resource Sharing TOU Due Date is set at 21 days, the loan period could be 17 days.
   We would prefer that Loan Due Dates follow the pattern:
   If Loan TOU is shorter than {Due Date - Transit and Holdshelf time}, loan length should= Loan TOU. Otherwise, follow existing rule for Loan Due Date.

   It would be ideal if a Loan Due Date could be a standardized length. Currently Loan Due Date= Due Date minus transit time and holdshelf. Often this results in an inconsistent length of time. This is most evident when loan periods are short. For example, if an item has a 14 day loan policy according to the Loan TOU, and the Lending Resource Sharing TOU Due Date is set at 21 days, the loan period could be 17 days.
   We would prefer that Loan Due Dates follow the pattern:
   If Loan TOU is shorter than {Due Date - Transit and… 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…)
   0 comments  ·  Resource Sharing  ·  Delete…  ·  Admin →
   How important is this to you?

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

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Death of a patron - Need to immediately and permanently cease sending all letters

   In the unfortunate event that we learn that a patron passes away, we need a quick, clear, and finite procedure to immediately and permanently cease/stop any and all IZ and NZ notifications to the patron's email account, especially those that are tied to a SIS load (Example: Banner). College administration directs the library to ensure no emails are sent to the deceased's email account. We need to be able to definitively state to college administrators "Absolutely zero communications, automated or manually generated, will be sent regarding the deceased patron's library account from the IZ or NZ."

   Existing work-arounds include toggling the account to internal, removing the email from the account, or entering a fake email; or use of the "Patron Opt-in/Opt-out function" that does not cover all possible letters. However, work-arounds are insufficient and not best practice. As it stands, any patron account toggled external (account information controlled by SIS), will continue to be subject to automated and manual notifications outside of the letter list. Our college uses "Banner" for our SIS. Whereas Banner will eventually remove the patron, there is a governing policy which states the college must retain student records for three years, which means the purge date could be up to three years away from the expiration date of the patron account. Our instance of Alma is also part of a shared library system (consortia NZ) and part of an AFN (automated fulfillment network) and thus linked records may exist in other systems, which would not apply in most Alma instances. As part of the AFN, patron notifications originate from the lending institution and not the patron's home institution. We do have a procedure to remove items involving the AFN from the patron record, however that takes time. The need to block notifications is immediate under these circumstances.

   We recently received notification about the tragic death of a patron and the college made it clear that the family should not (ever, now or in the future) receive any notifications about any college business such as overdue notices. I am 100% in agreement with the college's policy. We would like to honor that policy, but if we toggle the student's account as internal, the account will likely not be purged according to the college's policies. It would be best if we maintained the record as externally controlled by SIS and simply prevent generation of any notifications, period. The need is to have a very simple way to instantly stop any and all notifications from being generated from the deceased's account in their home institution as well as any linked accounts via a simple, clearly labeled toggle switch available in the patron's account by an operator with the appropriate permissions/role.

   In the unfortunate event that we learn that a patron passes away, we need a quick, clear, and finite procedure to immediately and permanently cease/stop any and all IZ and NZ notifications to the patron's email account, especially those that are tied to a SIS load (Example: Banner). College administration directs the library to ensure no emails are sent to the deceased's email account. We need to be able to definitively state to college administrators "Absolutely zero communications, automated or manually generated, will be sent regarding the deceased patron's library account from the IZ or NZ."

   Existing work-arounds include toggling… more

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

8. Display "Bibliographic Rank" for Electronic Collections IZ/NG

   In the November 2023 Alma release, "bibliographic rank" information displays for Community Zone collections (please see attached screenshot and https://ideas.exlibrisgroup.com/forums/308173/suggestions/39648964) but this information does not display for Community Zone collections activated in the Institution Zone/Network Zone.

   This makes it more time consuming to evaluate the bib record quality of collections already activated because one would need to search for them one by one in the CZ.

   Please display "bibliograpic rank" for all elections collections (CZ and local too if possible) in a library's Institution Zone and Network Zone and also make this data available in Analytics so reports can be run to easily see this data in bulk.

   In the November 2023 Alma release, "bibliographic rank" information displays for Community Zone collections (please see attached screenshot and https://ideas.exlibrisgroup.com/forums/308173/suggestions/39648964) but this information does not display for Community Zone collections activated in the Institution Zone/Network Zone.

   This makes it more time consuming to evaluate the bib record quality of collections already activated because one would need to search for them one by one in the CZ.

   Please display "bibliograpic rank" for all elections collections (CZ and local too if possible) in a library's Institution Zone and Network Zone and also make this data available in Analytics so reports can… more

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

9. Please, let us use the full power of rft_dat / pid again!

   rftdat (OpenURL 1.0) and pid (OpenURL 0.1), respectively, is one of if not the most powerful OpenURL field(s) and SFX allowed the customer to make full use of this power. It's such a shame for the Alma link resolver not even being able to parse a local identifier from rftdat / pid in cases when these parameters contain anything else than just the identifier (like in rftdat=<GVI>BV012345678</GVI>). So please allow regular expressions to define a pattern for a substring to extract from the value passed in rftdat / pid.

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

10. Don´t share locations when working in Alma in multiple tabs in the same browser

    Since May 2024 Release it is possible to work in Alma in multiple tabs in the same browser.

    Multiple tabs functionality works
    .) in the same Alma environment
    .) for the same logged-in user

    The aim of the new feature is to enhance productivity and efficiency by enabling users to simultaneously work on multiple workflows.

    However, it is not possible to be logged-in at two different desks/departments at the same time which would be necessary to really make working in Alma more efficient and to e.g. reduce mistakes when scanning in items.
    You might be working at the circulation desk and at the same time do subject cataloging. Thus you would have to be logged-in at the library´s circulation desk and at the subject cataloging work order department. Or you might be responsible for acquisition and at the same time also work at the library´s circulation desk. Thus you would have to be logged-in at the ACQ department and the circulation desk.

    Therefor we argue for another review. Locations should not be shared/synced across browser tabs.

    Since May 2024 Release it is possible to work in Alma in multiple tabs in the same browser.

    Multiple tabs functionality works
    .) in the same Alma environment
    .) for the same logged-in user

    The aim of the new feature is to enhance productivity and efficiency by enabling users to simultaneously work on multiple workflows.

    However, it is not possible to be logged-in at two different desks/departments at the same time which would be necessary to really make working in Alma more efficient and to e.g. reduce mistakes when scanning in items.
    You might be working at the circulation desk… more

    5 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

11. Add the ability to search ( and save query ) for holdings with suppressed tag yes

    Please add the ability to search ( and save query as a set ) for holdings with suppressed tag yes.
    Right now we can search for Holding having Tag Suppressed at Title level. This is not enough and is sometimes misleading (e.g. when a Title has 2 holdings, one suppressed and one not suppressed).

    We need to identify, save as set and manipulate holdings having tag suppressed at holdings level. This info has been added at Items level in Analytics, and is useful in case of report, but we need to work at Holdings Level in Alma with real time records.

    Please add the ability to search ( and save query as a set ) for holdings with suppressed tag yes.
    Right now we can search for Holding having Tag Suppressed at Title level. This is not enough and is sometimes misleading (e.g. when a Title has 2 holdings, one suppressed and one not suppressed).

    We need to identify, save as set and manipulate holdings having tag suppressed at holdings level. This info has been added at Items level in Analytics, and is useful in case of report, but we need to work at Holdings Level in Alma with real time… more

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

12. Make "Change expected date"-button available for unclaimed PO lines

    Currently, the function “Change Expected Date” is only available, when a PO line is in claim.

    However, it happens often, that vendors announce a delayed publishing date before a POL is claimed. It would be very practical, if in cases like these, the expected date could be changed via the button "Change Expected Date" as well, instead of having to open the POL > Edit > Change date > Save.

    It would save a few clicks and allow us to use the same workflow for the same task.

    10 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

13. Acquisitions API - Interested in user – add other identifiers in addition to Primary ID

    Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.

    We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.

    Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.

    It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.

    Ref #06652820 – Gobi Order API – interested_user - alma identifiers

    Currently Alma allows multiple identifiers to identify ALMA Users, however the Acquisitions API (Interested In users) mapping only allows “primary_ID”.

    We’d like any other identifiers used in Alma also be allowed in the mapping (e.g. Email Type). If this is added on the API parameter, staff can use the less sensitive info instead on vendor site.

    Noting that adding other identifiers in the Interested_User api parameters - is only doing what EOD acquisition workflow/mapping can already do.

    It is cumbersome for staff having need to search the requester’s primary id to be able to use this feature.

    Ref #06652820 –… more

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

14. Delete Bibliographic Records Job should be able to be restricted to the different Related Record Types

    The "Delete Bibliographic Records" job can be executed with "Do not delete if related to other records", but the parameter takes into account any Related Record Type to other bib records. We think it would be a great improvement if "Do not delete if related to other records" could be used to optionally select the exact Related Record Types that should be used for running the job. This selection would be very similar to the functionality for consortia "Restrict Deletion of Network Zone Bibliographic Records with Related Records " with Configuration > Resources > Collection Retention > Bibliographic Record Deletion - Related Records (https://knowledge.exlibrisgroup.com/Alma/Product_Documentation/010Alma_Online_Help_(English)/Metadata_Management/040Working_with_Bibliographic_Records/Restrict_Deletion_of_Network_Zone_Bibliographic_Records_with_Related_Records_and%2F%2For_Local_Extensions). A list should be added to the job parameter "Do not delete if related to other records" in which the various Related Record Types are stored. The libraries can then select only the Related Record Types for which "Do not delete if related to other records" should apply.

    The "Delete Bibliographic Records" job can be executed with "Do not delete if related to other records", but the parameter takes into account any Related Record Type to other bib records. We think it would be a great improvement if "Do not delete if related to other records" could be used to optionally select the exact Related Record Types that should be used for running the job. This selection would be very similar to the functionality for consortia "Restrict Deletion of Network Zone Bibliographic Records with Related Records " with Configuration > Resources > Collection Retention > Bibliographic Record Deletion… 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  ·  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

15. RS - Copy Request Note to Request Cancel Letter as well wheb Converting Borrowing requests into patron physical item requests

    The idea of
    Converting Borrowing requests into patron physical item requests
    has been implemented in 2019 (https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes?mon=201902BASE).
    Request Note is copied in the Note field of the request.

    However it would be great that, after a successful 'View local resources' the request note could also be copied to a Note field in the "Ful Cancel Request Letter" automatically received by the user, thus letting the user know more specific info we usually write in the request note. For example, we write there an additional link to the resource we might have found, Having that automatically in a Note in the Ful Cancel Request Letter emailied to the user would be useful.

    The idea of
    Converting Borrowing requests into patron physical item requests
    has been implemented in 2019 (https://knowledge.exlibrisgroup.com/Alma/Release_Notes/010_2019/Alma_2019_Release_Notes?mon=201902BASE).
    Request Note is copied in the Note field of the request.

    However it would be great that, after a successful 'View local resources' the request note could also be copied to a Note field in the "Ful Cancel Request Letter" automatically received by the user, thus letting the user know more specific info we usually write in the request note. For example, we write there an additional link to the resource we might have found, Having that automatically in a Note… more

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

16. Ability to add Request Note during Scan In to Work Order Deparment

    When performing Scan In on items to a Work Order Department, we have the ability to Set Status To our congigured status options, but no ability to add a Request Note, as we have if we were creating work order requests for some other Department.
    If we want to include a Request Note (to be included on any subsequent transit letters, for example), we then have to go into each entry in Manage In Process Items, locate the request that was created by the Scan In, and input a Request Note.
    It would be great if, while setting the status during Scan In as on the screenshot I've included, we also had the option of immediately adding a Request Note.
    (At my institution, someone figure out a way to batch-apply Request Notes via API, but this is not sustainable as it relies on one or two very busy people.)

    When performing Scan In on items to a Work Order Department, we have the ability to Set Status To our congigured status options, but no ability to add a Request Note, as we have if we were creating work order requests for some other Department.
    If we want to include a Request Note (to be included on any subsequent transit letters, for example), we then have to go into each entry in Manage In Process Items, locate the request that was created by the Scan In, and input a Request Note.
    It would be great if, while setting the status… 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  ·  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

17. Change physical items job -- adding notes improvement

    The "Append to field" option was added in November 2023, but two additional options are still required.

    1. 'Delimiter' should be an option.
       Now, the default delimiter is ";".
       Some institutions use symbols other than ";" as delimiters.
       For example, we use "|".
       Therefore, there is a need to make the delimiter optional.

    2. Writing forward in the note
       The current specification is to write backwards.
       Some institutions operate writing new information in the front of the note.
       There are three reasons for this.
       (1)It is easier to manually add notes at the front of the note.
       (2)It is easier to see on the Alma screen if the recent note is written forward.
       (3)Analytics cuts off backwards text if it exceeds VARCHAR(4000).
       Therefore, it should be optional to append forward or backward.

    The "Append to field" option was added in November 2023, but two additional options are still required.

    1. 'Delimiter' should be an option.
       Now, the default delimiter is ";".
       Some institutions use symbols other than ";" as delimiters.
       For example, we use "|".
       Therefore, there is a need to make the delimiter optional.

    2. Writing forward in the note
       The current specification is to write backwards.
       Some institutions operate writing new information in the front of the note.
       There are three reasons for this.
       (1)It is easier to manually add notes at the front of the note.
       (2)It is easier to see… more

    45 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

18. Make headings and descriptions editable for PO Lines without Inventory

    It is possible to create a PO Line without inventory by using the "Order without Inventory" option in the Acquisitions area of Alma. When creating such an order, Order Heading, Alternative Heading, and Description are all required fields. However, these fields are not editable after the order is created, so if you make a typo or there is a change to the name of a service (or whatever it is you are ordering), it is not possible to update that information in the heading. Ex Libris should make these fields editable after the order is created.

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

19. Add vendor UTB to Upload Electronic Holdings workflow

    The vendor UTB has already e-collections in CZ which have dozens of activations in the EMEA region. We've already contacted the vendor, and they would be willing to implement the Upload Electronic Holdings workflow.

    Vendor name: UTB
    Website: https://www.utb.de
    Contact: Tanja Klapputh, klapputh@utb.de
    Alma Interface name: UTB GmbH

    23 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

20. Addition of the Accrued fines field in the Fines and Fees subject area in Alma Analytics

    It would be great if there was an option in Alma Analytics to create a report with a list of people with a specific amount of accured fines if they had returned overdue documents on a given day (the day before actually).

    19 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