[514] in ad-lib
FINAL - Expansion Table Spec
daemon@ATHENA.MIT.EDU (Eric Celeste)
Wed May 3 10:41:34 1995
To: ad-cat@MIT.EDU
Cc: gyoung@MIT.EDU
Date: Wed, 03 May 1995 10:40:45 EDT
From: Eric Celeste <efc@MIT.EDU>
I'm sending this to ad-cat for the record. Grant needed a copy to e-mail
to MR. There have been no changes to this spec since the last time you saw
it in your e-mail.
By the way, we still have to develop our codes. Even though we may not
have the Expansion Table software for a few weeks, we still have to start
using the new coding on May 15. Maybe Stephen and I can get together to
draft a set of codes this week?
...Eric
EXPANSION TABLE SPECIFICATION
MIT Libraries / Final Revision / 26 April 1995
MIT requires an Expansion Table to create codes that will be used by a
loader subroutine to fill in fields in the ITEM record from the OCLC 949
tag. This Expansion Table will be maintained by MIT though a keyword which
may be invoked in the cataloging module.
The Expansion Table will be used to create 852 subfields a, b, c, h, i, j,
k, x, and z. All other subfields (g, p, t, and v) will appear directly in
the 949. The value of any subfield appearing directly in the 949 will
override the default value found in the Expansion Table.
The call number for 852h will be located in the bibliographic record
according to the precedence value as found in the table. For example, if
the precedence value is "099,090,050" then 099 would be used as the 852h,
if no 099 is present then 090 would be used, if no 090 is present then 050
would be used. If the call number found is "x", then the value "No call #"
will be used instead. If no call number is found and no 949h is present,
then the loader subroutine will report the error and load the
bibliographic record with its 949 tag into the workfile.
The value in the 949a will be used to match the Expansion Table codes.
(Note that since 949a will be used to match the code, the 852a value found
in the Expansion Table will never be overridden.) Matching will be case
insensitive. Expansion Table codes can be up to tweny characters long and
include any characters, embeded spaces, or punctuation except the "*".
In addition to being used by the loader subroutine and Expansion Table to
create 852 tags, any 949 tags on an incomming record will be left on the
record in the bibliographic database. If the loader subroutine determines
that a 949a does not match any code in the Expansion Table, then it will
report the error and load the bibliographic record, with its 949 tag, into
the workfile.
The following two example layouts represent MIT's vision of how the
Expansion Table and Expansion Code screens should appear and function.
MIT EXPANSION TABLE
Number of codes : 110
Code Description
--------------------- -----------------------------------------
1. h Humanities Book
2. hj Humanities Journal
3. h-ref Humanities Reference
4. h-fiche Humanities Microfiche
5. b Barker Book
6. bj Barker Journal
7. b-ref Barker Reference
8. b-fiche Barker Microfiche
Options: Enter specified line number
? help Add item # line Print Forward Backward
Search jump Exit
MIT EXPANSION CODE
Defaults for expansion code : a-film
------------------------------------------------------------------
1. Description : Aero Microfilm
2. Institution : MIT
3. Sublocation : AERO
4. Collection : MICRO
5. Prefix :
6. Suffix : Non-Circulating
7. Circulation Code : NOCIRC
8. Call Number Precedence : 099,090,050
9. Classification :
10. Cutter :
11. Accession number :
Options: Enter specified line number
# line Line by line Copy Print Delete File Exit
