Question

Why is AVA field for publishing to Primo not created for all records?

Answer

Items that are defined in ./xxx50/tab/tab15.lng as not OPAC displayable (column 10) are not included in the expand. So items with a specific item and/or item process status don’t cause the creation of an AVA field.

Example
./xxx50/tab/tab15.lng:
! COL 2. 2; NUM {00-99}; #;
! Item status;
! Item status;
! COL 10. 1; ALPHA {Y,N}, UPPER; ;
! Web OPAC;
! display/do not display copy in Web OPAC;
! 1    2  3 4      5                         6 7 8 9 1 1 1 1 1 1  1 1
!                                                    0 1 2 3 4 5  6 7
!!!!!-!!-!!-!-!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!-!-!-!-!-!-!-!-!-!-!!-!-!
15K   79 ## L ACQ                            N N N N N N N N N 00 N
15L   79 ## L ACQ                            N N N N N N N N N 00 N
15C   79 ## L ACQ                            N N N N N N N N N 00 N
15K   11 ## L Regular Loan Kunst             Y Y Y N Y Y N N N 00 N
15L   11 ## L Regular Loan Closed Stack      Y Y C N Y Y N N N 00 N
15C   11 ## L Regular Loan Closed Stack      Y Y C N Y Y N N N 00 N

For item status “79” there will be no display in OPAC according to the “N” in column 10 of tab15.lng and therefore there will also be no AVA field created whereas for status "11" items will be displayed in OPAC and and AVA field will be created.

Additional Information

See also:

* the article " Aleph Z00P records missing AVA fields *MASTER RECORD* " and

* the document " The Aleph Publishing Mechanism ", Chapter 2.1

Category: Publishing

Subject: Publishing Services

• Article last edited: 10/8/2013