This standard specifies a universal exchange format for bibliographic information. This standard applies to the exchange of information such as various types of bibliographic records and normalized records, and also applies to communication between data processing coefficients. This standard does not specify the length or content of each record, nor does it give specific meanings to field identifiers, indicators or subfield identifiers, which are specified by the implementation format. This standard provides a universal framework structure and is not used as a processing format within the system. Although this standard is designed for magnetic tapes, its structure can also be used for other data carriers. GB/T 2901-1992 Magnetic Tape Format for Bibliographic Information Exchange GB/T2901-1992 Standard Download Decompression Password: www.bzxz.net

National Standard of the People's Republic of China
Format for bibliographic information interchange on magnetic tape
Replaces GB2S0182
This standard refers to and adopts the international standard IS2709-1981 "Documentation work - Format for bibliographic information interchange on magnetic tape\. 1 Subject content and scope of application
This standard specifies a universal exchange format for bibliographic information. This standard is applicable to the exchange of information such as various bibliographic records and normalized records, and also to communication between data processing systems. This standard does not specify the length or content of each record, nor does it give specific meanings to field identifiers, indicators or subfield identifiers, which are specified by the implementation format. This standard provides a general framework structure and is not used as a processing format within the system. Although this standard is designed for magnetic tape, its structure can also be used for other data formats. 2 Reference standards
GB1988 Information processing - Seven-bit coded character set for information interchange 3 Terminology
3.1 Bibliographic record: A collection of sections, which includes a record header, a month area, and the date data of one or more bibliographic units processed as a whole.
Note: If the bibliographic record requires, it is allowed to connect several bibliographic records or parts of them to the record and execute it according to the provisions of the specific exchange formula. 3.2 Data field is a variable-length part of the bibliographic record that contains a specific range. It is located after the date area and corresponds to a directory item in the date area.
Note: A data field can contain one or more subfields. 3.3 Subfield identifier: A character composed of one or more characters used to identify a subfield. It indicates the starting position of the field: Note: Its first (or only) character must be the English symbol \US\ specified in GB1988. 3.4 Indicator: The data element at the beginning of the field indicates the nature of the data content in the field, the relationship between fields in the same record, or the information required for data processing.
3.5 Record: See 3.1. Bibliographic record
3.6 Date area: It is an index to the position of all data fields in the record. 3.7 Record header is the beginning of each record, providing a fixed-length area for processing parameters related to bibliographic records. 3.8 Table of contents area description: a group of parameters that describe the structure of the directory items in the table of contents area. 3.9 Delimiter: a control symbol used to logically or hierarchically divide and limit data units. 3.10 Field: a part of a field, which contains a certain content. 3.11 Subrecord: a group of fields in a record that can be processed as a whole. 3.12 Structure: the arrangement of the various components that make up a bibliographic record. 3.13 Field identifier: a group of symbols that identify a data field. It consists of three characters. State Technical Supervision Bureau approved on April 13, 1992 for implementation on December 1, 1992
4 Structure of bibliographic record interchange format
GB/T 2901--92
5 The structure of a bibliographic record is shown in Figure 1, and the detailed structure is shown in Figure 2. Figure 2 contains four different alternative structures for bibliographic fields.
Record Header
Data Area
Record Section Features
Figure - General Structure
A record contains the following fixed-length and variable-length fields, in the order shown in Figure 2. Record Header: Fixed-length
Data Area; Variable-length
Record Identifier Field: Variable-length
Reserved Fields: Variable-length
Data Fields: Variable-length
The data area, record identifier field, reserved fields, and data field all end with a segment delimiter, and the record ends with a record delimiter. The field separator and record separator use the following control characters respectively: G131988 control character \RS\ Record separator: GB188 control character \GS\ 4.1 Record header
As shown in Figure 2, the record header is fixed length, and its parts are defined as follows: 4.1.1 Record length (character position 0~4): The total number of characters in a record including the record header and the record separator, expressed as a five-digit number, right-aligned. When it is not five digits, it is filled with zeros on the left.
4.1.2 Record status (character position 5)
A character that describes the status of the record, for example, whether it is a new record or a modified record. The choice of characters and their meanings shall be specified in the execution format of the body. 4.1.3 Execution code (character position 6~9)
No specific provisions are made, and the exchange parties reach a special agreement. 4.1.4 The indicator length (character position 10) is represented by a decimal number indicating the number of character bits of the indicator. If the indicator is not used, the indicator length is set to zero. 4.1.5 The length of the sub-field identifier (character position 11) is represented by a decimal number indicating the number of character bits of the sub-field identifier. The first character or the only character of the sub-field identifier shall be the control character \1IS\ of (131988). If the sub-segment identifier is not used, the sub-segment identifier length is set to zero. 4.1.6 The data base address (character positions 12 to 16) is represented by a five-digit decimal number, aligned to the right. If it is less than five digits, the left side is The value is equal to the total number of characters in the record header and the day area including the segment separator at the end of the directory area. 4.1.7 User system definition (character position 17~19) 4.1.8 Month area description
Character position 20: Use a decimal number to indicate the number of characters occupied by the "data field length" of each day item in the month area. GB/T2901-92
Character position 21: Use a decimal number to indicate the number of characters occupied by the "starting character" of each directory item in the date area. Character position 22: Use a decimal number to indicate the "approximate length" of each directory item in the directory area. The number of characters in the "execution part" is reserved. Character position 23: reserved.
4.2 Directory area
The daily area consists of a directory item and a segment separator at the end of the daily area. Each daily item corresponds to a data segment (record identification field, reserved field, and monthly field). 4.2.1 Monthly item
The daily item consists of "field identifier", "data field length", "starting character position" and "execution part", and is listed in this order.
The length of the "field identifier" is three characters, and the length of each part of the daily item cannot exceed nine characters. All items in the subarea have the same structure.
4.2.2 Field Identifiers
Three numeric characters are used to identify the name of the corresponding data field. The meaning of these three characters shall be specified in the implementation format. 4.2.3 Data Field Length
The length of a data field has the following types:
H. Indicates the total number of characters of a data field (including indicators and field separators): b. Indicates the total number of characters of a data field greater than the "length" of the item. The allowed number is a binary number (n). In this case, the data field is divided into several parts. Except for the last part, the length of the other parts is the same (n). Each part has a corresponding subitem, which contains the same field identifier and the starting character position of the data in that part. The length of the data field corresponding to the subitem is not the last part, and its length is treated as (1); c. Indicates the number of characters of the last part of the data field in case b (including field separators). Under the circumstances described in bc, the items corresponding to the parts of the same data field must be adjacent in order. 4.2.4 The starting character position
is a 1-bit number indicating the position of the first character in the data field corresponding to the field identifier relative to the data base (for example, the starting character position of the data field of the th data field in the current month is cen). 4.2.5 Agreement execution part
If the "agreement execution part" exists in the item, it contains the competition information related to the judgment section corresponding to the item of this month 4.3 Data area
All data fields end with a field separator. There are three types of fields:
Record identification field: field identifier is 001. Reserved field: field identifier is 002 to 009. 00A to 00Z can be used when necessary. Note:) The characters can use uppercase or lowercase letters. So-called field: field identifier is 010 to 999. 04A to Z2Z can be used when necessary. Note: 2) Any combination of numbers and alphabetic characters may be: pure numbers, letters or a combination of letters. Letters may be capitalized or capitalized. When using alphanumeric characters, do not start with 00, as this is the default. 4.3.1 Record Identifiers
are characters that identify records and are determined by the organization that compiles the record. This field does not indicate the use of 4.3.2 The reserved section
provides parameters that may be needed to process the record. This section does not have indicators and paragraphs. 4.3.3 Date Fields
Each date field consists of an indicator (optional), a field identifier (optional), data and a field separator. The presence or absence of an indicator or field identifier is determined by the indicator length defined in the record header (character position 1) and the sub-paragraph length (character position 11) defined in the GB/T290192
document header, and their lengths must be consistent in each document field in the record. Each date field in the record must be written in one of the following four formats (Figure 2):
character position 0-4
12 -16
Record length
Record status
Executor
Indicator length
Subfield identifier
Data base address
User system
Length of "data field length"
Length of "start character"
Length of "fixed execution segment"
3 characters
Data base address
Field identifier IKI
Character identifier 002!
- D09 and LOA - 0OZ
Other segment identifiers
Segment identifiers
Digital length
Starting character
Execution part (optional)
Change items
Project
Segment separator
Record identifier field data
Segment separator
Reserved word data
Segment separator line
Segment separator
Field separator Storage character
Ningfen Huafu
Record separator
Record
Book month field format, 1
Indicator length is, = 0
Thousand field identifier length, = heart
Record fee #
Identification field
Reserved word exhibition
Book field
Record most beautiful board
Fixed length (called a word)
Guangzi enjoy service identifier
Xuedian separator|| tt||quarterly report identifier
school delimiter
year identifier
school period identifier
record delimiter
next record
Figure 2 detailed structure
indicator
field delimiter
explanation
word delimiter
indicator
field delimiter
record delimiter
a record
|Character calibration symbol
Special to field
Study section terminator
Indicator
Character study procedure
Sub-process flag
Additional storage
Indicator
[Subfield identifier
Sub-section identifier
Character section required
Record section required
Next record
GB/T 2901-92
The indicator length and subfield identifier length in the data-record header are both zero. a.
b: The length of the subfield identifier and the indicator in the data-record header is set to zero, and the length of the subfield identifier is set to 1 or greater than 1 c.
The length of the indicator and the indicator in the data-record header is set to 1 or greater than 1, and the length of the subfield identifier is set to zero. The length of the indicator, subfield identifier and the indicator in the data-record header and the length of the subfield identifier are 1 or greater than 1 A1 Introduction
GB/T 2901-92
Appendix A
GB/T2901-92 Recommended Implementation Format
China Common Exchange Format (CCFC)
Reference)
Since the State Administration of Standards promulgated and implemented GB2901-82 "Magnetic Tape Format for Bibliographic Information Exchange" in January 1983, the opinions reflected by the trial units are mainly that the original standard can no longer meet the requirements of the current computerization of document processing. For this reason, the Fourth Subcommittee of the National Technical Committee for Documentation Standardization decided to revise the standard from 1985 to 1986. According to the spirit of the Fourth Subcommittee's enlarged meeting, a special revision group was established in November 1985 to carry out the specific revision work. By May 1986, the working group had completed the draft of GB2901 "Magnetic Tape Format for Bibliographic Information Exchange" and its references. In this revision, the working group made a comprehensive revision of the main text of GB2901-82 based on ISO2709-1981. For the recommended format proposed, the basic idea of ​​the working group is: First, many document departments hope to have a detailed rule that is fully compatible with GB2901 and more flexible and practical, which is very necessary and beneficial for the use of various units and the future exchange of bibliographic information tapes at home and abroad. Second, the working group believes that as an exchange format, it should meet the following basic requirements: · Contain the most basic data items required for various types of documents; · Clear structure, easy to modify and expand;
, which is conducive to computer processing.
Third, the working group solicited the opinions of the document departments and determined the basic data items for monographs and serial publications. As for the basic data items of other types of documents, they could not be completed this time because the country lacked relevant standards and would be supplemented later. Based on the above ideas, the working group found that the Common Exchange Format (CCF) currently launched by the General Information Planning Office of UNESCO was formulated by the document work celebrities of various countries in the world today. Its design goal is to facilitate the exchange of bibliographic records between libraries and information work departments, so that each user unit can use a program to process records from different book institutions, and hopes to use this format as the basis for the database format of bibliographic institutions. The working group believes that this goal is correct and efforts should be made to achieve it. After carefully reviewing each item of the format and comparing it with other relevant standards, the working group believes that partial adjustments based on this format can meet the requirements of computerization of document work in my country. Therefore, the working group referred to the 1984 version of CCF and compiled the "China Common Exchange Format (CCFC) (reference document) 1>". The fourth subcommittee discussed and basically approved this document in January 1987. In August of the same year, it was also voted and approved by the National Technical Committee for Document Standardization. The reference document was tested by the China Institute of Scientific and Technical Information and proved to be feasible. In February 198B, UNESCO launched the second edition of CCF. According to the content of the new edition, the working group made some updates to the format content, which is the current format. However, the Common Exchange Format (CCF) itself is a new format that has not been tested in long-term practice. The working group also lacks sufficient experience and predictive ability in this regard, and it is inevitable that some ill-considered problems will occur. Therefore, this time it is only proposed as a recommended format. It is hoped that relevant units will refer to it for trial use and promote its improvement and development in practice. A2 Purpose, terminology and structure description
A2.1 Scope and application
This format is set for the following three purposes:
To enable the exchange of bibliographic records between libraries and information departments in the form of machine-readable tapes; Note: 1) China Common Exchange Format (CCFC) (reference document) was edited and supplemented by An Shulan, Qian Qilin, Lian Yachun, Pan Taiming, Sun Beixin and others in the working group.
CB/T 2901-92
b. To enable any bibliographic institution to use a computer program to process the bibliographic records obtained by different document service departments; c. To provide a reference for each bibliographic institution to design its own bibliographic database format. In order to achieve the above goals, this format adopts the following measures: a. Select a small number of data items necessary for identifying documents as basic data items recognized by all bibliographic institutions in the entire library and information community; b. Specify the required data items to adapt to various different recording practices; c. Based on the practical experience of the bibliographic institutions, further recommend some optional data items; d. The format also arranges some non-standard data items that may be selected by various bibliographic institutions; e. Provides a method for connecting related records and sections to establish connections between related bibliographic information. A2.2 Terminology
This format uses the following terms:
bibliographic recordWww.bzxZ.net
A set of strings of characters on a tape arranged in accordance with the format, including a record header, a table of contents, and bibliographic data that describes one or more bibliographic materials but is processed as a complete entity. It is referred to as a record in this document. Record header recordlabel
The first 24 characters of each record are used to provide the relevant parameters required for processing the record. Directory area directory
Consists of a number of directory entries. Each directory entry corresponds to a data field in this record. The entry contains the identifier of the corresponding field, its length, the position in the record, the identifier of the section to which it belongs, and the occurrence order of the field. Data field
The variable-length part of the record containing a specific range of data, located after the table of contents, is referred to as a field in this document. A segment contains one or more subfields and corresponds to a monthly entry in the monthly record. Subfield subficld
The part of a field that contains a specific information element and can be independently identified. Data element data-elerment
The smallest unit of information that can be identified. A data element in a field constitutes a subfield, which is identified by a subfield identifier, while in the record header and record, the data element is identified by the position of its characters. Field identifier tag
Three characters that identify a data segment.
Sub-letter identifier sublieldidentilierThe two characters at the beginning of a field used to identify the segment. The first character must be IS1 specified in GB1988. For the sake of writing, @ is used in this format.
Subfield code subfield cade
The second character of the field identifier; a letter or a number. Indicator indictor
The first two characters at the beginning of a segment are used to indicate the nature of the data content in the field, its relationship with other fields, or to provide parameters required for data processing.
Field separator
The last character of each data segment and date, also known as the field terminator. It is represented by character 1/14 (RS) in GB1988. Segment
A group of data fields that are used to describe a document and have the same segment identifier. Fields belonging to the same segment can only describe the same document entity.
Primary segment
GB/T2901-92
Fields in a record used to describe the primary recording object. Each record must and can only contain one primary segment. Seundurysegment
A segment in a record that describes documentary data related to the above-mentioned recording object. Each record can contain one or more secondary segments. Segment identifierscgmenl idemiliel
The first character of the agreed execution code within the day, used to identify the segment to which the corresponding field belongs. Occurrence identifierCrcurrenceidentifierThe second character of the agreed execution code within the month. Used to indicate the occurrence number of fields with the same identifier in the same segment. Vertical relationshipThe subordinate hierarchical relationship between documents, such as the subordinate relationship of a single volume to the series to which it belongs or the subordinate relationship of a journal article to the journal to which it belongs.
Horizontal relationshin different versions of the same document, different carrier forms, different language versions and different external versions. Chronological relations reflect the relationship between changes or evolutions in the passage of time between documents, such as a continuation relationship between the predecessor and the successor of a serial publication.
I5 level bibliographic level
A kind of mark given in the bibliographic record to illustrate the position of the document in the vertical relationship structure. Required fieldsnandalnry ficeld
Refers to the fields with the word "required" in the technical format. When the document itself has this information or can obtain this information through other channels, this type of segment must appear in the basic segment. Required subfield refers to a field marked with "Required" in this format. When the field to which it belongs appears in the record, the field must appear with it. Repeatable
refers to a field or subfield marked with "Repeatable" in this format. Such fields or subfields are allowed to appear multiple times in a section or field; fields or subfields marked with "Non-repeatable" are only allowed to appear once in the same section or subsection. Source record saurccrecardl
Records obtained from other bookkeeping institutions are called source records, which are used to distinguish bookkeeping records compiled by this unit. Bibliographical material
The objective facts described by the data in this section. Base item The most important or basic item that constitutes a record, that is, the data referred to by the level code in the seventh position of the header area. Base address data The position of the first character of the first data word relative to the first character of the record. Link or linkinug A method of establishing and defining a relationship between data segments, record segments, or records Related data itm
Data that has a horizontal or vertical relationship or a change relationship with another document described or identified in a certain section of the record. Related data is directly or indirectly related to the document described in the basic section. A2.3 References
This recommended format refers to the following standards, books, code tables and other related documents: GB1987 Information Processing Information Processing Interchange Seven-bit Coded Character Set G13/T2901 International Information Interchange Format G152559 Code for Service and Regional Names
GB3469 Code for Document Type and Document Media GB4880 Code for Language Name
GB5795 Chinese Standard Book Number
GB/T 2901—92
IS()4-1972 International code for periodical title abbreviations ISO3297—1975 International Standard Serial Number (ISSN) Common Exchange Format (CCF) 1988 UNESCO General Information Planning Division International CODEN Manual International CODEN Service Centre UNIMARC International Machine-Readable Format International Library Association (IFLA) International Serials Data System (ISLDS) Recommendation, UNESCO A2.4 Physical structure of records
This recommended format strictly complies with the provisions of GB/T2901. In order to meet the needs of information exchange, the following specific structure is adopted.
Each bibliographic record must have the following four parts: record header
table area
data field area
d, record separator
A2.4.1 Record header
At the beginning of each record, there is a header with a length of 24 characters, where the meaning of each character is as follows: character position
A2.4.2 Table of contents
Record length
Record status, represented by the code in the A4.1 code table for backup (this format is tentatively set as a space)
Bibliographic level, represented by the code in the A4.2 code table for backup (this format is tentatively set as two spaces) field indicator length, this format is specified as 2 sub-field identifier length, this format is specified as 2 data base address, that is, starting from the first character in the record with the middle bit zero, the starting position of the first data field in the record.
Reserve (this format is tentatively set to three spaces) The number of characters representing the length of the digital segment\ in the day item,This format specifies the number of characters that indicate the "starting position of the data field" in the 4 directory items, the number of characters that indicate the "agreed execution code length" in the 5 directory items, and the number of characters that indicate the "agreed execution code length" in the 2 format (temporarily set as a space in this format)
The daily record contains several daily records, each directory record corresponds to a data field, and indicates that the record contains this field and its characteristic parameters. This format specifies that each directory record consists of 11 characters. The end of the daily record uses a field separator to indicate the end of the month. English New
(24-character special)
Daily Record Wind||t t||(Variable length)
Data area
(Can be checked)
Record separator
(1 character)
Directory area
Daily item
(1 character)
(14 characters)
Directory item
(14 characters)
Daily item
(14 characters)
Stage sub-item
(14 characters)
Stage sub-item
(14 characters)
GB/T 2901 --92
Number of characters
Field identifier
(9 characters)
Field length
(4 characters)
Starting position
(5 characters)
Header structure
Record length
(5 characters)
Record length
(1 character)
(1 character)
Bookmark
(1 character)
(2 characters)||tt ||Indicator length
(characters)
Sub-character identifier length
(1 character)
Data base address
(5 characters)
(3 characters)
Data segment in the project change item
Length of the character
(1 character)
Start of character in the daily item
Number of characters for the period
(1 character)
Determination of the implementation of the grain display in the celebration item||tt ||Code length
(1 character)
"characters"
The first character of the identifier
【1 character】|(1 character)
Data segment end
Indicator
Field identifier
(2 characters)"(2 characters)
Field
(can be longer)
Field identifier
Subfield
Segment terminator
(2 characters) Character)
(can be long)"
(1 character)
Figure AICCF record structure diagram
A monthly item must have four parts:
Field identifier (three bits)
Field length (four bits)
Field starting position (five bits)
Agreed execution code (two bits)
This format defines the four components of the monthly item as follows: a. Segment identifier: A three-character code representing the name of the data field represented by the daily item. This format A3.3 lists all the field identifiers recommended for use to identify each specifically defined data field. If the unit needs to add data fields, a field identifier with a first letter (A~-Z) followed by two digits (0~9) can be used to indicate that the expanded field is of universal significance; if all three characters are text characters, it means that the expanded field is purely owned by the unit. h. Word length: refers to the total number of characters contained in the corresponding field, including the bit indicator and the one-bit field separator. If the data segment is the last segment of the record, the length of the field does not include the record separator. The number of characters representing the field length is specified as 4 in character position 20 of the header of this format. Therefore, the maximum length of a field shall not exceed 9999. c. Field starting position: refers to the position of the first character of the corresponding field relative to the data base address, expressed as a five-digit decimal number. The starting position of the first field of the record is "\\". d. Record segment identifier: a one-bit character indicating the segment to which the corresponding field belongs. This format specifies that the segment identifier is composed of numbers 0 to 9 and letters A to Z (see A2.5).
The first identifier is: A digit represents the number of times the same identification field appears in the same segment, and is composed of numbers 0 to 9. This format specifies that for a field that only appears once in a segment, this character bit is assigned the value "0\". When a repeatable field appears multiple times in a segment, the first occurrence is assigned the value "\0". The subsequent fields are assigned values ​​in ascending order from 1 to 9 in their respective directory entries. The structure diagram of a monthly item is as follows: Segment identifier
3 characters
Daily item example:
3000033028910
Field length
1 character
In the above example, the meanings of each bit are as follows:
Segment starting position
5 characters
Segment identifier
Character
Quality
1 character
The field identifier is the first three digits \300", which means that the field content corresponding to this daily item is a personal name. The next 4 characters \0033\ indicate that the corresponding length of the field is 33 characters. "00289\These 5 characters mean that the first character of this field is the 289th character starting from the data base address. The following \1 indicates that the field belongs to a sub-section of this record. If the field belongs to the basic section, the section identifier should be \0\". The last decimal digit "0" means that this field appears for the first time in section 1.
42.4.3 Data field area
The data field area contains the following data fields. This format stipulates that each data field must have the following components: Field indicator (two-bit)
One or more sub-characters (variable part) Segment separator (part)
The specific definitions of these three parts are as follows: Field indicator: two-character, definition and representation method see the description of A3.3. a.
b. Subfield: This format stipulates that it starts with a sub-segment identifier, followed by a data string, and then ends with another sub-field identifier or a field separator. The subfield identifier uses two characters. The first character must be 1/15 in the national standard GB1988. In this article, it is represented by @. The second character can be used to indicate the content of the field. C. Field separator: The field separator is 1/14 in GB1988 and is the last character of each field. However, if it is the last paragraph of the record, it must be followed by the field separator and the record separator. The following table shows a field structure containing 1 subfield: Field separator
Field identifier
2 characters
The following table shows a field structure containing two subfields: Next paragraph
Variable length
Paragraph end
1 character
Word indicator
2 characters
First subparagraph identifier
2 characters
character pairs
Below is an example of a field:
GB/T2901-92
The first subparagraph
11@[email protected]@D1953-@E673Second subfield identifier
2 characters
Second subparagraph
Variable length
Segment stop line
The field identifier of this field is "300\, which appears in the directory entry corresponding to this field, but not in this field. The first character of the field "1\ is the first field indicator, which means that this author is primarily responsible for the document described in this record section of the record. The second character \1\ means that the author name used here is taken from the authority file of the institution that created this record. The name printed in the document may be different in form from the name given here. Subfield A begins with its own subfield identifier @A and contains the significant part of the author's name. In this case, it is the family name. This part is also the data item used to sort in the sequential index. Subfield B records the part of the author's name other than the significant part. The content in subfield D is the author's date of birth, which is obviously taken from the authority file of the creating agency. The two-digit decimal code "673" in field E is A4.8. It means that the author is responsible for guiding the research work reported. The field ends with a field separator. The schematic symbol here is a solid square. In fact, the character used is the character 1/14 in the GB1988 standard, not other symbols. A2.4.4 Record separator
This format stipulates that the record separator must be 1/13 in GB1988. It is placed at the end of the record to indicate the end of the record. A2.5 Logical structure and connection method of records This format allows the bibliographic information of more than one document to be recorded in one record. The specific implementation method is that in one record, several sections are set up, and several fields are set up in the sections. The bibliographic information of each related document is placed in different sections, and their mutual relationship is represented by the section connection field. The bibliographic information of the same document is placed in each data field of a section, and the mutual relationship between the sections is represented by the field connection field. This format divides the sections into two types: basic sections and secondary sections. The basic section is a required section in a bibliographic record, used to describe the bibliographic information of the most important or most basic recording object of this record. Therefore, only one basic section is allowed in a record. The secondary section is used to describe the bibliographic information of related documents that have vertical, horizontal and change relationships with the primary recording object. The bibliographic information in the secondary section can be direct bibliographic information or a control number used to point to another record that already describes the document. A2.5.1 Relationship between sections
A section consists of all fields that identify and/or describe the same document. In most cases, a record only contains descriptive information of a single document. At this time, the record has 4 sections, as shown in the figure below: Record
Header Section
Data Field
Basic Section
However, many bibliographic agencies need to describe or identify several documents in one record, such as a monograph and its corresponding book; a conference proceedings and each academic report contained in the proceedings; a group of journals formed due to changes in the journal titles within a certain period of time, etc. At this time, the same bibliographic description needs to include information about several interrelated documents. Therefore, it is necessary to use multiple sections in the record, as shown in the following figure: Record
Header date sub-section
Data field
-- E -
-Basic section-
Level section-
-Sub-section [-
That is to say, if two or more documents are related to each other, they will only appear in the same book record, and the relationship between these books will be
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.