ava_location_priority for sorting AVA fields
- Article Type: Q&A
- Product: Aleph
- Product Version: 20, 21, 22, 23
It seems that the order of sublibraries/locations in the z00p AVA fields sent to Primo can be controlled by the xxx01/tab/ava_location_priority table. Do all sublibraries and collections need to be added to the table?
The expand_doc_bib_avail was enhanced with v22 rep_changes 58 and 2077 to read the (new) ava_location_priority table. This can be used to control the order of the sublibraries in the records published to Primo.
Subfield $$p, which holds the location priority, is only created when there is at least one entry in the table for the sublibrary (collection code can be assigned as #####). If such an entry is missing, the AVA field is put at the top of the AVA fields that are sorted alphabetical by sublibrary. So it would make sense to add a line for any sublibrary in the list.
- Article last edited: 1/28/2016