BISON DATABASE REPORTS
Date of latest revision Oct. 15, 2002
This region provides lists of reports needed for monitoring the quality
of the BISON database and for the possible conversion from NOTIS to a
replacement library system at a future date. Included are descriptions of
each report and the intended purpose of the report. As reports are produced the
number and name of the report are provided. Also provided is the date the
report was produced and the schedule, if established, for running the
report in the future. There are a mixture of reports which were are needed
only once and others which are needed on a continuing basis.
A. Reports needed currently in order to maintain the
quality of records.
1. A report which will update the list of status x records with a bib
fixed field R/DT date of Jan. 12, 1997 or later.
PURPOSE: Status x records are ones which are marked for physical
deletion. These records need to be reviewed prior to their being
physically deleted.
EXAMPLE: ECE8189
EXISTING REPORTS: CTSTAB33 BIB FILE COPY RECORDS, Count of Catlg Status
Equal x was run on 1/11/97.
NEW REPORTS: CTSTAB34, run on 5/13/97 covered the period
1/12/97-5/11/97. CTSTAB76, Count of status equal x and 245 does not
begin TO BE DELETED, was run on 7/9/97 after a physical deletion of
selected records was done and on subsequent dates.
ACTION TAKEN WITH REPORT: Reports are used to confirm records for
deletion and to remove all fields except the 245 from the record. The
245 is being changed to read "TO BE DELETED" followed by the record
number. If an MHLD has been marked for deletion,
"MHLD" is being inserted before the record number. If there is a
completed or cancelled order associated with the record "DEAD ORDER" is
being inserted before the record number. In those instances where
there is both a deleted MHLD and and a completed or cancelled order,
only "DEAD ORDER" is being used.
1a. Reports by processing unit which list those records which have been
identified for deletion but the status has not been changed to "x."
These records can be identified by text in the record level NOTES
field of a copy holdings record beginning "dup" "to" or "do"
PURPOSE: Records have been determined to be duplicates or are not
needed for other reasons and should be deleted. However, since the
status was not changed to "x" the records will never be deleted. These
records need to be reviewed and the status change to "x" if
appropriate.
EXAMPLE: EDW8452
NEW REPORT: UB813, Records without status x but with notes beginning
to, do, or dup, was first produced on 8/20/97.
1b. Reports by processing unit which list those records, excluding those
with a status of "x," which have a record level NOTES field of a copy
holdings record beginning with text other than "dup" "to" "do" or
"bib"
PURPOSE: To review the content of these notes fields and eliminate
those which are no longer needed.
EXAMPLES: EBX3606 CHC8422
NEW REPORT: UB820, Records with notes not beginning with to, do,
dup, or bib, to, do, or dup, was produced first on 8/21/97.
2. Records with a status of "a" and status of either "0A" or "2A" in all
copy statements listed by processing unit then by record number.
PURPOSE: Records have been added, but the work on the records was never
completed. These records need to be identified, and the necessary work
either completed or the records marked for deletion.
EXAMPLES: ECJ4010 (0A) EBF3390 (2A)
NEW REPORTS: UB052 Records with a status of 0A or 2A copy status and
UB053 Records with status "a" and no copy statements were first
produced as follows: UB052 on 5/28/97 and UB053 on 6/4/97.
2a. By processing unit lists of record numbers which have a status of "a"
and one or more copy statements with a status other than "OA" or "2A"
PURPOSE: Records created through the derive process have a default
status of "a" and when the records are added for a purpose other than
needing a record against which to place an order there is no automatic
status change or system prompt to change the status. Because of this,
records which are fully cataloged can appear to be in the pre-order
process or as in the process of being cataloged.
EXISTING REPORTS: UB052 lists records with a status of "a" and with
copy statements having a status of either "0A" or "2A"
NEW REPORT: UB059,Records with a status and not a 0A or 2A copy status
3. Records with lack a subfield b in any activated copy statement which
has a call number or call number substitute.
PURPOSE: The subfield b is the initial subfield of the call number
portion of a NOTIS copy statement. NOTIS permits one subfield b but
multiple subfield c. The NOTIS software fails to detect the absence
of a subfield b although the absence results in the call number failing
to display in the public mode. While this particular formatting of
call numbers may be unique to NOTIS, there is still the need to correct
records which lack a subfield be in a copy statement in order to have
all call number formatted in a uniform manner at the time of the
conversion.
EXAMPLE: EAV9895
EXISTING REPORTS: UBO46-Active copies with no b subfield in call
number, run on 5/19/97.
NEW REPORT: UB046, Active copies with no b subfield in call number, was
first produced on 5/19/97.
ACTION TAKEN WITH REPORT: A review of GL and PL records will begin the
week of June 23. Appropriate changes will be made to call numbers. The
reports for HL, LL, and ML are too inclusive and need to be replaced
as part of 3a.
3a. In order to eliminate on order and in-process copies as well as copies
which have been blocked from public view, copy statements with a class
type of "A," "I," "U," or "Z" should be excluded.
4. Unlinked item records which have been discharged. Include record number
and call number from unlinked item record in report.
PURPOSE: When an unlinked item record is created without the catalog
review flag marked or the flag is marked and the discharged item is
still not routed for relinking, the unlinked item record remains
active. The items need to be relinked to copy holdings statements.
EXAMPLE: AZ39240-001-0001
EXISTING REPORTS: A report was produced in May 1995 and was called
"Unlinked item records, discharge is last transaction." Also called
"UNLINK2."
NEW REPORT: UB060, Active unlinked item records with discharge as last
transaction, was first produced 6/10/97.
NOTE ON ACTION TAKEN ON REPORT: Records which appear to have been
created for training purposes (AZ01006-001-0001 is an example) cannot
be relinked.
5. Unlinked item records which have never been charged. Include record
number and call number from unlinked item record in report.
PURPOSE: When an unlinked item record is created in error and is
never charged, it remains active. These unlinked item records for
which there has never been a circulation transaction need to be
reviewed and, in most cases, marked for deletion. These records need
to be eliminated so that the list or file of active unlinked item
records which will be needed at the time of the conversion will not
include these records.
EXAMPLE: AZ47014-001-0001
EXISTING REPORTS: A report was produced in May 1995 and was called
"Unlinked item records, never charged" Also called "UNLINK1"
NEW REPORT: UB061, Unlinked item records, never charged, was produced
first on 6/10/97.
NOTE ON ACTION TAKEN WITH REPORT: Those records which lack barcode are
being deleted (status = d).
6. Active copy statements in ML records with a record number of EBK0150 or
higher which have a status of "2," or the same report but not
restricted to a record number range.
PURPOSE: Much effort has been put into reviewing active copy statements
with a status of "2" (1) to determine if title is received currently
and should, therefore, have a status of "2"; (2) to provide values for
the fixed fields in the MHLD if that has not already been done; (3) to
complete the holdings information in the MHLD and/or express holdings
according to the ANSI standard if either has not already been done; and
(4) to serve as another means of identifying duplicate records. Using
an earlier series of reports this activity has already been completed
for all other processing units, and there is no reason why records
added after the the earlier reports were produced need to be reviewed
for any processing unit other than ML. Having holdings data in a consistent
format is now the primary objective with this activity.
EXISTING REPORTS: UL114 "Records with copy status=2" was produced in
April 1993.
NEW REPORT: UB411, ML records with active copy statements with 2
status, was produced on 6/22/97. This report will not be needed again.
7. Lists by processing unit of record numbers which have a status of c
(not to be cataloged) or e (manually cataloged). There may not be
any records with the latter status (compare with no.6 in pt.C below).
PURPOSE: Any records with these NOTIS-defined status codes need to be
revised and given on of the more commonly used status codes.
EXAMPLES: ECR9179 AAA9426 EBB4731
EXISTING REPORTS: CTSTAB33 lists the records with a status of "x" It
does not provide the data by processing unit, however.
NEW REPORT: UB333, All records with a c or e status by proc. unit, was
first produced on 6/12/97.
NOTE ON ACTION TAKEN WITH REPORT: After examining the report it was
decided that records with a status of "c" will not be changed to a
different status.
8. A list by processing unit which provides each unique text in the
subfield k of any copy statement and the number of copy statements
in which that particular text occurs. All copy statements should be
examined.
PURPOSE: The subfield k in copy statement is used to provide
sub-location information when there is no location for the
sub-location. Since the subfield k is free text, there can be
inconsistencies. These need to be identified and corrected.
EXAMPLES: EBP2874 CHC0723 EBD3990
EXISTING REPORTS: A report "Count of all subfield k values" (CTSTAB28)
was produced 10/19/94. This report did not provide the data by
processing unit, however. Another report produced 9/21/94 "CPY FILE
RECORDS counts of SUBK values by processing unit." There is no number
which appears on the report.
NEW REPORT: UB505, Counts of subfield k values by processing unit was
first produced on 6/17/97.
8a. Two supplementary reports to UB505 are needed. By processing unit
there needs to be the capability of requesting the record numbers
associated with incorrect subfield k values.
NEW REPORTS: UB505g, p, u, h, m, and l were produced on 7/19/97 and
on 8/25/97.
SCHEDULE: These reports will be requested as needed.
The second supplementary report should be restricted to LL records
which have a DT fixed field date of 02/01/96 or later and with
subfield k text beginning with the letters "Video." A list of all
record numbers is needed.
EXAMPLE for secondary report: ECW0929
NEW REPORT: UB505a, LL records with subfield k starting Video and
DT=02/01/96 or greater, was produced on 7/9/97.
8b. A supplementary report which lists all records with a record number
of EAR9999 or lower which have a copy statement containing a subfield
k of "CAN" is needed.
PURPOSE: When records for Canadian documents entered BISON as part of
the initial load the copies were created with a linked item record
count of 1, but item records were not created. Since that time some of
the records have had item records created. We need to review all records
with a subfield k of "CAN" and elminiate the item record count if
there are still no linked item records assxociated with the copies.
EXAMPLE: CIF0023
NEW REPORT: UB505CAN, Records with subf k=CAN and bison number
< EAR9999m was run on 8/19/97.
NOTE ON ACTION TAKEN WITH REPORT: All ghost item record counts have
been eliminated.
9. A list of record numbers for records which have as the second or higher
copy statement a copy which fits these criteria: no item record count
associated with the second or higher copy and a copy creation date
the same as the one in the copy statement which immediately precedes
the copy which lacks an item record count. For example, if the second
copy statement lacks an item record count, the copy creation date
should be identical to the date associated with the first copy. The
second or higher copy statement should have a status other than Z.
PURPOSE: A frequent problem with the GTO has been passing records
multiple times. When the record entered the system a second time after
the initial copy statement has been completed, there may have never
been a reason for a staff member to return the record. Therefore,
these "blind" copy statements have remained in the system. The
statements do display to the public. Identifying and removing these
copy statement is highly desirable.
EXAMPLE: EBN4459
NEW REPORT: UB621, Copy statements with the same date as previous copy
and no item record, was produced on 6/23/97.
9a. Same as 9 above except that copy statements with a status of 2 or 3
should be excluded.
10. A report is needed to identify those ML records which have a status of
"h," a class type of "L," or "T," and are lacking from an 035 field
data which begins "(CStRLIN)" or "(OCoLC)."
PURPOSE: An undetermined number of fully cataloged ML records lack
bibliographic utility record numbers. The absence of such a number
prevents eventual machine overlay.
EXAMPLE: ECS8274 (type of record to capture) EBA7927 (type of record
not to capture).
NEW REPORT: UB804; Run 8/7/97.
11. There is an undetermined number of HL records which have lack MeSH
(Medical Subject Headings). Those records need to be indentified so
that the headings can be added. The report should provide the BISON
record numbers for all HL records which have a status of "h," a class
type of "B" or "L," and lack any 650 fields with a second indicator of
"2."
PURPOSE: All HL records should have subject analysis.
EXAMPLE: ACB6026 (type of record to capture) CAE1038 (type of record
to exclude)
NEW REPORT: UB825, HL records without subject analysis, was run on
8/25/97.
12. A report of ML records which have a GMD fixed field with a value of
"s," a DIM fixed field value of "g" and one or more 028 fields with a
first indicator of "0" and second indicator of "2." Arrangement of
report should be by 028 subfield b with entries also containing 028
subfield a, subfields b and c from the copy holdings statement, and
BISON record number.
EXAMPLES: EBF0171 EBE9413 EBY2293 ECS3882
NEW REPORTS: UB923 for indicators 02; UB924 with any indicators
13. A report which provides the record numbers of item records to which
selected location codes have been entered as temporary location codes.
Reports by processing unit of (1) item record numbers which contain a
temporary location code other than APC1; APC2; APC3; APG; APR1; APR2,
APR3; BIND; CB; CMC1; CMC2; CMC3; CMG; CMR1; CMR2; CMR3; GL,BIND;
HL,BIND; HSCB; HSC1; HSC2; HSC3; HSG; HSRR; HSR1; HSR2; HSR3; LA,P;
LACB; LAC1; LAC2; LAC3; LAC4; LAC5; LAC6; LAC7; LAC8; LAG; LAR1; LAR2; LAR3;
LAR4; LAR5; LAR6; LAR7; LAR8; LL,BIND; LOAR, LOBR; LOG; LORR; LOR1;
LOR2; LOR3; ML,BIND; MUA; MUCB; MUR1; MUR2; RPCB; SEA; SEAR; SEC1; SEG;
SERR, SER1; SER2; SER3; UGA; UGR; UGG; UGRR; UGR1; UGR2; UGR3 and (2) item
record numbers which contain only one of the following codes as a
temporary location code: APG; CB; CMG; HSCB; HSG; LACB; LAG; LOG;
MUCB; MUG; RPCB; SEG; UGG.
PURPOSE: NOTIS allows for a location code to be used in a copy
holdings statement as an official location and in an item record as a
temporary location. There are instances of codes remaining in the item
record when they should have been removed. There are other instances
when a code has been used as temporary location when it should have
been used as the official. It is also advisable to review records
which contain those codes which are used as temporary location codes
on a regular basis.
EXAMPLE: EAP7297-001-0001
EXISTING REPORTS: SYS5.SOURCE60.SAS UB002A, Records in a given
location (report includes call number and BISON number) and UB042B,
Records in a given location (report includes call number, BISON number
and title information) identify records in which the location code has
been used as the official location in a copy holdings statement in a
copy holdings record.
NEW REPORTS: UB1016, Items with selected temporary location codes, and
UB1015, Items with location codes other than selected list, were
produced first 10/97.
14. Reports by processing unit listing the record numbers which contain
copy holdings statements with a class code of (1) C, D, E, F, O, or R
and (2) X.
PURPOSE OF REPORT: NOTIS-defined class codes of C, D, E, F, O, or R
should not have been used locally. If any copy holdings statements
contain one of these class codes, the codes need to be changed.
Some records were added to the database in 1990 with a class code of
X. Since these copy holdings statements may also lack call numbers,
they need to be identified and corrected.
EXAMPLE: EAN7077
15. Lists of record numbers by processing unit which contain one or more
active copy statements with a status of 2 or 3 for which there is no
linked MHLD. Include only records with a status of "h" and copy
statements with a status of "2" or "3," and with class types other
than "X" or "Z"
PURPOSE OF REPORT: Records for multi-part works should have an MHLD
linked to each active copy statement. Some active copies lack an MHLD,
and, therefore, there is no record of holdings. This report will
enable us to correct that problem.
EXAMPLE: EDS0446
NEW REPORT: ASS01
16. Lists of records by processing unit of linked item records which lack
barcodes. Records are needed for GL, HL, LL, and ML. A report should
not be produced for PL.
PURPOSE OF REPORT: The NOTIS software permits the creation of linked
item records which do not contain barcodes. Although linked item
records which do not contain barcodes can be appropriate in some
situations, most such item records were created in error and need to
be deleted.
EXAMPLE: EBV4229-001-0001
NEW REPORT: UB1016B
17. Separate files of purchase order numbers with an order status of "X"
by year and by processing unit.
PURPOSE OF REPORT: These files will enable us to capture data on
orders placed and cancelled in NOTIS. After the data is captured,
the bibliographic records to which the cancelled orders are attached
will be reviewed for possible deletion.
NEW REPORT: UA903, created 9/7/97
18. Separate files of purchase order numbers for non-serial records with
an order status of "Z" by periods of six months beginning 1/1/95 and
by processing unit.
PURPOSE OF REPORT: These files will enable us to capture data on paid
non-serial orders, thus, eliminating the need to carry this
information into the new system.
SCHEDULE: Files are needed now. An updating file will be requested
when the current database is closed.
NEW REPORT: UA910, created 9/10/97
19. Reports by processing unit of item records which are charged
to a Missing on GEAC patron record. Missing patrons are:
29072004105181 29072004105157 29072004091126
29072004105173 29072004105140
29072004091142 29072004105132
29072004091167 29072004091118
29072004091126 29072004105207
29072004091134 29072004105199
29072004105165 29072004183295
PURPOSE OF REPORT: Some items which were missing at the time NOTIS was
implemented were charged to a Missing patron via an unlinked item
record. These Missing patrons were established as SE Missing on Geac,
LO Missing on Geac, etc. Multiple patron records were established for
AP, LA, LO, SE, and UG.
These items need to be relinked to copy holdings statements so
that the missing status is available in the OPAC.
SCHEDULE: A partial report is needed now. Produce for these patron
records only: 29072004105140
29072004091167
29072004105181
NEW REPORT: UB1016 was produced 3/98 for the above test patrons.
20. An item record status of "O" (orphaned) is not to be used locally.
PURPOSE OF REPORT: Any item records, linked or unlinked, need to be
identified so that appropriate action can be taken.
EXAMPLE: There are no known examples of this.
SPECIAL NOTE: This was handled as part of the conversion program for
implementing NOTIS LMS 6.4.1. A separate report will not be needed.
21. Selective unlinked items records have been coded as "w" (withdrawn) if
the item is not to be relinked and the barcode is to be removed from the
item.
PURPOSE OF REPORT: The extent that this has been done needs to be
established and alternatives for dealing with these records
considered.
EXAMPLE: AZ43328-001-0001
NEW REPORT: UB1219 was produced on 1/22/00.
22. Three listings (1 for GL, 1 for HL, and 1 for PL) of records
which have one or more copy statements which meet all of the following
criteria:
(1) copy status of 2 or 3; (2) a class code other than Z; and the
absence of either "hldg" "vhld" "mhld" or "dhld" in the NOTES area
of the copy statement. The above data can appear in any location of
the NOTES area.
PURPOSE: In order to have the maximum number of MHLDS which have
holdings expressed according to the ANSI standard and are therefore
consistent, we need to identify those records for muti-part works for
which this activity has not taken place.
EXAMPLE: ECM5328
NEW REPORTS: UB524G, H, and P were produced 5/24/98.
23. A list of record numbers containing a copy statement with a call
number substitute of "|b shelved;by;master;microfilm" (use of
semicolons and upper and lower case can vary).
PURPOSE: The NOTIS software allows the use of a call number substitute
in a copy holdings statement. The appropriate class code for a call
number substitute is "U." The text is not searchable through the call
number index. Inasmuch as data used as a call number substitute cannot be
retrieved through a call number search, a report is needed. This will
be the first in a series of requests for reports on different text
used as a call number substitute.
EXAMPLE: ECC5546
SCHEDULE: Report is needed now.
NEW REPORT: UB817 was produced 8/18/98.
24. Lists of headings in provisional subject authority records when the
heading is subordinate to a full (non-provisional) subject authority
record. A subject authority record is identified by the presence of a
150 field. A provisional heading is identified by an "o" in the E/L
fixed field. A full authority record can be identified by an E/L
value of "n"
PURPOSE: Many provisional authority records were created by BNA for
subordinate headings which are not needed. These need to be identified
and marked for deletion.
EXAMPLE: BEV7478 (a provisional subject authority record) is
subordinate to BEB8212 (a full subject authority record).
EXISTING REPORT: UBAUTH84, GL Authority Records with a 150 beginning
with E and E/L = o (report was restricted to the letter e)
NEW REPORT: UB1123 was produced 11/24/97; follow-up in 12/97 with
split files by letter with processing unit added to data extracted. There
was a second follow-up to eliminate problem caused by diacritics.
24a. Lists of headings in provisional subject authority records when the
heading is subordinate to another provisional subject authority
record or is not subordinate to another record.
NEW REPORT: UB1124 was produced 6/22/98.
25. Lists of headings in provisional authority records for titles when the
authority record lacks a 642 field. An authority record for a title
is identified by the presence of a 130 field. A provisional heading
is identified by an "o" in the E/L fixed field. Include the processing
unit for each authority record identified.
PURPOSE: Many provisional authority records were created by BNA for
titles and are not needed. These need to be identified and marked for
deletion.
EXAMPLES: BCA0860 and BCD9833 are examples are records which should be
identified. Because it contains a 642 field, BDV2991 is an example of
a record which should not be identified.
EXISTING REPORT: UBAUTH04, Authority records with 130 field, will
identify all GL provisional authority records with a 130 field. It
does not eliminate those which contain a 642 field.
NEW REPORT: UBAUTH24 was produced 2/24/99.
26. List of all full topical subject authority records associated with ML
processing unit. A topical subject authority record is identified by
the presence of a 150 field. A full authority record is identified by
an E/L value of "n"
PURPOSE: The status of many provisional authority records have been
changed to full by ML. Other than coding, the records are still
provisional and, in most cases, are not needed. The records need to
be reviewed and most deleted.
EXAMPLE: BAE0918
26a. Same report for records with a 150 field.
26b. Same report for records with a 100 field.
26c. Same report for records with a 110 field.
27. Lists of headings in provisional geographic subject authority records
when the heading is subordinate to a full (non-provisionl) subject
authority record. A geographic subject authority record is identified by
the presence of a 151 field. A provisional heading is identified by an
"o" in the E/L fixed field. A full authority record can be identified by
an E/L value of "n"
PURPOSE: Many provisional authority records were created by BNA for
subordinate headings which are not needed. These need to be identified
and marked for deletion.
EXAMPLE: BEF1337 (a provisional geographic subject authority record)
is subordinate to BAQ9621 (a full geographic subject authority
record).
EXISTING REPORT: A report restricted to records tagged 150
was produced 11/24/97; follow-up in 12/97 with split files by
letter with processing unit added to data extracted. There was a
second follow-up to eliminate problem caused by diacritics.
NEW REPORT: UB1127 was produced 4/5/98.
27a. Lists of headings in provisional geographic subject authority records
when the heading is subordinate to another provisional geographic
subject authority record or is not subordinate to another record.
NEW REPORT: UB1127a was produced 7/98.
28. Lists of headings in provisional authority records which are coded as
"c" in the SUBJ fixed field, are tagged other than 650 or 651, and are
subordinate to a full (non-provisionl) subject authority
record. A provisional heading is identified by an "o" in the E/L
fixed field. A full authority record can be identified by an E/L
value of "n." Multiple reports based on tagging would also be
acceptable.
PURPOSE: Many provisional authority records were created by BNA for
subordinate headings which are not needed. These need to be identified
and marked for deletion.
EXAMPLE: BFN0964 (a provisional authority record) is subordinate to
BAT8938 (a full authority record).
EXISTING REPORT: Reports which are restricted to records with a 150
tag have already been produced. Produced 11/97; follow-up in 12/97
with split files by letter with processing unit added to data
extracted. There was a second follow-up (UB1128) to eliminate problem
caused by diacritics.
29. Reports by processing unit of serial records which lack an OCLC record
number in the 035 field. A serial record is identified by a value of
'S' in the FMT fixed field. An OCLC record number begins with
(OCoLC)
PURPOSE: In order to facilitate machine loading of local
holdings data into OCLC all serial records need to contain an OCLC
record number. This report will identify those serial records which do
not contain an OCLC record number.
EXAMPLE: EAR5208. Note that records can contain multiple 035 fields
that the OCLC number can be in a second or higher 035 field. An
example is ABC8726.
30. Report of record numbers for MHLDs for non-print formats which lack
007 fixed field data when the location code for the copy is one of
the following: apm; apm,p; arm; hsa; laam; lodm; lodm,p; lom, lom,p;
mam; mam,p; mum; rpm; sedm; sedm,p; sem; sem,p; ugm; ugm,p
PURPOSE: When the format of holdings is other than non-print an 007
field is needed in the fixed field area of the MHLD. There are
specific 007 strings for individual non-print formats. An immediate
puropose for this data is to facilitate the machine loading of local
serials holdings data into OCLC.
EXAMPLE: ECJ6877-001
NEW REPORTS: LISTLOD for lod and lod,p; LISTLODM for lodm and lodm,p;
LISTSED for sed and sed,p; LISTSEDM for sedm and sedm,p. All were
produced 8/00.
31. Reports by processing unit of record numbers for records which have
the text "msg" with or without a period or "missing" in any position
in a copy statement note.
PURPOSE: The above values have been used to indicate that an unlinked
copy is missing. These records need to be reviewed and, if the copy
is still missing, action taken to suppress the record from public view.
EXISTING REPORTS: SYS5.SOURCE60.SAS (UBOO1T) produces this report.
32. Reports by processing unit of record numbers for bibliographic records
which contain one or more 856 fields.
PURPOSE: The MARC 856 field contains the URL for Internet resources.
Since the current NOTIS MARC tag table does not support the full range
subfields associated with the 856, we have to montior the fields in
order to ensure proper catalog display.
EXAMPLE: CHC0367
NEW REPORT: UB814 was produced 8/14/98.
33. Reports by processing unit of record numbers for bibliographic records
which contain one or more 538 fields.
PURPOSE: The MARC 538 field contains access information for Internet
resources or file characteristics for CD-ROMs. Use has been made of
the field to provide access information required before a web catalog
was available. With the introduction of a web catalog the data in the
538 must be reviewed and corrected as necessary.
EXAMPLE: CHC0367
34. Reports of GL records which fit the following criteria.
a. Record has an OCLC number in an 035 field (field begins (OCoLC),
is suppressed (D/S fixed field value of "s"), in any format
other than serials (BL fixed field value other than "s"), status other
than "x," and all activated copy statements have a class code of "Z."
EXAMPLE: AAY4716
b. Record has an OCLC number in an 035 field (field begins (OCoLC),
is suppressed (D/S fixed field value of "s"), in serials
format (BL fixed field value of "s"), status other than "x," and
all activated copy statements have a class code of "Z."
EXAMPLE: ABC2995
c. Record has an OCLC number in an 035 field (field begins (OCoLC),
is not suppressed (D/S fixed field value of "d"), in any
format other than serials (BL fixed field value other than "s"),
status other than "x," and all activated copy statements have copy
statements have a class code of "Z."
EXAMPLE: CIE8732
d. Record has an OCLC number in an 035 field (field begins (OCoLC),
is not suppressed (D/S fixed field value of "d"), in serials
format (BL fixed field value of "s"), status other than "x," and
all activated copy statements have a class code of "Z."
EXAMPLE: CHG3355
PURPOSE: Records for titles which have been withdrawn should also be
deleted from OCLC. These reports will also identify those records
which should also have been suppressed.
NEW REPORTS: 34a UB0913; 34b UB0914; 34c UB0915; 34d UB0916
35. Reports, by processing unit, of authority records which meet the
following criteria: 1) record is not marked for deletion (the second
character in the STAT fixed field is not an uppercase D); 2) record
contains a 665 field.
EXAMPLE: BDP0067
PURPOSE: The Library of Congress ceased using the 665 field in 1981.
This field diplays as an explanatory note in the original command
version of the catalog. Requesting the line number for the display in
web version of the catalog results in an error. Inasmuch as the field
is no longer used by LC, we will eliminate all local instances of the
field rather than make the necessary adjustment for the field to
display in the web version of the catalog.
NEW REPORT: UB1220 was produced 12/20/98.
36. Reports, by processing units, of record numbers for bibliographic
records containing one or more 852 fields. The 852 fields contain
holdings data and were present in some OCLC records for serials created
prior to the loading of the BISON database in 1990.
EXAMPLE: CHJ9736
PURPOSE: Data contained in 852 can be out dated. All uses of the 852
field need to be eliminated from the database so that the field is
available for other uses in a future system.
NEW REPORT: UB0105 was produced 1/5/99; UB852 produced on 10/19/00
provides the same data.
37. Reports, by processing unit, of record numbers for bibliographic
records with a fixed field encoding level (E/L field) value of "8."
EXAMPLE: EAN7077
PURPOSE: The E/L value of "8" indicates that the bibliographic record
is a CIP record. Each record with this status needs to be reviewed and
upgraded to full status.
NEW REPORT: UB0218 was produced 2/18/99.
37a. Reports, by processing unit, of record numbers for bibliographic
records with a fixed field encoding level (E/L field) value of "8" when
there is also one or more copy statements with a class code of "L."
PURPOSE: The E/L value of "8" indicates that the bibliographic record
is a CIP record. Each record with this status needs to be reviewed and
upgraded to full status. Restricting the universe to records for which
there are one or more copy statements with a class code of "L" eliminates
records with a status of either on order or in-process.
EXAMPLE: AAY3038
NEW REPORT: UB0310 was produced 3/10/99.
37b. Reports, by processing unit, of record numbers for bibliographic
records with a fixed field encoding level (E/L field) value of "8"
when there is also one or more copy statements with a class code of
"T."
PURPOSE: The E/L value of "8" indicates that the bibliographic record
is a CIP record. Each record with this status needs to be reviewed
and upgraded to full status. Restricting the universe to records for
which there are one or more copy statements with a class code of "T"
eliminates records with a status of either on order or in-process.
EXAMPLE: EDE3190
NEW REPORT:
37c. Reports, by processing unit, of record numbers for bibliographic
records with a fixed field encoding level (E/L field) value of "8"
when there is also one or more copy statements with a class code of
"B."
PURPOSE: The E/L value of "8" indicates that the bibliographic record
is a CIP record. Each record with this status needs to be reviewed
and upgraded to full status. Restricting the universe to records for
which there are one or more copy statements with a class code of "B"
eliminates records with a status of either on order or in-process.
EXAMPLE: ACA1291
NEW REPORT: UB0310A was produced on 11/16/00.
38. Reports, by processing unit, of record numbers for bibliographic
records which contain one or more 650 fields with a second indicator
of 3, 5, 6, or 8. Record numbers for each indicator can be provided in
a single report or in separate reports by indicator.
PURPOSE: The indicators are either invalid or are ones which should
not be used locally.
EXAMPLE: ECF8631
NEW REPORT: UB0228 was produced 3/3/99.
39. Reports, by processing unit, of record numbers for bibliographic
records which contain one or more 690 or 691 fields.
PURPOSE: Subject headings coded 690 or 691 are considerd provisional
and should not be in completed records.
EXAMPLE: ECF8631
NEW REPORT: UB0303 was produced 3/3/99.
40. A single report listing item records for all processing units which
contain barcodes with a library identifier other than the one assigned
to the State University of New York at Buffalo. The assigned
identifier is 39072. The report should list record numbers for item
records containing barcodes which do not begin with 39072.
PURPOSE: To identify and correct barcode numbers which, although
incorrect, passed the validation check. These incorrect barcode
numbers do not agree with the numbers on the physical barcodes.
EXAMPLE: CBZ2416
NEW REPORT: UB0304 was produced 3/3/99.
41. A single report listing records with an 856 field containing a hyphen.
PURPOSE: A hyphen is sometimes used to break a long string of
characters into more than one line. Breaks can cause URLs to fail.
856 fields containing hyphens need to be identified and the hex code
of %2D substituted for the hyphen.
EXAMPLE: EDM2356
NEW REPORT: UB815 was produced 3/14/99.
42. A count of the number of copies associated with a specified location
code.
NEW REPORT: UB045 was produced 4/99
43. Reports, by processing unit, of records for serials containing 247
fields. The BL fixed field value is "s" and the record contains
one or more 247 fields.
PURPOSE: Records containing 247 fields reflect latest entry serials
cataloging. Those records need to be replaced with ones which reflect
successive entry cataloging.
EXAMPLE: EAH4838
NEW REPORT: UB0508
44. Reports, by processing unit, of records for serials containing "MUL"
in the 040 field and lacking any 6xx fields. The BL fixed field value
is "s," "MUL" appears immediately after the subfield a of the 040
field and the record lacks any 6xx field.
PURPOSE: Many serial records entered by MUL lack subject analysis.
EXAMPLE: CHC2031
45. Report of records in the ML processing unit with a value of "m" in FMT
fixed field, a value of "c" in RT fixed field, and one or more 490
fields.
PURPOSE: Information in the 490 fields may need to be placed in an 028
field.
EXAMPLE: EAY4132
NEW REPORT: RT490
46. Report of records in the ML processing unit containing one or more 5xx
fields which begin with ellipses.
PURPOSE: To identify records for which "dashed on" entries were added.
EXAMPLE: EDN2983
NEW REPORT: A report was produced.
47. Report of records by processing unit with a fixed field BL level of
"s" and any copy statement with a "1" Any class type can be present.
PURPOSE: To identify serial records which for which holdings have been
treated as a single piece monograph.
EXAMPLE: ABP3447
NEW REPORT: uldtmc47 was produced 08/01/2000
48. Report of authority records for which there are no associated
bibliographic records.
PURPOSE: To identify those authority records which are associated only
with bibliographic records which have been deleted from the database.
EXAMPLE: BDM1238
49. Report by processing unit of holdings records which contain one or
852 fields.
PURPOSE: When specific shelving information has been required, the 852
field has been used. This information needs to identified and deleted.
EXAMPLE: CIE0888
NOTE: Same as #36 above.
50. Report by processing unit of holdings records which contain one or
more 866 fields with text beginning "shelved" (not case senstitive).
PURPOSE: When specific shelving information has been required, the 852
field should have been used. In some instances the 866 field was used
in error, or, more commonly, the information was added as part of
the initial load of the database. This information needs to identified
and deleted.
51. Report of records which have in the record level NOTES field text
beginning with "this is a dummy"
PURPOSE: Dummy holdings records have been created for database repair
purposes. We need to be able to identify these records so that they
will not be moved to a new system.
EXAMPLE: EAS9796
NEW REPORT: A report was produced.
52. A program to identify all provisional authority records associated
with any processing unit. A provisional authority record is identified
by an "o" in the E/L fixed field.
PURPOSE: Sufficient work has been done with subsets of provisional
authority records. All remaining provisional authority records can
be eliminated.
EXAMPLES: BER5204, BBT7334
53. A program to identify bibliographic records containing one or more
selected 9xx MARC tags. These fields are 910, 911, 912, 913, 923, 924,
925, 926, 930, 931, 932, 934, 935, 970, 972, 971, 973. The report is
needed for each processing unit. Separate reports for each MARC tag
are not necessary.
PURPOSE: NOTIS defines a series of 9xx MARC tags which can be used
for local information. It has not been our policy to use these tags,
although RLIN records contain one or more such tags. The purpose of
this report is to identify uses of selected 9xx fields but not
including those used in RLIN records. Since there is the potential
for using selected 9xx fields for local information in another system,
identifying previous uses of the field is important.
NEW REPORT: uldtmca53 was produced 06/30/00
54. A program to identify bibliographic records containing one or more
940 fields. The report is needed for each processing units with the
exception of HL.
PURPOSE: Many RLIN records contain 940 fields. Since there is the
potential for using 940 fields for local information in
another system, identifying previous uses of the field is needed.
The 940 field is the only 9xx field used in RLIN records which may
used in another system.
EXAMPLE: ADF3790
NEW REPORT: uldtmc54 was produced 08/02/2000
55. Reports by processing unit of record containing duplicate values in
the 035 field.
PURPOSE: The primary purpose is to identify and correct duplicate uses
of OCLC numbers within a processing unit.
EXAMPLE: CAQ6430 and EBX1457.
NEW REPORTS: UZ090d selects duplicate RLIN numbers; UZ090 selects
duplicate OCLC numbers;
56. Lists of record numbers by processing unit of records with an "S" in
D/S fixed field and also containing one or more active copy
statements.
PURPOSE: When there is one or more active copy statements, the D/S
value should be "D"
EXAMPLE: AAC3002
NEW REPORT: UB0913A was produced on 8/22/00.
57. List of ML record numbers for ML authority records containing an 090
field.
PURPOSE: The 090 is a local field for cutter number. Those records
need to be identified so that the information can be captured and
made part of a non-BISON file, thereby eliminating a potential
reason why authority records cannot be overlaid.
EXAMPLE: BHJ4868
NEW REPORTS: MFZ005C and MZ0101. One selects ML records only.
58. Lists of record numbers for records in the GL processing unit which
meet the following criteria: copy statement status of 2 and location
code of lod, lod,p lodm, lodm,p, sed, sed,p sedm, and sedm,p. Output
needs to be divided into four reports: 1) lod and lod,p; 2) sed and
sed,p; 3) lodm and lodm,p; 4) sedm and sedm,p.
PURPOSES: To identify for statistical purposes all government document
titles of a continuing nature which are currently received and to review
the status of those records.
EXAMPLES: lod=CHE2907 lod,p=CHD5679 lodm=ECD9500
lodm,p=EBG7680 sed=EDA5625 sed,p=EBX1457 sedm=EDC4247
sedm,p=EBF4812
59. List of records with a copy status of 2, a location code of gl,in and
a subfield k value of "US" "CAN" or "NY"
PURPOSE: To identify for statistical purposes all government document
titles of a continuing are which are available in electronic format.
EXAMPLE: EDW2899
NEW REPORTS: UBGOV1 was produced on 8/15/00.
60. Reports by processing unit which list those records which have been
identified for deletion and the record status changed to 'x" but
the record level NOTES field of the copy holdings record begins with
"marked."
PURPOSE: "marked" is unexpected text for this field. Because of this
records with this text have not been identified by other reports.
EXAMPLE: EAW5305
NEW REPORT: A report was produced.
61. Reports by processing unit which list those records which have an
uppercase D in the second position of the fixed STAT field. There is
no fixed relationship between this character in the STAT field and the
content of the D/S fixed field or the status of the record.
PURPOSE: The uppercase D in the STAT fields removes the record
from all indexes other than record number. It has been discovered
that this character is in the records of at least once processing
unit. The character needs to be replaced.
EXAMPLE: EBX1457
62. Reports by processing units of OCLC numbers in suppressed records. A
record is suppressed if there is an "S" in the D/S field. The report
should contain BISON number and corresponding OCLC number.
EXAMPLE: EDW3041
NEW REPORT: JXM006 was produced on 3/28/01.
63. Reports by processing units of RLIN numbers in suppressed records. A
record is suppressed if there is an "S" in the D/S field. The report
should contain BISON number and corresponding RLIN number.
EXAMPLE: ADE6900
NEW REPORT: JXM007 was produced on 3/28/01.
64. Report of records containing OCLC numbers consisting of less than
eight digits. The OCLC number is in an 035 field as follows
(OCoLC)ocmnnnnnnnn This report needs to identify those numbers
consisting of only seven digits. It appears in all instances the
seven digit number is followed by a space and then several digits.
These final digits are not part of the actual OCLC number.
PURPOSE: In order to standardize the format for OCLC numbers, the
leading zero needs to be added to the OCLC number and the unrelated
digits deleted.
EXAMPLE: ECN9209
NEW REPORT: JXM008 was produced on 3/28/01.
65. For those records which have one or more copy statements with a class
type of "T" and a textual call number in the subfield b of "Electronic
Journal, reports by processing unit of record numbers and title
information from the 245 field.
PURPOSE: In order to implement the new policy of separate records for
electronic journals we need to capture the record numbers and titles
of those electronic journals which are on records for print versions
of journals.
EXAMPLE: CBG8540
66. Lists by processing units of item numbers containing more than one
barcode. Report should identify item record by complete record number
(BISON record number-three digit copy number identifier-four digit
item number) and include all barcodes contained in the item record.
PURPOSE: Aleph can handle only one barcode in an item record; in the
conversion the barcode with the highest number is assumed to be the
one in use with any others placed in a note area. We need to identify
and examine all instances of multiple barcodes in order to determine
which barcode is valid.
EXAMPLE: CAL2631-001-0003
67. List of authority records which lack a 010 field but contain a 100
field with a subfield g.
PURPOSE: To identify another category of authority records which need
to be replaced.
EXAMPLE: BGC1863
68. List of authority records which have one of the following fields 100,
110, 111, or 151 and which also have an 035 field beginning (CStRLIN)
PURPOSE: To identify another category of authority records which need
to be replaced.
EXAMPLE: BGH1666
69. For ML only a list of record numbers for records containing one or
more 700 fields with a subfield g.
EXAMPLE: ECU0891
NEW REPORT: tmccts700_ml.txt was produced on 7/24/01.
70. List of record numbers for records containing one or more copy
statements with a copy level note of "Duplicate copy; not
processed." Case and punctuation can vary.
EXAMPLE: ECV9055
71. List of record numbers with a location code of loe or loer and
a fixed field LANG value of chi.
EXAMPLE: EBN3940
72. List of record numbers with a location code of loe or loer and
a fixed field LANG value of kor.
EXAMPLE: ECT9924
73. List of record numbers with a location code of loe or loer and
a fixed field LANG value of jpn.
EXAMPLE: ECL7753
74. List of ML record numbers with a call number starting M 91=01 or
M;91=01 and no no 240 field or no 240 field with a |s Vocal score
EXAMPLES: EBA2209 (no 240); EBY9414 (240 without a |s Vocal score).
REPORT: CTSA74run on 11/05/2001.
75. List of records by processing unit which have one or more copy statements with a both a class
type of I and and a subfield b.
EXAMPLE: ADF0311
REPORT: CTSA75 run on 10/28/2001.
75a. List of records which have one or more copy statements with a class type of I, a location of
SEL, and a subfield b.
76. List of records, by processing unit, in the Data File format. Records in the Data File format
can be identified by a value of "D" in the FMT fixed field.
EXAMPLE: EEG8182
REPORT: ULDTMC76 run on 11/14/2001 for ALL units.
77. List of records, by processing unit, containing a 245 |h [computer file]
EXAMPLE: EDT2010
78. By processing unit the record numbers and text of 866 subfield Z fields
in MHLDS.
PURPOSE: In addition to holdings data free text messages have been
entered in 866 fields of MHLDS. Use of the subfield Z distinguishes
a message from holdings data and results in the display of the message
in the public mode.
EXAMPLE: CHC6251
79. By processing unit the record numbers for those records in the Serial format which have in
the 035 field text beginning (CStRLIN). There are such records for HL or PL.
EXAMPLES: ADG7634 (LL); EAG3096 (ML); CDX7694 (GL)
80. By processing unit the record numbers for those records which have 100, 110, 111, 700, 710, or
711 fields containing a subfied w.
EXAMPLE: EAS3147
B. Reports which are needed as records of specific
characteristics of the database. Reports should not be produced until the
NOTIS database is closed/new system is available. At this time the
assumption is that the NOTIS record number will be available in the
replacement system as a search key. Although it is anticipated that all of
these reports will be required, once the capabilities of the replacement
system are known the nature of some reports may change or instead of
reports some of the instructions may become part of the conversion
specifications.
1. By processing unit the record numbers and text of 866 subfield Z fields
in MHLDS.
PURPOSE: In addition to holdings data free text messages have been
entered in 866 fields of MHLDS. Use of the subfield Z distinguishes
a message from holdings data and results in the display of the message
in the public mode. A record of these messages is needed.
EXAMPLE: CHC6251
NOTE: Same as A78 above.
REPORT: CTS20866 run on 4/25/2001.
2. By processing unit the record numbers and text of 866 subfield X fields
in MHLDS.
PURPOSE: In addition to holdings data free text messages have been
entered in 866 fields of MHLDS. Use of the subfield X distinguishes
a message from holdings data. The message does not display in the
public mode. A record of these messages is needed.
3. The record numbers and text of each copy statement note which begins
with "um=for circulation status" or "um=for circ. status" All
characters can be upper or lower case.
Include all processing units including ML.
PURPOSE: Since the NOTIS software does not provide for a means of
handling bound-withs, a local approach was devised. An operator-added
public message has been added to the copy statement of any copy which
is for a subordinate title in a bound-with. The note instructs users
that the circulation status can be obtained by performing a keyword
search on the BISON record number for the title in the bound-with which
has the linked item record. This report will identify those records for
which a new way of handling bound-withs in a replacement system will
have to be developed.
EXAMPLE: CCZ5567
SCHEDULE: The report will be needed when the present database is
closed.
NEW REPORT: CTS1A2320 was run on 9/12/2001 for ALL units and
generated tmccts1a23_20all.txt
4. By processing unit the record numbers and text of each copy statement
note which begins with "um=" but which is followed by text other than
"for circulation status" The data can be in any position of the copy
notes field.
PURPOSE: NOTIS provides for creating full text public messages by
prefacing the desired text with "um=" It is necessary to identify each
use of this feature and to decide whether each should be added to the
new system. Because of the nature of the problem associated with notes
beginning "um=for circulation status" the present report should not be
combined with the one for "um=for circulation status"
EXAMPLE:CHC0723
SCHEDULE: The report will be needed when the present database is
closed.
NEW REPORT: CTS1A23 was run on 1/31/01, producing separate reports by unit.
PRELIMINARY REPORTS: Generating (tmccts_a23gl.txt; tmccts_a23hl.txt;
tmccts_a23ll.txt; tmccts_a23ml.txt; tmccts_a23pl.txt) which also
have spelling errors of the above. Can be modified to create a
report for B.3 above when needed.
5. The record numbers and text of each ML copy statement note. The text is
needed irrespective of whether it begins "um="
PURPOSE: ML did not follow a uniform approach in making notes for
bound-withs. Because of the various ways in which the situation was
handled, there is no option other than to capture and examine all copy
statement notes.
EXAMPLE: EAX0774 EAW9569 EAX1414 EAX1420
NEW REPORT: UB001M was produced on 3/4/00.
6. A list by processing unit and then by those record status codes which
are listed below of record numbers for each record with the
status of b (received and in cataloging backlog), c (not to be
catalged, d (cataloged separately with the use of this code generating
a public message), f (cataloged temporarily with a brief record,
cataloging copy found), or g (cataloged temporarily with a brief
record, cataloging copy not found) (compare with no.7 in pt.A above)
PURPOSE: These are NOTIS-defined status codes for which there may be
no parallel in another system. The use of one of these codes indicates
a special status which the record has. In a new system the records will
have to be designated in ways provided by the system, revised so that
they do not require a special status, or eliminated from the database.
EXAMPLE: CHD7283
EXISTING REPORTS: CTSTAB33 lists the records with a status of "x" It
does not provide the data by processing unit, however; UB333 lists by
processing unit all records with a status of c or e.
NEW REPORT: MB333g was produced on 6/30/99. This report captures status
"g" records for HL.
7. Separate lists by processing units of record numbers for copies which
contain any of the message codes which are listed below. Each
processing unit should receive individual lists for each code. The
codes can appear in any position in the copy statement note area. The
codes are as follows:
ci:mi ci:pr ci:re ci:cd ci:ls ci:dp ci:ll cr ci:jl
svs svr sv ci:rf ci:bd tm sc se
PURPOSE: NOTIS allows for codes to defined for use in copy holdings
statements. These codes result in messages being displayed in the
public mode.
EXAMPLE: CHC0723
NEW REPORT: UB001TA produced on 9/11/00 provides ci:cd, ci:dp, ci:jl,
ci:mi, ci:mn, ci:pr, ci:re
NEW REPORT: CTSA2320 produced on 2/4/01 providing ci:cd, ci:re, ci:rf ci:bd
PRELIMINARY REPORT: CTSA2320 has generated reports by UNIT for ALL codes
requested in reports (B.7, B.7a, and B.11). This can
be modified to generate separate reports, by UNIT,
for each individual code.
7a. List of record nubers with the copy level code of sh:sn
EXAMPLE: ABA4102
PRELIMINARY REPORT: CTSA2320 has generated reports by UNIT for ALL codes
requested in reports (B.7, B.7a, and B.11). This can
be modified to generate separate reports, by UNIT,
for each individual code.
8. A list of record numbers by processing unit and according to the MTHD
codes listed below which have an MHLD with an R/STAT of 4 and an MTHD
of "p" "g" "d" or "e"
9. Lists of records for each of these location codes "gl,in" "hl,in"
"ll,in" "ml,in" and "pl,in"
EXISTING REPORT: UB001SAS can provide this.
10. Lists by processing units of notes in fields NO and NV of active
O/P/Rs.
EXAMPLES: CHF4480 (EBH7009?) EDH5628
NEW REPORT: For NV, a new report is ready that
has been run. The program is ACQ10B52 and the reports
are BY UNIT and named, tmcacq10_b52gl.txt, etc.
NEW REPORT: For NO, a new report is ready that
has been run. The program is ACQ10B53 and the reports
are BY UNIT and named, tmcacq10_b53gl.txt, etc.
11. Lists by processing units of record numbers with one or more copy
statements containing the code "sws" in either lower or upper case.
EXAMPLE: ABD0580
PRELIMINARY REPORT: CTSA2320 has generated reports by UNIT for ALL codes
requested in reports (B.7, B.7a, and B.11). This can
be modified to generate separate reports, by UNIT,
for each individual code.
12. Lists by processing unit of record numbers with 730 fields containing
any of the following text. Text can be upper or lower case. Additional
text can follow the specific wording identified below.
All processing units: WEB RESOURCE
ULELECT
GL: DOC
DOCMF
DOCORIG
DOCORIGP
GIFTSUB
MEMBCOPY
MEMBCOPYCAN
NEWMAP
NEWMEDIA
NOCOPY
NOCOPYSER
NOCOPY CAN
NOCOPY ELEC
NOCOPY SER ELECT
NOCOPY WEB
NYDOC
HL: NOCOPY HSL
NOCOPY ELEC HSL
NOCOPY SER ELEC HSL
NOCOPY WEB HSL
HL NEGATIVE DECISION
HSL ELECTRONIC MONOGRAPH
HSL WEB RESOURCE
HLREQ MRC
LL: LLCOPY
LLINTERNET
LLORIGINAL
LLSCANBOX
LLSERIALS
LLSHARED
(description of this report is not complete)