1) Exclude 'Failed - Usage Not Ready for Requested Dates' usage reports from appearing in the SUSHI Weekly Report.
2) Also include user option to suppress past usage reports with no available usage from reporting again in the SUSHI Weekly Report.

When Uploading a File, it should be possible to preview the file before clicking on send, to prevent the wrong file from being uploaded.

It should be possible to Complete a request when using Ship Item Digitally in the same way that this option exists when supplying via Ship Item

It should be possible to add a Note at the same time as Uploading a File to a patron. Currently, we have to send a separate Patron Query Template after the link has been sent.

The import profiles to load bibliographic records and attach holdings and items are currently limited to only ONE holdings record per bibliographic record. We would like the ability to create multiple holdings records, one for each distinctive call number. After loading records, if we have multiple copies it is manual work to create new holdings records when the holdings have all been merged into one.

We would like to have WebHooks, that are triggered by acquisition events.

For example sending of POs shall trigger a Web Hook (similar to a finished job) to start subsequent processes via the Alma-API. In principle, we could also use the packaging job, however, if orders are sent directly, this does not work.

Use case: Extrenal setting of call numbers, inventory counters, setting of item properties within multiple item orders.

Invoices can include different VAT percentages in different invoice lines, so VAT must be calculated per invoice line level (not in invoice level), but because library is not paying VAT (paid centrally by the university), VAT should not be expended from the library’s funds in Alma.

The problem is that when the checkbox “VAT per invoice line” is ticked, the checkbox “Expended from fund” is automatically ticked and it can’t be un-ticked.

It should be possible to choose “Expended from fund” to be ticked or un-ticked, when “VAT per invoice line” is ticked.

Hello,

Most archival materials are cataloged as follows:
LDR pos. 6 = p
LDR pos. 8 = a
Currently, the facet in Alma show these kind of materials as "Undefined".
Adding a facet of "Achieve Material" according to LDR pos.8 = a, would be very useful.

Thanks.

We would like to be able to include item barcodes as a field on both the Pick from Shelf and the Print Slip reports. Since holds are placed on a specific item in almost all cases, it makes sense to be able to confirm you are retrieving the correct copy from the shelf. Many of our locations work in a way that requires them to search for specific items rather than simply by title or call number and having barcodes associated with holds would also make this work easier

We'd like to be able to see the patron name for the hold request on the "Pick From Shelf" list. (See attached image.)

I would like to make it an option to change the color scheme of the ALMA top ribbon/possibly sidebar to differentiate locations especially between Main Circulation Desk and Acquisitions, of which I have to switch regularly. This would save me time spent on correcting errors due to being in the wrong location for a particular procedure.

In the new metadata editor there is no back button anymore! Please bring it back. I often go from editing a new item into the holdings record to add a call number and then need to go directly back into the item creation page. With no back button from the MDE it takes three times as long.

We would like to use the date of death of the creator in order to define a rule for embargo. This information is available in the subfield $$d from the 100/700

Currently it's possible to define a rule for embargo where Access is denied based on any of the following date:

Additional Publication Year
Fixed Date
MMS Creation Date
Publication Year
Representation Creation Date

We've defined the following Sort Subfields Task but there seems to be a problem in combination with "GND Authorities -Preferred Term correction"

700: iaqbcdtmnrpkolgfs0
710: iagbndctkplfs0
711: iagendctkplfs0

The subfield i which we defined as first in 700/710/711 is suddenly put last. If this happen, the latest job that was run is always Authorities - Preferred Term correction

In any case, the sorting should be the way we defined it in the Sort Subfields Task

We've defined the following Sort Subfields Task but there seems to be a problem in combination with "GND Authorities -Preferred Term correction"

700: iaqbcdtmnrpkolgfs0
710: iagbndctkplfs0
711: iagendctkplfs0

The subfield i which we defined as first in 700/710/711 is suddenly put last. If this happen, the latest job that was run is always Authorities - Preferred Term correction

In any case, the sorting should be the way we defined it in the Sort Subfields Task

In the Browse shelf listing, currently, the “call number level” is set by default to “Holding call number” and it’s not configurable.
It’s possible to set a default value for the “call number type” but not for the “call number level”. We would like to have the possibilty to change the “call number level” by default as it's for the “call number type”.

We are grateful that there is a print daemon. Since our network does not allow any application to access the Internet, version 1.2 will not run without affecting the secured network configuration.

The improvement I request is to implement a network configuration setting to configure the proxy settings the way as it works in Browsers.

Kind regards
Urs Wider

Alma provides the possibility of local authorities for cataloguing in an Institutional Zone and its local records. Unfortunately I cannot use those local authorities if I work in a Network Zone environment for records linked to the Network Zone.
I would like to:
a. define the local authority in the Institution Zone.
b. Link to this local authority in a local field 6XX (= with $$9LOCAL) via F3 in MDE even if the bibliographic record is linked to the Network Zone.

From Admin > Run a Job > Delete External Data Sources, users should be given a list of codes instead of labels. If libraries are importing different sets from the same source and want to use the same label, if external data needs to be deleted, staff have to temporarily relabel the appropriate discovery import profile.

Any drop down list in Alma should be using unique fields not fields that can be not unique.