Call Numbers are an essential piece of information for anyone using a catalogue, especially if getting lengthy hits after a search. Totally agree they need to add this feature to the public interface side so catalogue users can extract complete information about individual titles.

Alma is a solution for staff, perhaps, but not for end users; their only access is via Primo.

FWIW, if you take the Excel export from Primo, and create a set by uploading that file in Alma, you can then print that out and it'll display the call number. Shouldn't be that hard but it is a work around!

This is an alignment issue, as possible in Primo Back Office with Alma, but not Primo VE.

Did not make it through round 2 of NERS 2023.

(15 complexity points, got 2929 votes).

Personally I consider this more of a bug fix than a feature request. We're talking about library catalogues here.

(Ideally the patrons should be able to decide if they want to export all call numbers or only the ones of a specific library.)

NERS 8256, round 2 open for voting now.

I'd be very useful if the call number for physical items is added as an extra colum in the export!

We need this!

Essential for our workflow!

It was included on this year's NERS ballot but alas didn't make it through; it was not even in top 20. But it is indeed possible in Primo BO with the AVA field, and not possible in Primo VE (which doesn't use that field) so it's a parity issue. Perhaps it could be addressed as such?

Any update on this?

We are looking to have the call # and physical location added to the Excel export for VE as well. I don't believe the suggestion for adding the AVA field for display applies to VE?

Our researchers are looking for the ability to include call number in the Excel file export, so that they have quick reference to location within the libraries. We would support it being added, based on this user need.

Thank you very much, Stacey https://ideas.exlibrisgroup.com/users/195318681-stacey-van-groll for your input. Will investigate adding the AVA field for display in order for it to be included in the Excel export.

Hi Natasja, you should be able to do this by adding the AVA field for display. We have a local practice of using LC in the bib record and then adding a Local running call number at the holdings level when we shift items to our off-site Warehouse. So, a little different use than yours in open stacks. I've already had a Local Call Number field for display, but just from the 090 in the bib for resources without LC. To date I've only grabbed both the AVA and the 090 for search data, just in case it's the only information a user wrote down from a record, but am now adding the AVA also for display as well, so that it is included in the Excel Export.