Skip to main content
OCLC Support

Data exchange

Details of the 7 enhancements and 17 bug fixes for exporting, importing, third-party discovery synchronisation and RSS feed generation can be found on this page.

This information is part of OLIB 9>> Release Notes>> Service Pack 14


Enhancements

IMS Ref Description
OLB-13905
OLB-13988
Data can now be sent to WorldCat data sync over sftp. To facilitate this, a small change is required to the Output Format to select the appropriate OCLC data centre. This should be done in conjunction with OCLC in order to ensure that the OCLC side of the process is configured for the appropriate data centre.
OLB-15034

When synchronising holdings with WorldCat, titles should be allowed to be Modified To Be Checked without causing the removal of all holdings

NERC

OLB-15059

Provide a way to re-synchronise all of the holdings for a symbol with WorldCat.

Please contact OCLC for advice on this process.

FamilySearch

OLB-15216 The export to third party by FTP processing must be separated from the WorldCat sync processing.
OLB-15231

Provide a way to run the automated export part of daystart on demand.

This is now possible with the use of the Process Now action on output formats. This also provides debug information for support purposes in the Trace Information domain.

Note that, for RSS feeds, it will not carry out the file based parts of the process as this can only be done during daystart.

OLB-15296

Modify the CP_COTI tag to output all levels of the serial title hierarchy.

FamilySearch

Bug fixes

IMS Ref Description
OLB-10736

The MARC import does not populate the copies.copyseq field when copies are created by the import.

DEFRA

OLB-14559

Title batch deletion is not sending holdings removal via the WorldCat metadata API.

FamilySearch, NERC, Logos

OLB-14900

Export to 3rd Party Delivery Systems: Records for first push not exported when track status set to 'Y'.

SWIMS

OLB-14962

Overnight exports to third-party systems failing after upgrade to SP12.

NE NHS

OLB-14986

OLSTF imports should create new objects for new titles and not match objects with the same locator for older titles.

SWIMS

OLB-15031

When syncing with WorldCat, if a format changed record fails to export the OPAC Synch Status is set to -ERRX for both status entries.

NERC

OLB-15036

MARC Exports can generate invalid data in tag 300 by not starting it with a valid subfield.

NERC, PXL

OLB-15038

Invalidating WorldCat holdings due to a format change is not necessary for records that have no OCLC Number and are yet to be authorised (-PEND)

NERC

OLB-15108

Add the namespace label to the <collection> tag when exporting MARC XML.

This was made possible by editing the MARC-XML Outptut Format as below:

Adjust the header procedure to specify the desired namespace for the MARC content:

LibraryExportGeneral.ExpHeader('XML',
 'namespace:collection xmlns:namespace="http://www.loc.gov/MARC21/slim"')

This provides the system administrator with control over which namespace is utilised in the export and allows for the XML to be embedded in a larger XML wrapper if required, without leading to unavoidable namespace clashes.

If amended, an OLIB Web rebuild is required for the change to take effect.

IMechE

OLB-15177 OLSTF Import Batch not loading data.
OLB-15181

The Configurable user import process can fail with ORU-10028 leading to ORA-01400.

Chartered Society of Physiotherapy

OLB-15197

No diagnostic information to assist export issues.

Natural Resources Wales

OLB-15220

The configurable user import does not extend reference data mappings.

Chartered Society of Physiotherapy

OLB-15282

ORA-06502 error specified in email from email notification for export to external system by FTP output format. This occurred when there was no message body text configured on the Output Format.

OLB-15305 MARC21 export/MARC21 view: creation of duplicate tags - intermittent issue
OLB-15313

Unable to export department and course information.

NE NHS

OLB-15314

Exporting data for Excel does not transfer diacritic content correctly.

Standard Output Formats have been updated. In order to remedy this for custom output formats, the new function "fix_diacritics" should be specified in the Header Procedure field. Refer to "Example Excel Export" (-25) for an example.

FamilySearch

 

 

  • Was this article helpful?