Some standard content:
ICs 01. 140. 20
National Standard of the People's Republic of China
GB/T 20163--2006
China MARC format for archives2006-03-15 Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China Standardization Administration of China
2006-10-01 ImplementationbzxZ.net
Foreword·
Scope
2 Normative References
3 Terms and Definitions
4 General
4.1 Field Description
4.2 Symbol Specification -
Record Structure·
Frame Structure:
Record Header,
Record Table of Contents
Variable Length Segment
Required Fields·
Record Length·
Record Connection
Character Set
Data Repetition
Record Block Function
Record Header and Data fields - This specification · 6.1
Fields and subfields are repeated:
Field order
Subfield order.
Characters used when significant
6.6 Non-sort control characters
6.7 Form and content of data
6.8 Identifiers used in the description
6.9 Chinese extension fields
Record header and data fields -
7.1 Record header
Appearance
- Field description
Field identifiers, indicators and subfields 7.1.4 Fixed-length data elements
7.1.5 Notes on field contents
7.1.6 Related paragraphs ·
7.2 Data fields -
TiKANiKAca -
GB/T 20163—2006
GB/T 20163—2006
Identification block
Coding information block
Description information block
Notes block
Record connection block
Related title block
Subject analysis block
File responsibility block
International use block
Domestic use block
Appendix A (Normative Appendix)
China Archives Machine Readable Catalog Format Data Format Sample AT
Record exchange format
Record learning period format
Appendix (Informative Appendix)
B, 1Record header example
China archives machine-readable recording format data field example identification block example
Coded information block example
Description information block example
Note block example
Record connection block example
Related title block example·
Subject analysis block example
File responsibility block example·
International use block example
Domestic use block example·
iikAoNiKAca
GB/T20163--2006
The framework format of this standard is compiled based on ISO2709:1996 Information and Documentation Information Interchange Format formulated by the International Organization for Standardization, and the implementation format of this standard is compiled based on the International Readable Cataloguing Format formulated by the International Federation of Library Associations and Institutions and the International Standard Archival Description Rules (General Principles) formulated by the International Council on Archives, combined with the actual situation of my country's archives machine-readable cataloguing. This standard was proposed by the State Archives Administration.
This standard was approved by the National Archives and Document Standardization Technical Committee. The drafting units of this standard are: Shanghai Archives Administration, Shanghai Branch of Nanjing Political College. The main drafters of this standard are: Zhang Zhengqiang, Zou Weinong, Duan Rongting, Yan Lin, Ka Gang, Chang Jianhong, Zhang Wenyou, Zhang Dawei. GB/T 20163—2006
The sharing of archive information resources is an indispensable part of realizing the sharing of overall document information resources in my country. With the establishment and formation of computer networks of all levels and types in my country, a favorable network environment has been created for the sharing of archive information resources. However, without a unified and standardized archive machine-readable catalog format, the sharing of archive information resources cannot be realized. For this reason, this standard is specially formulated to standardize the archive machine-readable catalog format, laying the foundation for realizing the sharing of archive information resources and establishing a high-quality archive catalog database. 1 Scope
China Archive Machine-Readable Catalog Format
This standard specifies the archive computer machine-readable catalog format that is compatible with relevant international and national standards. This standard applies to the establishment of archives and diaries database and the processing and exchange of archives catalog data. 2 Normative references
iiKAONiKAca-
GB/T20163—2006
The clauses in the following documents become the clauses of this standard through reference in this standard: For all referenced documents with dates, all subsequent amendments (excluding errors) or revisions are not applicable to this standard. However, the parties who reach an agreement based on this standard are encouraged to study whether the latest versions of these documents can be used. For all referenced documents without dates, the latest versions are applicable to this standard. G3/T1988—1998 Information technology - Seven-bit coded character set for information exchange (eq1ISO/1EC60646:1991) GB/T2260 Administrative division code of the People's Republic of China GB2312 Coded character set for information exchange GB/T2659 Code for names of countries and regions of the world GB/T2901 Magnetic tape format for information exchange (GB/T·2901—1992: neq2709:1981) G3/T4880.2—2000 Code for language names Part 2: Three-letter code (eqVISO639-2:1998) GB/T 7108 Data elements and exchange formats Date and time representation for information exchange (GB/T7408-1994, ISO 8601:1988)
GB13000 Information technology General multi-octet code character set GB/T15418 Rules for archive classification and indexing
GEB/T18894—2002 Electronic document archiving and management specifications DA/T13 Rules for file number compilation
DA/T18 Rules for archive entry
DA/T19 Rules for archive subject indexing
ISO2709:1996 International Standard for Information and Document Information Exchange Formats Rules for Archival Description (General Principles), International Council on Archives Manual of International Machine-Readable Cataloging Formats: Bibliographic Formats, International Federation of Library Associations and Institutions 3 Terms and definitions
The following terms and definitions apply to this standard. 3.1
Access point
Access point is a name, word and code specifically used for access catalog records. 3.2
Content identifier content designator is used to identify data elements or provide additional information about data elements. Content identifiers include field identifiers, indicators and sub-segment identifiers.
data element
data element
The smallest unit of information that is clearly identified. In variable-length fields, data elements are identified by sub-field identifiers, which constitute sub-fields. In record headers, sub-fields and fixed-length sub-segments, data elements consisting of codes are identified by the position of their characters. 1
GB/T 20163—2006
data element identifierdata element identifierSee sub-field identifier.
directory areadirectory
Index of the position of each field in the data area of a record. 3.6
Field Tield
A string identified by a field identifier and defined, which can contain one or more sub-fields. 3.7
Field separator
A control character used to find the end of each variable-length field to distinguish each adjacent field. It is also used at the end of the sub-area. 3.8
Fill character
Used in a specific character position to indicate a character that cannot give a corresponding code value at that character position, although the character position has been defined. 3.9
Fixed length subfieldA subfield of fixed length, whose appearance is specified by the rules of this standard, may contain one or more data elements and may appear in a fixed-length data segment, such as the $a field in the 100 field, or in a variable-length field, such as the $z field in the 200 field. 3.10
Field indicator indicalor
Characters (numeric or alphabetic) associated with variable-length fields, used to provide additional information about the contents of the field, the relationship between the field and other segments in the record, and operational information required for certain data processing. 3.11
Record record
A collection of fields, consisting of a record header, a record number area, a data field area, and a record terminator. 3.12
Record header recordbe
Located at the beginning of each record: a field that provides processing parameters for the record. 3.13
Source format sourceformat
The data format of computer-readable records that existed before conversion to the Chinese Archives Machine Readable Catalog format. 3.14
Subfield subfield
A clearly defined unit of information within a segment (see data element). 3.15
Subfield identifier A two-character code used to identify different subfields in a variable-length field. The first character is a separator, which is always a special character specified by ISO2709. The second character is the subfield code, which can be either a number or a letter. 3.16
Field identifier tag
A set of three-digit symbols used to mark a field. 2
Textual data
Data other than code data used for display in a catalog record, or text data. 3. 18
Unit of description
iiKANi KAca-
CB/T 20163—2006
A document or collection of documents in any form of carrier that is treated as an entity or is itself an entity and forms the basis of a record.
Variable length field
Field of variable length. It can contain one or more data elements or subfields. Its length is calculated in characters, including the number of characters occupied by text data and the sum of the number of characters occupied by field indicators, subfield identifiers and field separators. 4 General
4.1 Field description
This standard provides guidance for the use of various fields. In order to ensure the completeness of the description and the convenience of searching, this standard describes the field identifiers in ascending order and stipulates that the description of various data fields is generally described in the following structure: a) Field definition, briefly describing the content of each field. b) Occurrence: explain whether each field is repeated, whether it is a mandatory field or an optional field. In some fields, it also includes descriptions and restrictions on the occurrence of the field. ) Indicator: explain the value of the indicator: d) Subfield: list the subfields in sequence, and list the definition after each subfield: and its applicable scope, repetition and whether it is mandatory. e) Field content notes: explain the relationship between the data content of the field and the subfields in the field, including applicable specifications, identification symbols for entry, and suggestions for the form of field content. f) Related fields: list the fields or data elements related to the content of this field, in order to facilitate the comparison of fields, and briefly explain the usage of related fields.
If one of the items is missing in the description structure of a field, it is assumed that the content of the item has not been described in the field. 4.2 Symbol specifications
The fields, indicators and subfields listed in this standard and in the related descriptions and examples adopt the following specifications for symbols: a) Field identifier: The symbol "$" is used to represent 1S1. in GB/T1988--1998 as the first symbol of the subfield identifier. b) Space character: The symbol " is used to represent the space character in GB/T1988-1998, that is, the character at position 2/0 in the seven-bit coded character set code table. "卡" represents the space in the difficult text of this standard, or represents the space that is not obvious from the text but must appear.
e) Subfield separator: The symbol \@" is used to represent IS2 in GB/T1988-1998, as the field separator in the complete example. Although each field of the machine-readable catalog record generated according to this standard is actually separated by "②\, it is omitted in the examples where each field is applied separately. d) Record end character: The symbol "%" is used to represent (IS3 in GB/T1988-1998. is used as the record end character in the complete example. e) "Undefined": When the phrase "undefined" is used in conjunction with an indicator position, it means that there is no value assigned to the indicator position and it is filled with a space. System-external character symbol: For system-external characters that cannot be recorded at present, the system-external character symbol "=" is used instead. g) Non-sorting characters: Use the characters at positions 08/08 and 08/09 in the ISO6630 monthly control character set, namely "NBS" and \≠VRF≠\, which respectively indicate "non-sorting start" and "non-sorting end", indicating that the data between these two sorting symbols is not used for sorting.
GB/T 20163—2006
5 Record structure
5.1 Frame structure
This standard is the implementation format of ISO 2709 developed by the International Organization for Standardization. It specifies the frame structure that must be followed for machine-readable catalog data records used for exchange, namely, the record header, record directory area, data field area (variable length) and record end character. The structure of the record is as follows;
Record header
5.2 Record header
Record subarea
Data field area
Record terminator
According to ISO2709, each record starts with a 24-character record header, which contains data about the record structure defined in ISO2709 and data elements specifically defined by this standard as the implementation format of ISO2709. These data elements defined as the implementation format are: record type, record level, record level relationship, archival control, description level, record completeness, and whether DA/T 18 is used in the abbreviated record. The data elements in the record header are mainly used to meet the needs of record processing and indirectly used to confirm the archival recording unit".
5.3 Record directory area
After the record header is the record's monthly area. Each directory item consists of three parts: a field identifier represented by a three-digit decimal number, the length of the data field represented by a four-digit decimal number, and the starting character position of the field represented by a five-digit decimal number. In addition, no other characters are allowed in the directory item. The structure of the record's monthly item is as follows: First monthly item
Identifier
Field length
Starting character position
Second directory item
Other directory items
Monthly item
Identifier
Field length
Starting character position
Second directory item
Other directory items
Monthly item
The second part of the area is the number of characters in the field, which includes all the characters of the field: indicator, subfield identifier, text characters or code data, and field separator. After the segment length is the field start character position, that is, the field start character position relative to the first character position of the variable-length field part of the record. The position of the first character of the first variable-length field is 0, and the character position in the entire record is indicated by the numbers on the 12th to 16th bits in the record header. The length of the field identifier is 3 characters, the length of the data is 4 characters, and the length of the start character position is 5 characters. All directory entries consisting of 12 characters correspond to each data field in the record. The delimiter that marks the end of the sub-area is GB/T. IS2 in 1988-1998. The directory entries in the directory area are sorted by the first digit of the field identifier. The data fields in the record do not need to be sorted because their positions are completely determined by the directory area. 5.4 Variable-length field
The variable-length data field follows the date area and usually contains file directory data rather than processing data. The structure of the variable-length data field is as follows:
The structure of the data (control) field (00-):
1) The definition of the file record unit is shown in 3.18. Data
Field separator
The structure of the data field (01 to 999)
Indicator
Indicator
Subfield identifier
$a(etc.)
iiKANi KAca-
GB/T 20163-2006
other subfields
delimiters
Except for the field identifiers of the nested structure fields in the 4-record connection block, the segment identifier does not appear in the data field, but only in the content area. The field with the field identifier constructed with the value 00- (such as 001) consists only of data and field separators.Other data fields consist of two-digit indicators and several subfields following them. Each subfield starts with a subfield identifier, which consists of a subfield delimiter and a code (a letter or a number) that identifies the subfield. The subfield delimiter is IS1 in GB/T1988-1998. Following the subfield identifier is code data or text data of any length, but if the data length in the field is fixed, there is a special description for it. The last subfield in the field ends with a field separator, and the segment separator is IS2 in GB/T1988-1998. After the last data character in the record is the field separator IS2, and after IS2 is the record terminator that marks the end of the record. The record terminator is IS3 in GB/T1988-1998. 5.5 Mandatory fields
The following are the fields that must be provided in the machine-readable monthly record of the file compiled in accordance with this standard, that is, the mandatory fields: 001--record identification number
020--file number
100--general processing data
101--—file language
200--title and statement of responsibility
801--record source
5, 6 Record length
The record length is limited to 99 99 characters in this standard, and can also be determined by negotiation between the exchange units. 5.7 Record Connection
In actual cataloging work, if it is necessary to connect the record of one cataloging unit with the record of another cataloging unit, the connection fields in the record connection block 4---
can be used. These fields are specially set to establish such a connection. For more detailed instructions, see the description of each field in this block and the introduction of this block. A connection field includes the cataloging information of another related cataloging unit, regardless of whether the cataloging unit has separate record information. A connection field can be composed of several sub-fields, each of which contains nested machine-readable catalog field identifiers, indicators, sub-field identifiers and field contents formed in the format of this standard. 25.8 Character Strategy
The machine-readable catalog of archives generated according to this standard should use the national character set standard, or the character set standard established by the International Organization for Standardization. The record header, record month area, indicator, subfield identifier and the code values specified in this standard should use the functional characters and graphic characters of GB/T1988-1998, which is considered to be the default character set in the machine-readable catalog record. In the a subfield of the 100th paragraph, the 26th-29th and 30th-33rd character positions are used to specify the character set used in the record. The character set used should be a national standard character set or a character set confirmed or registered by the International Organization for Standardization. 2) Note that the nested period is not retrieved through the record's date area, because a complete link field has only one month item in the same area. The field identifier nested in the link field indicates the relationship between the archival record unit identified by the link field and the archival record unit recorded in this record.
GB/T 20163—2006
In the machine-readable diary generated according to this standard, the control function characters of GB/T1988-1998 are allowed to be used. The commonly used control function characters are as follows:
a) Control function character IS1 in GB/T1988-1998: used as the first character of the two characters in the subfield identifier. b) Control function character IS2 in GB/T1988-1998: used as a field separator. Used at the end of the target area and each data field.
c) Control function character IS3 in GB/T1988-1998: used as a record end character. Used at the end of each record. 5.9 Data repetition
There are four cases where data may be repeated in different forms: data appears in both coded form and text form, and in both display form and non-display form. a
b) The file contains the same information in different languages and scripts. DA/T18 stipulates under what circumstances, how to record parallel data, and in the machine-readable recording of the file generated according to this standard, different subfields or repeated subfields are used to achieve this.
c) Provide multiple recording languages and literature for readers familiar with multiple languages and literature. (l) In order to meet various complex output requirements, the same information is repeated in different text forms. 5.10 Record block function
The data field area of this standard is divided into 10 blocks. The first number of each field identifier indicates the block to which the field belongs. The functions of each block are divided as follows:
O---Identification block; records the number that identifies the record or identifies the recording unit and is recorded on the entity. 1---Coded information block, which records the fixed-length coded number element that describes various aspects of the record or data. 2--
Description information block: records the description items specified in A/T18, but excludes notes and related codes (such as archive code, microfilm number, etc.).
3--Note block: records any notes about the description unit or notes about related records to supplement the description items, access points and other contents.
Record connection block: records the relationship between the record and other archival records, including time relationship, level relationship and parallel relationship.
5--Related title block: records the titles related to the archives recorded, which usually appear on the entity of the record unit such as archives, except for the main title.
6---Subject analysis block: records the subject data of different systems composed of words or symbols.
6---File responsibility block: records the individuals, institutions, groups and families who have some form of responsibility for the description unit. 8---International Use Block: Records fields that are not suitable for blocks 0 to 7 according to international agreements. 9----·-National Use Block: Records data with a certain meaning, such as collection information related to a certain unit. 6 Record Header and Data Fields - Basic Instructions 6.1 Field and Subfield Repetition
Fields and subfields in a record can be repeated, but they should comply with the appearance rules of the data field description and the rules for defining subfields. Fields nested in the link field of a small record should be repeated in the same way as the corresponding fields in the record. Whether the data to be repeated is repeated by repeating the entire field or by repeating its subfields in a non-repeatable field is specified in the field. These rules must be followed to ensure consistency when different users use this standard.
6.2 Section Sequence
Sections in a record do not need to be ordered. The title sequence of each item in the sub-area is not necessarily the actual order of the sections. 6.3 Order of Subfields
The value of the subfield identifier indicates that there is no prescribed order for the subfields. Only in certain circumstances is a recommendation made for the position of a particular subfield. However, the fields corresponding to DA/T 18 are recorded in the order specified by DA/T 18, which also determines the order of the subfields.
Subfields with numerical identifiers are placed before or after the part to which they apply according to the following rules: Subfields $3.$6.$7 are placed before all other subfields, while $2, $4, S5 are placed after all other subfields: The above groups of preceding or following are sorted in ascending mathematical order. The mathematical subfield is as follows;
String 1 connection data (see 4---Record connection mapping) $2 System code
$3 Authorized record number
$4 Relational term
$5 Field use organization
$6 Inter-field connection data
$7 Field alphabet/literature
$8 Undefined
$9 Chinese phonetic symbol
6.4 Characters
In the machine-readable journal of the archive produced in accordance with this standard, when the data is in text form, any character corresponding to the graphic symbol may be used. In the position of the field indicator of the coded subfield, the characters allowed to be used are specified by the relevant section of the technical specification. 6.5 Characters used in case of ambiguity
Filling characters are used when the correct value cannot be assigned to a coded data item, for example, when there is no complete corresponding value in the source format. The filler character is a \|\ (vertical bar) character in GB/1 1988-1998.That is, the characters on the 7/12th bit in the seven-bit coded character set code table.
filler characters cannot be used in record headers, record directory areas, field identifiers or text data, nor can they replace required coded data elements, subfield identifiers, special identifiers and other specific characters, or replace all codes in an optional abbreviation segment (that is, the character should not be used).
For code numbers, when the recording authority has never specified a code value for a particular type, such as field 100 (general processing data), position 22-24 (language of recording), this filler character is used to indicate that the recording authority has not used a code to describe the language of recording here. In some cases, filler characters should be contrasted with the use of codes "#\, \u", "\"\x"\y", \z". The following is the most general description of the use of these codes;
is empty, no more values. This code can be used when there are fewer code values than the allocated character positions in the fixed-length field.
u is unknown. When the recording staff cannot find the data required for this item and requires as much as possible, This code is used when it is possible to give a clear code.
Combination. This code is used when a combination of multiple single code features appears on the recorded object. xNot applicable. This code is used when the defined code feature is not applicable to the type of record to be recorded. yNot present. This code is used when the defined code feature does not exist for a specific recording unit. %Other. This code is used when codes have been defined and the characteristics of the record are known, but none of the defined codes are suitable. Sometimes, such as when there is no 1 in the code table for a certain type of record or u is already used for a specific type of record, this code can be used as "unknown". For field indicators, when the recording agency does not record a specific type of value, such as the first indicator (conference indicator) of field 711 (organization name), filler characters can be used in the indicator position. Fillers may also be used when "", "\ and " appear in the indicator position basket, that is, "\ combination", "unknown" and "other". Fillers may also be used if this standard format has a special indicator, but the indicator value cannot be derived from the source format's wild code value.
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.