| |
MASTERFILE Databases
USMARC Record Format and Attribute Sets
This document is in two parts. The first describes common fields in the USMARC record format sent by the EBSCOHost Z39.50 server. These fields are common to the EBSCO Masterfile databases. Other databases will have other field definitions, and will be described as the databases become available in USMARC format..
The second part describes the semantics of the Z39.50 BIB-1 Attribute set as it relates to EBSCOHost.
MARC Record Structure:
The data is formatted in a standard MARC record structure. This record structure conforms to the international standard for bibliographic interchange on magnetic tape (ISO 2709-1981) and with its American equivalent ANSI Z39.2-1979.
The record structure used is the same as that used for US MARC, Canadian MARC, UK MARC and many others.
MARC Field Definitions:
Note: for the purposes of the following examples, the subfield introducer code (Hex 1F) is shown as a dollar sign ($).
|
Tag |
Description |
Repeats |
|
001 |
Control Number
This field is the EBSCO Accession Number (AN) for the item. The AN is a 10 digit number, the first 6 digits indicate the date on which the item was indexed (in the form YYMMDD). |
No |
|
008 |
Fixed Data Elements:
0-6 = blank
7-10 = Year
11-34 = blank
35-37 = language |
No |
|
016 |
Accession Number
This field is identical to the Control Number (001)
First indicator: blank
Second indicator: blank
Subfield codes:
$a Accession Number |
No |
|
100 |
Author
The author of the article.
First indicator: 1
Second indicator: 0
Subfield codes:
$a Author Name |
Yes |
|
245 |
Article Title
First indicator: blank or 1 (not used)
Second indicator: 0 to 9 number of characters ignored in filing
Subfield codes:
$a Article title |
No |
|
300 |
Length of Article
Number of pages for the article.
First indicator: blank
Second indicator: blank
Subfield codes:
$a Number of pages.
E.G. $a3p |
No |
|
500 |
Locals Message
A message indicating whether the journal is local to the library appears here. Another 500 field may also be generated with local notes.
First indicator: blank
Second indicator: blank
Subfield codes:
$a Text
E.G.
$aThis journal is available in the library. |
Yes |
|
520 |
Abstract
Summary of the article being indexed
First indicator: blank
Second indicator: blank
Subfield codes:
$a Summary Information
$9 ISBN of reviewed book if record is a Book Review
|
No |
|
650 |
Subject Heading
First indicator: blank
Second indicator: 4 other subject heading
Subfield codes:
$a Subject heading |
No |
|
700 |
Additional Author
First indicator: 1
Second indicator: 0
Subfield codes:
$a Author Name |
Yes |
|
773 |
Journal Source
Summary of the article being indexed
First indicator: blank
Second indicator: blank
Subfield codes:
$g Date, Volume, Issue starting page and illustration
information. (If page length is greater than 1 a +
sign follows the page number)
$t Journal title
$x ISSN
E.G.
$g1/18/93, Vol. 141 Issue 3, p43+, 1bw$tTime$x0040781X |
|
|
856 |
Full Text Indicator
If this article has associated full text, the first $i field contains "TEXT*". There may be multiple $i fields. Subsequent $i fields may contain descriptors fors for images. These formats are yet to be specified.
First indicator: blank
Second indicator: blank
Subfield codes:
$i TEXT*
E.G.
$aTEXT* |
No |
|
900 |
Full Text Fields
Each separate paragraph in a full text article becomes 900 field. The title of the article, subtitles, bulleted points, etc. each become one 900 field.
Full text can be large. If the MARC record grows larger than the preferred or exceptional record sizes, or larger than an internal server limit, the full text is truncated, and a 900 field is created with the message "Text Truncated".
A copyright message usually appears in the full text at the end. It will appear after the "text truncated" message if text is truncated.
First indicator: blank
Second indicator: blank
Subfield codes:
$a The text
E.G.
$aTitle of Article |
Yes |
|
903 |
Publication date in YYMMDD format
Date of publication of the article
First indicator: blank
Second indicator: blank
Subfield codes:
$a Date of publication (yymmdd)
E.G.
$a930118 |
No |
|
904 |
Title as a Descriptive Phrase
Prior to November of 1987, the article title was a descriptive phrase of the article not the exact title. For articles prior to Nov 87 the title will appear in the 245 tag and there will also be a 904 tag which includes the phrase "Wording of title may not be exact."
First indicator: blank
Second indicator: blank
Subfield codes:
$a Text string "Wording of title may not be exact."
E.G.
$aWording of title may not be exact. |
No |
Indicators
Indicators are the two characters immediately preceding the subfield identifier. Most indicators are set to "blank" "blank" with the exception of the following fields.
650 Field (subject): the a subfield is added with indicator SPACE 4.
- Indicator 4 means "Source not specified".
100, 510, 700 Fields: Author processing.
- if the author includes the text "ET AL", indicators "10" are used.
- if there is a hyphen then the indicators are set to ""20", meaning "multiple surnames"
- otherwise the indicators are "00".
- if the text JR is in the author name, the JR is stored in subfield c.
Full Text
If full text for the item is available, it may be sent via USMARC or requested via a proprietary mechanism.
856 field. If full text is available for the item, an 856 field is included as follows:
856 $i TEXT*
This is an indication to the client that full text can be requested via another mechanism (if not using USMARC format- see the document EBSCOHost Full Text Via Z39.50 and Non-EBSCO Clients for more information). This field is generated in both BRIEF and FULL element sets. If a client makes use of the alternative Full text delivery mechanism, the server will stop sending full text in the USMARC because it knows then that the client can request full text separately.
900 field. Each full text title and paragraph is converted into one 900 field. The result is that the USMARC record will have the title, abstract, author, and then as much of the full text as fits in the record size requested by the client.
BIB-1 ATTRIBUTES
This section describes the way the EBSCOHost server responds to various attributes in the BIB-1 Attribute set described in Appendix 3 of the ANSI/NISO Z39.50-1995 document.
1. BIB-1 USE ATTRIBUTES
These entry points are used by the Masterfile Series of databases. The numbers correspond to the BIB-1 USE attribute set. If an unsupported USE attribute is specified, the server uses a default set of search indexes.
Entry point indexes can be indexed by Word, Phrase, or Numerically. In a Word index, each word is separately indexed. A phrase index searches the entire field as one word. A numeric index is similar to a Word index but can also be searched using the relation attributes. Phrase and Numeric indexes are indicated in the description of the index.
|
Attribute |
Description, Usage in Masterfile |
|
1003 |
Author |
|
4 |
Title |
|
5 |
Title |
|
6 |
Title |
|
40 |
Title |
|
21 |
Subject |
|
62 |
Abstract |
|
8 |
ISSN (Phrase Indexed) |
|
1028 |
Accession number |
|
31 |
Date of Publication (Numeric Indexed) |
|
1033 |
Journal Name |
|
1014 |
Full text exists for this record (search for "Y") |
|
1035 |
Full text, plus author, title, journal name, abstract |
|
Any other |
Default attribute set is used (author, title, journal name, abstract) |
2. BIB-1 Relation Attributes
|
Attribute |
Description, Usage in Masterfile |
|
1 |
< |
|
2 |
<= |
|
3 |
= |
|
4 |
>= |
|
5 |
> |
|
All rest |
N/A |
- BIB-1 Position Attribute
This attribute is not used by EBSCOHost.
4. BIB-1 Structure Attribute
|
Attribute |
Description, Usage in Masterfile |
|
1 |
Phrase |
|
6 |
Word List |
|
All rest |
Default to "Phrase" |
5. BIB-1 Truncation Attribute
|
Attribute |
Description, Usage in Masterfile |
|
1 |
Right truncation |
|
2 |
Left truncation |
|
3 |
Left and right truncation |
|
4 |
No truncation |
|
All rest |
Default to "No truncation" |
6. BIB-1 Completeness Attribute
This attribute is not used by EBSCOHost.
|
