• Product: Aleph
• Product Version: 20, 21, 22, 23
• Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care

Description:
We've added COLLECTION=Y in the PRIMO section of tab_expand, but are not seeing the additional AVA fields in records exported to Primo. E.g., we added a second collection in the ENGIN sublibrary to 000933874, and used p_publish_06 to create a record set, which I then copied over to our Primo staging server. The exported record had the additional 852 field, but still only had one AVA.

Resolution:
ue_21 is the publishing daemon. It processes the z07p records produced by ue_01. 
After making a change to tab_expand for publishing, ue_21 needs to be stopped/restarted in order for the change to be in effect.
Looking at the run_e_21 logs in abc01 $data_scratch, we see that ue_21 was last restarted on June 8.

See also, article " Aleph Publishing: Only 1 AVA field per Sublibrary despite multiple Collections " (KB 16384-15201).

• Article last edited: 12-Mar-2016