Tech Blog

Publishing to SUNCAT: Experience of the University of York

The content of this article was contributed by Kingsley Boulton from the University of York

Scope of data published

We report to SUNCAT our print and electronic journal holdings. The majority of our journals are now in electronic format.
Note that in the University of York, print and electronic holdings are always attached to separate bibliographic records, though the publishing process can manage shared print/electronic bibliographic records.
The conditions we need to specify are not available for an All Titles set. We thus had to create separate Physical Titles and Electronic Titles sets.


These are the conditions in the Physical Titles set we use, SUNCAT physical titles:
Physical Titles where All titles (Tag Suppressed equals “No”) and Holding (Library equals “University Library” or Library equals “King’s Manor” or Library equals “University Library – Special Collections” or Library equals “York Minster Library” or Library equals “National Railway Museum” or Library equals “Borthwick Institute”) and Physical items (Material type equals “Journal”)

These are the conditions in the Electronic Titles set we use, SUNCAT electronic titles:
Electronic Titles where All titles (Tag Suppressed equals “No”) and Electronic Portfolio (Material Type equals “Journal”)

Normalization Rule
SUNCAT require the LDR position 9 (Character encoding scheme) of all records to be populated with ‘a’ (for UCS/Unicode). In a large number of our records that flag is blank. As a result the following normalization rule, LDR field position 9 replace with a, is run as part of the publishing process:

rule "change LDR pos 9 to a"
(not existsControl "LDR.{9,1}.a")
replaceControlContents "LDR.{9,1}" with "a"

Configuration of publishing profile

The following are screenshots of the publishing two profiles we use for print and electronic titles respectively:

Publish print records to SUNCAT:

Not all UK Alma libraries have used the same physical inventory enrichment mapping. SUNCAT can manage variations but perhaps an agreed mapping might have been useful.

Publish electronic records to SUNCAT:

Frequency of updates

It has been agreed with SUNCAT that the publishing process will be run monthly, so that SUNCAT will receive new, updated and deleted records on the first of each month.

Leave a Reply