If an user has found an article that is not available electronic, but the library has the journal in print, the end user gets the list of holdings for the journal and can go into a specific holding to see the items.

In general we would like that when the end user has found an article they should only need to click on Request (or Digitize) and all relevant metadata are sent to Alma and the system selects the correct item to fulfill the request. If locate is not possible the librarian has enough information to work on the request.

The end-user are on the article level while the system are on the journal/issue level.

The end-user gets a lot of items and need to find the correct item either using the drop-downs or the navigational buttons. Not very user friendly. Could it be made easier to display the items that might fulfill the request by preselecting based on the metadata in the record?

This sceanrio are described in this screen-recording:
https://cloud.bibsys.no/index.php/s/XWASfMFpqbmFYpK

If there are no items to fulfill the request or the end user gives up finding the right item the Request a different issue option should contain more metadata that is sent to the library. This issue are adressed in this idea:
https://ideas.exlibrisgroup.com/forums/308173-alma/suggestions/36901999-improvements-to-request-form-when-article-is-not-a

We are disappointed with the technical support service provided by Ex Libris. We strongly believe that Ex Libris should provide customers with more effective, prompt and interactive service.

There should be an option to call or chat online in real time with a support person who has a sound understanding of the product in question. This would be in line with all system vendors we have previously dealt with.

We appreciate that there will be some issues that are designated as bugs or enhancements and will require more in depth investigation. However, a direct call/chat option with a properly trained support analyst would quickly and efficiently separate these issues from more general product queries. We are aware that there are many call-logging options used widely by other companies, such as FastCall, TenFold and RingDNA, which can be used to allow customer calls/chats to be registered directly in Salesforce. We believe that Ex Libris should implement this improvement as soon as possible.

Please vote to show your support for this idea and feel free to add comments relating to your experience of this issue.

Collaborative collecting agreements are becoming increasingly critical for libraries in managing collections and access across institutions. Formal agreements require libraries to commit to hold specific items. Currently, there is no way to mark this in records unless in free text notes, and no system checks in place for items to prevent accidental weeding of items that libraries have committed to retain. This idea outlines system functionality to ensure that libraries can safely manage committed collections.

• Two new fields in Alma Items: a Committed to Retain check box and a Retention note free text field (minimum of 200 characters)

• A system check that does not allow withdraw (delete) of items in batch, via api, or via the user interface for items with the Committed to Retain toggle set to yes, but instead presents an error noting that the item is Committed to Retain.

• Ability to update these fields manually through the user interface, update in batch via inventory batch job, and update via the item API

• Addition of the Committed to Retain value and Retention note to analytics to allow for collection analysis

We use the booking functionality in Alma for our Audio/Video-equipment. The equipment is administrated by our media production department, and is configured as a library in Alma.

The AV-library is the only place on campus patrons can check out and return AV-items. Apart from that, the AV-library also supports delivery to a library at a different campus (Kjeller).

• The transit time between the AV-library and Kjeller is set to 48 hours.
• The preview time on the equipment booking is set to one hour.

Use case:
When scanning an item due for pick-up at Kjeller within the next 48 hours, Alma insists you reshelf the item at the AV-library. Alma keeps on insisting you reshelf the item, until one hour before the booking time, alas until you are within the set preview time. Then, and only then, the item goes into transit to Kjeller, and the workflow is as expected. This of course, results in the equipment being too late for pick up at the Kjeller library.

If we change the preview time to 48 hours to accommodate the transit to Kjeller, the correct workflow kicks in at the expected time and the equipment goes into transit. Unfortunately, this affects the preview time for all the AV-items, regardless of pick up location. One apparent downside being patrons are blocked from checking out booked items, 48 hours prior to the booking time.

Our present work-around is to keep an eye on “Monitor Requests and Item Processes”, in order to sort out the equipment booked for pick up at the Kjeller library. Checking out the item as loaned for the patron before shipping it to Kjeller. The obvious downside, not being able to track the item in process, use scan in item … etc.

Suggested solution:
We would like to be able to make an exception to the preview time for bookings in the Fulfillment Unit based on pick up location: IF pick-up location=Kjeller THEN Preview period=48 hours.