RDA field 264 not sent by EDI
- Product: Aleph
- Product Version: 20, 21, 22, 23
- Relevant for Installation Type: Dedicated-Direct, Direct, Local, Total Care
Symptoms
The data for the 264 tag (imprint, publisher, etc.) is not being received by the vendor. It can be seen in the XML but not the outgoing EDI.
Defect Status
Corrected by v22 rep_change 2288 and v23 rep_change 29....
Description: EDI - Adding RDA support for an outgoing order.
Till now, the EDI imprint information is taken from '260' tag.
Now, when '264' tag (RDA) exists, it will have priority over '260' tag and the EDI imprint data will be taken from it.
If there is missing data for place, publisher or year, taken from the 264 field, the system will try ot get it from the 260 field.
=======
IMPORTANT NOTE:
The current EDI functionality will stay as is: the IMPRINT information will be sent in EDI only when the short doc imprint is populated (Z13-IMPRINT). It is the library responsibility to configure their tables to support RDA.
For example:
If the library adds '264' tag to a BIB record but the imprint was empty based on tab22 definitions, the EDI imprint will not be sent. The library will need to reconfigure tab22 to populate the z13-imprint from '264' tag and run Update Short Bibliographic Records (manage-07).
The changed program is xml_to_edi_orders .
See the article "Integrating RDA fields in ACQ reports" https://knowledge.exlibrisgroup.com/...in_ACQ_reports in this regard.
- Article last edited: 12-Feb-2016