- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Desired Outcome Goal:
Include all (or almost all) item fields as subfields in the Z30-1 or Z30-2 output field produced by expand_doc_bib_z30 (for example, when moving Aleph item information to a different system).
Column 3 in the ./xxx01/tab/expand_doc_bib_z30 table specifies what subfield each z30 field will be mapped to.
Any z30 field can be included in this table. The name needs to match exactly the name of the field as it appears in ./alephm/source/copy/Z30. Leave the first 2 active-library lines as is – though the subfield codes can be changed. See also KCS Q&A Article # KB 22462, What is expand_doc_bib_z30 and What Fields Can it Include? (https://exlibrisgroup.my.salesforce....Can-it-Include).
The ./copy/Z30 file shows the Z30 fields. Only the lowest level fields can be specified. If there's a 04 level, it cannot be specified at the 02 or 03 level. If there's a 03 level it can not be specified at the 02 level. (See example in Additional Information). The 26 lower-case letters, 26 upper-case letters, and 10 Arabic numerals can be used as subfield codes.
Note: the subfield codes of the fields and the order of the fields in expand_doc_bib_z30 can be changed as desired.
02 Z30-REC-KEY-3. S
03 Z30-VENDOR-CODE PICTURE X(20).
03 Z30-INVOICE-NUMBER PICTURE X(15).
03 Z30-LINE-NUMBER PICTURE 9(5).
This must be in the table as:
*Not* as z30-rec-key-3.
2. The expand_doc_bib_z30 header states: “It is also possible to define another tag using the parameter TAG in tab_expand if Z30-1/Z30-2 should not be created.”
This means that the Z30-2 (ISSUE) and Z30-1 (non-ISSUE) tags would both be changed to the TAG specified for the expand_doc_bib_z30 entry in tab_expand.
PRINT-03 expand_doc_bib_hol_usm TAG=931
Note: expand_doc_add_order_info can be used to expand order info into a bib record -- just as expand_doc_bib_z30 is used to expand item info.
- Article last edited: 28-Feb-2016