Slide 1

Data export to Summon

Mark Huppert, ANU Library
System & Web Coordinator
[email protected]


Slide 2

Disclaimer
• Neither ANU or I represent Serials
Solutions – I am here to discuss practical
issues, not to promote Summon

2


Slide 3

Overview
• The practicalities
– Planning decisions
– Data preparation
– Daily updates

3


Slide 4

Planning, Preparation
• What’s included in your uploads?
– Rare books? Electronic? Suppressed? Your
partners on the same system?

• BCODE3 (Bib status codes)
• Location codes (branches)

4


Slide 5

Planning, Preparation
• Use “tunnelling” with a 9xx field and the
export table
• Bib record; branches, bcode3 -> 907

5


Slide 6

Call numbers
• Bib or Item call no.
• Summon displays two ways:
– Dynamic screen scraping (good for Item cn)
– Bib marc fields (you can get this suppressed)

6


Slide 7

Send daily ‘new’ and ‘delete’ files
• What does ‘new’ mean?
At ANU, only a totally processed bib record receives
a CAT DATE. ‘New’ = CAT DATE since the last upload

• What does ‘delete’ mean?
It has been suppressed since the last upload
(BCODE3=n)

7


Slide 8

Send daily ‘new’ and ‘delete’ files
• Saved search (must change date every

day by hand



8


Slide 9

Relative date searching (please)

9


Slide 10

Send daily ‘new’ and ‘delete’ files
• Task Builder / Scheduler: create *.out file
of marc records and send to ANU server
• Perl script – change file names daily to
include a date stamp and ftp to Serials
Solutions

10


Slide 11

Upload to SS daily with new file names
• Why not Task Builder for the whole job?
– Need to change filenames every day,
eg: anu-catalog-new-2011-11-15.marc
anu-catalog-del-2011-11-15.marc

11