INNOPAC/GLADIS INTERFACES Revised: July 1996
The "SUM download" is the superimposition of the GLADIS SUM field in serial records onto the "LIB.HAS" field in the INNOPAC checkin record. (The LAK field does NOT download).
Daily. Monday-Friday.
Any update to any GLADIS SUM field triggers the download. Deleting a SUM will NOT trigger download.
LOCAT=NEWS titles do NOT download (holdings are too long)
The only match point is the INNOPAC checkin number (CI# field).
(When doing retrospective conversion of INNOPAC records that have never had a checkin card attached, the CI field will probably not be present in GLADIS. Maintenance will either need to be held until upload occurs; or one-time double maintenance keying should be done.)
(e.g., 1 for summary holdings; 1 for cum indexes)
This downloads as 1 field. It concatenates the texts, displaying
them in the same order as they appear in GLADIS, separated
by a semi-colon.
Updating any SUM causes all locations to download with their respective SUMs. This download process will be triggered even if the particular location you are editing does not have a CI Field.
The INNOPAC LIB.HAS. is protected from the GLADIS download.
The phrase "See GLADIS" displays in the INNOPAC LIB.HAS field.
None.
The "download" is the superimposition of the bibliographic portions of GLADIS serial records on their counterparts in INNOPAC. This is done so that the GLADIS and INNOPAC records will remain in sync without the need for double keying.
A particular day's updates or new records are downloaded the following morning, Monday-Friday.
The download is triggered by any of the following:
The following categories of GLADIS records are excluded from the download and MUST BE MAINTAINED in INNOPAC:
The following fields download from GLADIS to INNOPAC and MUST BE MAINTAINED in GLADIS (except for the exclusion categories noted in C above).
| country | |
| language | |
| government publication code | |
| 100, | 110, 111, 130 Main entry |
| 245 | Title |
| 246 | Other forms of title |
| 247 | "Title varies" note |
| 250 | Edition statement |
| 260 | Imprint |
| 362 | Dates and volume designation |
| 490 | Series untraced or traced differently |
| 500 | Bibliographic note |
| 580 | Linking entry complexity note |
| 700, | 710, 711, 730 Added entry |
| 780 | Link notes, preceding entry |
| 785 | Link notes, succeeding entry |
| 800, | 810, 811, 830, 840 Series added entry |
| 909 | GLADIS record number (always downloads and replaces any existing one) |
The following INNOPAC bib fields are protected from the download and MUST BE MAINTAINED IN INNOPAC:
ALT CNTRL # BIB LEVEL FAXON ID FREQUENCY ISSN MARC UCB/OLD ORD XREF A XREF T
The only match point for the download is the INNOPAC bib number. It downloads only to bib numbers associated with PO numbers in the serial range (i.e., less than o250000a).
It downloads only to the first one in the serial PO range.
The download specifications for seps and sets are the same. If seps appear to be operating differently (e.g., 245, 260 are not coming across after cataloging), this is due to SERCAT practice, not the download. For seps, SERCAT works on the authority records only (not the bibliographic record). Consequently, only the fields linked to the headings file get upgraded in the cataloging process; staff performing post-cataloging processing must do the rest.
None.
Report problem to the Systems Office. Cite the GLADIS #.
The "upload" is the transfer of order information (and checkin numbers) from INNOPAC to GLADIS.
New orders and updates from a particular day are transferred the following day. They must then be run through three separate programs before appearing in GLADIS, so they will generally appear 2-3 working days after they are created or updated in INNOPAC. The transfer is done Monday-Friday.
Any update of the order record will trigger the order upload. Any update of the checkin record or card will trigger the checkin upload.
Just updating the bibliographic record will not trigger the upload. You must also edit order or checkin record. If a bib record has no order or checkin records attached, it will not upload.
The following categories are excluded from the order upload:
acqtype: b biblevel: x catprio: t locat: bulkx; shar; any invalid locat code ordtype: p status: 1,2
The following categories are excluded from the checkin upload:
upload: n, r, t acqtype: b locat: bart any invalid locat code
These 2 uploads operate independently.
e.g., acqtype=b in order record does not suppress
checkin record
The incoming INNOPAC record will attempt to match GLADIS on the following:
The result of the upload process will either be:
GLADIS # INNOPAC order# INNOPAC bib # INNOPAC checkin #
A new GLADIS record will be created in the following situations:
The level of the GLADIS record is determined by the bib level in the INNOPAC record:
INNOPAC bib level GLADIS level s s m m e e otherwise o
language country issn/isbn author 100, 110, 111, 130 title 245 edition 250 imprint 260 series 4xx, 830 note 500 alt author 700, 710, 711 alt title 740, 741 variant title 246, 247 cont 780 cont by 785
(Some of these fields will only be present in record if they came in from bib load.)
Attempts to link these fields to GLADIS headings file. If match, will update these access points in the uploaded GLADIS record.
e.g., If you keyed it into INNOPAC as 1xx, but it is in headings file as 4xx (i.e., if it is a cross-reference), will change the GLADIS 1xx to the authoritative form. Therefore the potential exists for the INNOPAC and GLADIS records to get out of sync.
130 field is created in GLADIS based on the 245 $a of the incoming INNOPAC record. Heading is linked to the authority file.
The GLADIS call number is determined by the Bib level of the INNOPAC record:
INNOPAC bib level GLADIS Call Number s Call # varies--Standing order m Membership order e Comprehensive order otherwise Ordered for ...
The GLADIS location will be the same as that in the INNOPAC order or checkin record.
Contains the following fields if present in INNOPAC record:
INNOPAC order# *b INNOPAC bib # *i identity *o order date *s status (open/closed)--serials only *t sent to *v exchange partner
INNOPAC checkin number
*b INNOPAC bib number
*i identity (from checkin record)
Contains all the fields from the INNOPAC order record and brief bibliographic display from INNOPAC bib record.
Not yet implemented; no projected date.
The INNOPAC bib information will replace the existing GLADIS bib record in the following situations:
INNOPAC Bib Level GLADIS levels it will replace s o, q m or e m, e, o none o
Creates "Ordered for" call number & puts PO field & order information here
(If bib level = s,m,e creates the appropriate call number and display constant as in F.2.a above)
Tries to determine under which call number it belongs. If holdings for the INNOPAC location appear under:
0 call #:
Creates "Ordered For" call # and puts PO field and order information here.1 call #:
(If bib level =s,m,e creates the appropriate call number and display constant)
Attaches PO and order information here.>1 call #:
Creates an "Error" call # and logs as error.
If INNOPAC checkin number is not already established in GLADIS, tries to determine under which call # it belongs:
If holdings for the INNOPAC location appear under:
0 Call #s:
Creates an "Ordered for" call number and puts the CI# field here (If bib level s, creates "Call # varies--Standing order" call number and corresponding display constant)1 call #:
Puts the CI# field under this call number.>1 call #:
Puts CI# field under an "Error" call number and logs as error.
4 types of error logs are produced:
Loaded, but gives warning message in error log. Does not match article table (may or may not need fixing)