Procedures Records Maintenance Appendices Serials Cataloging Miscellaneous Procedures Serials Home

Berkeley Processing Manual - Serials Processing Table of Contents

INNOPAC/GLADIS INTERFACES                                                                              Revised: July 1996

  1. SUM DOWNLOAD

    1. DEFINITION

      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).

    2. FREQUENCY

      Daily. Monday-Friday.

    3. WHAT TRIGGERS THE SUM DOWNLOAD

      Any update to any GLADIS SUM field triggers the download. Deleting a SUM will NOT trigger download.

    4. EXCLUSION CATEGORIES

      LOCAT=NEWS titles do NOT download (holdings are too long)

    5. MATCH POINT

      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.)

    6. SPECIAL SITUATIONS

      1. If GLADIS has multiple SUM fields for same LOCAT

        (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.

      2. If GLADIS has multiple locations

        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.

      3. If GLADIS has no SUM (i.e., was deleted in error)

        The INNOPAC LIB.HAS. is protected from the GLADIS download.

      4. If GLADIS SUM is too long to fit in INNOPAC

        The phrase "See GLADIS" displays in the INNOPAC LIB.HAS field.

    7. ERROR LOGS

      None.

  2. BIB DOWNLOAD

    1. DEFINITION

      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.

    2. FREQUENCY

      A particular day's updates or new records are downloaded the following morning, Monday-Friday.

    3. WHAT TRIGGERS DOWNLOAD

      The download is triggered by any of the following:

      1. editing any bibliographic field in GLADIS

      2. any headings file update on GLADIS affecting that bibliographic record

      3. utility download (from OCLC/RLIN to GLADIS)

    4. EXCLUSION CATEGORIES

      The following categories of GLADIS records are excluded from the download and MUST BE MAINTAINED in INNOPAC:

      1. any format other than SE

      2. level o

    5. FIELDS THAT DOWNLOAD

      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)

    6. PROTECTED FIELDS

      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
    7. MATCH POINTS

      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).

      1. If the GLADIS record does not contain an INNOPAC bib number, it does not download.

      2. If the GLADIS record contains more than 1 bib number:

        It downloads only to the first one in the serial PO range.

      3. Sets vs Seps:

        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.

    8. ERROR LOGS

      None.

    9. WHAT TO DO IF TITLE DOES NOT DOWNLOAD

      1. Be sure title does not fall into one of the exclusion categories (see D above).

      2. Check to see if title has one of the problems noted in G above. If so, correct and re-download. If not authorized to perform this type of maintenance, report problem to the Technical Services, Serials/Documents Division.

      3. Otherwise, allow an extra 2 days (in case Systems Office had a delay in doing that production run).

      4. If still does not download:

        Report problem to the Systems Office. Cite the GLADIS #.

  3. UPLOAD

    1. DEFINITION

      The "upload" is the transfer of order information (and checkin numbers) from INNOPAC to GLADIS.

    2. FREQUENCY

      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.

    3. WHAT TRIGGERS UPLOAD

      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.

    4. EXCLUSION CATEGORIES

      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

    5. MATCH POINTS

      The incoming INNOPAC record will attempt to match GLADIS on the following:

      GLADIS #
      INNOPAC order#
      INNOPAC bib #
      INNOPAC checkin #
      The result of the upload process will either be:

      1. Creation of new GLADIS record
           (see section F)

      2. Upgrade of existing GLADIS record
            (see section G)

      3. Putting record into error log
           (see section H)

    6. CREATING NEW GLADIS RECORD FROM INNOPAC RECORD

      A new GLADIS record will be created in the following situations:

        1. Incoming INNOPAC record does not match on any of the 4 match points listed in E above

        2. Incoming bib level=s record matches GLADIS but:

          1. GLADIS record has level other than s, o, q
          2. or matches multiple GLADIS records (same PO), none of which are level=s

      1. GLADIS BIBLIOGRAPHIC RECORD

        1. Level

          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

        2. Format

          1. If the order record is the first one trying to upload, the GLADIS format is assigned as follows:

            1. If INNOPAC pubtype = p, m, n:
              GLADIS format = SE

            2. If INNOPAC pubtype = p, m, n:

              1. 1. If medium = a, c, d, e, j, k, m, p, v assigns appropriate format based on medium

              2. Otherwise: format = BK

          2. If the checkin record is the first one trying to upload, the GLADIS format is assigned as follows:

            1. If the 1st 3 characters of the 1st check note = MVM:
              GLADIS format = BK
            2. Otherwise: format = SE

        3. The following fields if present in the INNOPAC bib record will upload:

          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.)

        4. 1xx,  830

          1. If INNOPAC record contains a 1xx or 830 field:

            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.

          2. If INNOPAC record is bib level = s, but record contains no 1xx field:

            130 field is created in GLADIS based on the 245 $a of the incoming INNOPAC record. Heading is linked to the authority file.

      2. GLADIS HOLDINGS SCREEN

        1. Call number

          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 ...

        2. Location

          The GLADIS location will be the same as that in the INNOPAC order or checkin record.

        3. PO field

          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
        4. CI# field

          INNOPAC checkin number
          *b  INNOPAC bib number
          *i   identity (from checkin record)

    7. ORDER DETAIL SCREEN

      Contains all the fields from the INNOPAC order record and brief bibliographic display from INNOPAC bib record.

    8. CHECKIN DETAIL SCREEN

      Not yet implemented; no projected date.

  4. UPDATING EXISTING GLADIS RECORD
    1. BIB REPLACE

      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
    2. ATTACHING ORDER INFORMATION

      1. If INNOPAC order # is already established in GLADIS record:

        • replaces existing PO field in GLADIS (except for the Bib #) with new INNOPAC data

        • replaces GLADIS order detail information with new INNOPAC order information

      2. If INNOPAC order # is not already established in GLADIS:

        1. If record has no RECD date:

          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)

        2. If record has RECD date:

          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.
           (If bib level =s,m,e creates the appropriate call number and display constant)
          1 call #:
          Attaches PO and order information here.
          >1 call #:
          Creates an "Error" call # and logs as error.
    3. ATTACHING CHECKIN INFORMATION

      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.
  5. ERROR LOGS

    4 types of error logs are produced:

    1. Loader error logs

      1. Loaded as "error call number" (see G above)

      2. Rejected from load:

        1. Error 80:
          same INNOPAC bib # in 2 different GLADIS records

        2. Error 81:
          INNOPAC record has GLADIS # that points to 1 record, but its Bib # points to different GLADIS record

        3. Error 82:
          GLADIS # is valid, but no longer exists

    2. Interface error logs

      1. Rejected

        1. invalid GLADIS #:
          (lacks check digit, typo, stray punctuation marks)

        2. identity field has invalid characters (*)

      2. Loaded, but gives warning message in error log

        1. invalid ISSN
        2. multiple occurrence of same tag
          (ISSN/1xx/245/260)

    3. Preprocessor logs

      1. Rejected

        1. multiple occurrence of tag
          e.g. 100/110 conflict

        2. author with no tag or invalid tag

    4. Filing problems (separate log generated by interface program)

      Loaded, but gives warning message in error log. Does not match article table (may or may not need fixing)

  6. What to do if title does not load

    1. Wait at least 3 days.
    2. Try again.
    3. If still problem: Serials Cataloging Division or Systems Office.

 

Copyright © 1996-2003 The Regents of the University of California. All Rights Reserved.
Last updated Thursday, 04-Aug-2005 12:21:39 PDT Contact