GB/T 36068-2018 China Machine-Readable Collection Format GB/T36068-2018 |tt||Standard compression package decompression password: www.bzxz.net
This standard specifies the standard structure of computer-readable collection records, including field identifiers, field indicators and subfield identifiers, as well as the logical and physical format of the content identifiers of collection records on media such as tapes, floppy disks and optical disks. This standard is applicable to revealing the collection and management information of documents, and is used in conjunction with GB/T 33286-2016 "China machine-readable catalogue format for bibliographic data" (referred to as CNMARC bibliographic format).

ICS01.140.20
National Standard of the People's Republic of China
GB/T36068—2018
China machine-readable catalogue format for holdings data2018-03-15Issued
General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of ChinaStandardization Administration of the People's Republic of China
2018-10-01Implementation
GB/T36068—2018
Normative Reference Documents
Terms and Definitions
Format Structure
Format Description
Overall Structure
Function Module
Data Field Setting Principles
Application Rules
Required Words Segment
Level of collection description
Repeatability of fields and subfields
Subfield order
Filling characters
Code data values
Number subfields
Connection data between fields
Identification symbols
Format application
Comparison between fields of CNMARC collection records and GB/T24424-2009 entriesComparison between relevant fields of CNMARC collection records and CNMARC bibliographic recordsExplanatory notes·
Field description Description structure
Fields for domestic use
6 Detailed description of record header and data fields
Record header (recordlabel)
Identification block (identificationblock)6.2
Coded information block (codedinformationblock)6.4
Holdings location and retrieval block (locationandaccessblock): Notesblock (notesblock)...
Extentofholdingsblock (extentofholdingsblock)6.6
Responsibilityblock (responsibilityblock)6.8
Source information block (sourceinformationblock) Appendix A (informative appendix) Complete example
References
This standard was drafted according to the rules given in GB/T1.1-2009. This standard was proposed and managed by the National Technical Committee for Information and Document Standardization (SAC/TC4). GB/T36068—2018
The drafting units of this standard: National Library of China, Peking University Library, Documentation and Information Center of Chinese Academy of Sciences, Beijing Normal University Library The main drafters of this standard: He Yan, Cao Qian, Huai Yan, Liu Chunyue, Zhu Xuejun, Hou Xuhong. 1
GB/T36068—2018
0.1 Background
Machine-Readable Catalogue (MARC) is a data format that can be recognized and processed by computers and developed with the development of computer automation. The advent of MARC marks the transition of document cataloging from traditional manual operation to the automated era of computer processing. my country's research on MARC started in the 1980s. At present, the MARC format has become an indispensable tool for the communication and exchange of information resources in my country's libraries and information departments. Machine-readable catalogs have become an indispensable part of libraries and document collection units. The collection information they contain plays an important role in the preservation and protection of documents and reader services. As early as 1999, the UNIMARC Standing Committee (PUC) of the International Federation of Library Associations and Institutions (IFLA) commissioned a working group to compile the UNIMARC collection format, and completed and published the "Universal Machine-Readable Catalog Manual: Holding Format (Version 1)" in 2007. Due to the long-term lack of standards for the machine-readable catalog format of collection data in my country, various libraries and document collection units have different definitions of the machine-readable self-recording format of collection data. In order to enable my country to have a unified and standardized collection data compilation standard and provide a reference or basis for the establishment of collection databases and collection data processing, the national standard "China machine-readable catalog format for holdings data" is specially formulated. This standard can be used in conjunction with GB/T33286-2016. 0.2 Preparation Principles
This standard follows GB/T24424-2009 "Holdings statements", and refers to the "UNIMARC Manual: Holdings format (Version 1)" published by the International Federation of Library Associations and Institutions (IFLA) in 2007 and GB/T33286-2016 "China machine-readable catalogue format for bibliographic data", combined with The characteristics of various types of documents in my country, cataloguing practices and user needs, as well as the current status of collection disclosure in domestic document collection institutions are compiled. 0.3 Main changes
The main difference between this standard and the "Universal Machine Readable Catalog Manual: Holdings Format (2007 First Edition)" [UNIMARC Manual: Holdings Format (Version 1)" is that the "Universal Machine Readable Catalog Manual: Holdings Format (2007 First Edition)" follows the relevant provisions of ISO10324 and is only applicable to collection descriptions of level 3 and below. This standard follows GB/T24424-2009 The relevant provisions are applicable not only to the collection descriptions of level 3 and below, but also to the collection descriptions of level 4, and the relevant content about the collection description of level 4 is added.Ⅱ
HiiKAoNiKAca
1 Scope
China Machine Readable Collection Format
GB/T36068—2018
This standard specifies the standard structure of computer-readable collection records, including field identifiers, field indicators and subfield identifiers, as well as the logical and physical format of the content identifiers of collection records on media such as tapes, floppy disks and CDs. This standard applies to documents that reveal Collection and management information. 2 Normative referenced documents
The following documents are indispensable for the application of this document. For any referenced document with a date, only the version with the date applies to this document. For any referenced document without a date, the latest version (including all amendments) applies to this document. GB/T1988 Information technology Seven-bit coded character set for information exchange Basic set of Chinese coded character set for information exchange GB/T2312
GB/T2659
Codes for names of countries and regions in the world
Information and document information exchange format
GB/T 2901 1
GB/T4880.2 Language name code Part 2: 3-letter code GB/T7408 Data elements and interchange formats Information exchange date and time representation GB/T24424-2009 Collection description
GB/T33286-2016 China machine-read bibliographic format ISO646 Information technology ISO 7-bit coded character set for information interchange ISO5426 Extension of the Latin alphabet coded character set for bibliographic information interchange ISO5426-2 Information and documentation - Extension of the Latin alphabet coded character set for bibliographic information interchange Part 2: Latin characters for European minority languages ​​and old printed scriptsISO 5427 Extension of the Cyrillic alphabet coded character set for bibliographic information interchange ISO 5428 Greek alphabet coded character set for bibliographic information interchange ISO 6438 Documentation-African coded character set for bibliographic information interchange ISO 8957 Information and documentation-Hebrew alphabet coded character sets for bibliographic information interchange ISO 10586 Information and documentation-Georgian alphabet coded character set for bibliographic information interchange Information technology-Universal Multiple-1
HiiKAoNiKAca
GB/T36068—2018
Octet Coded Character Set (UCS)-Amendment l: Glagolitic, Coptic, Georgian and other characters charac-ters]
Universal Machine Readable Catalog Manual: Holdings Format (Version 12007) [UNIMARC manual: holdings format (Version 12007)
3 Terms and definitions
GB/T 24424-2009 and GB/T 33286-2016 defined and the following terms and definitions apply to this document 3.1
Integrating unit integrating unit
Basic bibliographic unit or secondary bibliographic unit added or changed by updating, which cannot be in a discrete state but is integrated into a whole.
Note: An integrating unit can be finite or continuous. 3.2
Updated whole iteration
An example of an integrated resource published for the first time or after it has been updated. 3.3
non-continuing resource
non-continuing resource
-A bibliographic resource that is published once or within a limited period of time3.4
continuing resource
continuing resource
a resource that has no clear end date in terms of publication timeNote: Continuing resources include serial publications and continuously updated integrating resources.3.5
integrating resourceintegratingresourceA bibliographic resource that is supplemented or modified through updates. The updated part is not discrete from the original resource, but integrated with the original resource.
Note: Integrating resources can be either finite resources or continuous resources. Examples of integrating resources include updated loose-leaf/loose-leaf pages, updated web pages, and updated databases.
4 Format structure
4.1 Format description
This format is a general format designed for data exchange and does not specify the internal format, content, or data structure of each system. The final result of any conversion process between systems shall comply with the provisions of this standard. In order to reduce the problems that may arise in data conversion, the definitions of field identifiers, fields and subfields in the internal format of the data exchange organization system should be consistent with the corresponding parts of this standard. 4.2 Overall structure
This format is a specific form of GB/T2901. It specifies the standard record structure that should be followed for each collection record used for exchange, which is composed of:
a) Record header: composed of 24 characters. b) Address directory area: The area contains one or more directory items, each of which consists of a 3-digit field identifier (referred to as field number)2
iiiKAoNikAca
and the field length and the starting character position of the field (starting from the first data field) GB/T36068—2018
Data field area: composed of several fixed-length and variable-length fields, each of which is separated by a field separator. Record terminator: used to mark the end of the record and distinguish it from the next record. d
The record structure is as follows:
Record header
Address directory area
Data field area
For the format description of the overall structure, see Chapter 5 of GB/T33286-2016. 4.3 Functional modules
Record terminator
The fields in the collection record are divided into different functional modules. The first (leftmost) digit of the field identifier indicates the module to which the field belongs.
Identification block: contains the number used to identify the record or collection. Code information block: contains fixed-length data elements (usually codes) that describe multiple aspects of the record or data. Collection location and retrieval block: contains information that identifies the institution, physical location, or available collection of the bibliographic unit. Notes block: contains notes for public display that help identify the document described in the collection record. Collection range block: contains information such as identification instructions, style, number and year for obtaining specific bibliographic items (primary or secondary units) in the collection.
Responsibility block: contains the form of responsibility mark associated with the document described in the collection record. Source of information block: contains the source of the record, as well as the cataloger's related notes on the data that are not publicly displayed. 9
National use block: contains local data established by the creator of the record. This standard does not define field identifiers for intra-system exchange, but some national use fields in the CNMARC bibliographic format can be applied to this format. 4.4
Data field setting principles
4.4.1 The field identifier should identify a field from two aspects: a) the type of string (such as collection location and accession number); b) the function performed by the string in the record (such as level). When assigning specific values ​​to the character positions of the field identifier, these two aspects should be reflected. Field identifiers can be either numeric or alphabetic. When assigning values, numerical values ​​are preferred, and can be expanded to alphabetic values ​​(lower case preferred) if necessary. 4.4.2 Indicators should be based on field identifiers, but their use should be as consistent as possible in all fields. Indicators can be either numbers or letters. When assigning values, numerical values ​​are preferred, and can be expanded to alphabetic values ​​(lower case preferred) if necessary. 4.4.3 Subfield identifiers should be based on field identifiers, and the same subfield identifiers should be used to identify common data elements in all fields as much as possible. Subfield identifiers can be either numbers or letters. When assigning values, alphabetic values ​​(lower case preferred) are preferred, and can be expanded to numerical values ​​if necessary. Subfield identifiers are assigned for identification, not for document sorting. Except that subfield $6 should appear as the first subfield, there is no specific order for subfield identifiers, and they should be determined according to the data. GB/T24424-2009 defines the order and format of data elements to ensure consistency in recording and interpretation; however, it does not define the display order of data areas in collection descriptions. 4.4.4 Descriptive information recorded in notes is not used as a retrieval point. 5 Application Rules
5.1 Mandatory fields
Except for the record header and the address directory area, the following fields are mandatory fields. 3
HiiKAoNiKAca
GB/T36068—2018
001 Collection record identification number
004 Related bibliographic record identification number
100 Common processing data (contains only specific data elements) 252 Collection location and retrieval number or 256 Electronic resource address and retrieval 801 Record source
The presence or absence of other fields depends on the level of the collection record, which is determined by the cataloging agency that created the record. However, if a data element exists, it should be fully identified according to the rules defined in this standard. 5.2 Collection Description Levels
According to the application rules of GB/T24424-2009, collection descriptions include the following four levels: a) Level 1 collection:
Identifies the title and collection institution of the document. This level is suitable for describing single-part documents. For multi-part documents and continuous resources, this level cannot indicate the scope of the collection. Regardless of the preservation principle or integrity of the collection, this level should record the institutional identifier of each bibliographic document. At a minimum, it should include the bibliographic item identifier and the collection location identifier of the collection. The bibliographic item identifier can be included in the identification number 004 field of the relevant bibliographic record. The collection location identifier can be included in the institutional identifier $a subfield of the collection location and retrieval number 252 field.
b) Level 2 collection:
Level 2 collections have a general collection description added to Level 1 collections, i.e., in addition to the requirements for Level 1 collections, they should at least include 1) receiving or acquisition status (170$a/0); 2) general preservation policy (171$a/0); 3) integrity mark (171$a/5).
c) Level 3 collection:
Level 3 collections have a brief description of the collection scope. The brief collection description can be open or closed. If the numbering and/or age are required, only the highest level is recorded.
d) Level 4 collection:
Level 4 collections have a detailed description of the collection scope. The detailed collection description can be itemized or compressed, open or closed, and the numbering and/or age should be recorded at the most detailed level (including all levels). 5.3 Repeatability of Fields and Subfields
If the word "repeatable" is associated with a field, it means that the field can be repeated in a record. If "repeatable" is associated with a subfield, it means that the subfield can be repeated in a field. 5.4 Subfield Order
The order of subfields is not specified by the value of the subfield identifier. Subfield identifiers are assigned values ​​for identification purposes, not for sorting.
5.5 Filler Characters
Filler characters may be used when the cataloging agency is unable to determine a content identifier or code information. The filler character is a graphic character "「" (vertical bar) in GB/T1988, which is 7/12 in the seven-bit code table. It avoids the use of 0 (zero) or space (#), which have specific meanings in this format.
Filler characters may appear in the following situations: a) the cataloguing agency does not enable this content identifier or assign a code to this information; or b) the cataloguing agency enables this content identifier or assigns a code to this information, but does not know the exact 4
HiiKAoNiKAca
value in this particular record; or
GB/T36068—2018
the cataloguing agency uses similar values ​​for this content identifier or code information, but they cannot be converted into exact equivalent values ​​in the CNMARC collection format.
Filler characters may not be used in record headers, address directory areas, field identifiers, or text data; they may not be used to replace mandatory coded data elements, subfield identifiers, bibliographic identifiers, or other special characters; and they may not be used to replace all codes in an optional coded segment (in which case the field should be abandoned). 5.6 Code Data Values
The following rules are used to fill in code values ​​in record headers and coded data subfields: # - No information provided.
u—Unknown. Used when the exact value to be filled in with the code cannot be determined. x—Not Applicable. Used when a characteristic is not applicable to the type of entity being described. y—Non-Existent. Used when the code cannot represent the entity being described. z—Other. Used when the characteristics of the entity are known, but none of the defined code values ​​are appropriate. [—Filler. Used when no code is intended to be assigned. 5.7
Numeric Subfields
This standard defines the following numeric subfields for use in collection records: Subfield
System Code or Source
Connection Text
Authority Record Number
Relational Term Code
Internal Field Connection Data
Field Letters/Words
5.8 Interfield Connection Data
5.8.1$6 Internal Field Connection Data
2-Field Block
256 Field
7-Field Block
7-Field Block
2-Field Block: 5-Field Block
2-Field Block; 3-Field Block: 5-Field Block$6 The subfield contains the data that connects this field to other fields in the record and a code that explains the reason for the connection. If subfield $6 is enabled, the first two elements of the subfield (character positions 0-2) are required, and the third element (character positions 3-5) is optional. Therefore, the length of subfield $6 can be three or six characters. Subfield $6 is always the first subfield in the field. The data recorded in subfield $6 is recorded according to the following structure: Data element name
(1) Connection description code
(2) Connection number
(3) Connected field identifier
The data element description is as follows:
1) Connection description code (character position
Number of characters
This code explains the reason for the connection between fields. Its value is defined as a-alternating text
Z-other connection reasons
Character position
GB/T36068—2018
Connection Number (character positions 1-2)
The $6 subfield of the record's respective fields that are linked together is a two-digit number. Its function is to match linked fields together and is not to be used as a sequence number or address number in any case. The link number may be assigned at random as long as the assigned link number is consistent in each field of the linked pair or group and can be distinguished from the link numbers assigned to other fields in the record.
Linked Field Identifier (Character Positions 3-5)3)
This element is a three-character identifier for the linked fields. This element is optional: if the identifiers of the two linked fields are the same, this element is usually omitted. 5.8.2 $7 Field Letters/Words
This subfield contains the code of letters or words that represent the main content of the field. Cataloging words (collection location, note, etc.) are identified in field 100 of the record (character positions 20-21). Some institutions need to record collection locations, notes, and collection descriptions in multiple scripts if the language has both transliteration and another script (also called alternate script forms) (e.g., simplified and traditional Chinese characters; kana and kanji systems for Japanese). Alternative script identifiers for collection locations, notes, and collection descriptions may all exist in a single collection record.
The alternate script form of the collection location description may be recorded in an additional 2-Collection Location field, using a $7 cataloging script subfield and the form of the basic collection location subfield to distinguish it from the script defined in field 100. Alternative scripts for notes or collection descriptions are recorded repeatedly in fields in their own field block. Different script forms of the same collection location, note, or collection description are connected by an S6 linking subfield, and these scripts are identified in the $7 cataloging script subfield and the basic address subfield. When the code in positions 20-21 of field 100 identifies the same letter/script as the letter/script identified in the $7 subfield, the $7 subfield in the field can usually be omitted. Example:
001163279
100##$aYYYYMMDDenga03######bao252##$6a01$a[Organization Identifier]$i[Request Number]252##$6a01$7ca$a[Cyrillic Organization Identifier]$huiCyrillic Request Number5.9 Identification symbols
GB/T24424-2009 specifies the identification symbols and separators in general collection items and collection range items, but does not specify the separators used between data items, as well as the identification symbols in the collection location data item, the recording date item and the collection note item. For the sake of consistency among CNMARC users, this standard recommends that, with a few exceptions, punctuation between subfields can be omitted. The use of all other punctuation marks in the record can be determined according to the actual situation of the cataloging agency issuing the record. 5.10 Format application
Collection item self-record
This format is mainly used to support the information exchange of collection item records. The records created for this purpose can also support alternate collection items related to collection location and retrieval. 5-Fields can be used to describe the style, identification description, numbering and age of the collection. Bibliographic entry model
According to GB/T24424-2009, a bibliographic entry is defined as follows: Bibliographic entry
Basic bibliographic unit (repeatable)
Non-serial publication
Single part
Multi-part
Serial publication/integrated resource
Auxiliary bibliographic unit (repeatable)
Non-serial publication
Single part
Multi-part
Serial publication/integrated resource
GB/T36068—2018
According to this model: A bibliographic entry can be composed of one or more bibliographic units. Each bibliographic unit can be a basic unit or an auxiliary unit, or a continuous, integrated or non-continuous unit. Multiple numbers
Each continuing resource or multi-part unit has its own numbering system, and the numbering system that is appropriate to the basic bibliographic unit specified by the collection record identifier should be recorded.
For alternate numbers, if there is an increasing numbering system or other numbering systems in addition to the regular numbering system, the alternate numbering system and other numbering systems are recorded after the regular numbering system with equivalent identifiers. When alternate numbers exist, there must be a relationship between the different numbering systems.
Example 1:
v.1-5=total 1-60
5.11 Comparison of CNMARC collection record fields with GB/T24424-2009 description items CNMARC collection record
Record header
0-Identification block
1-Coding information block
2-Collection location and retrieval block
3-Note block
5-Collection scope block
7-Knowledge responsibility block
8-Source information block
GB/T24424-2009 item/data element
Item identification item
Collection data item
Institution identification
Branch collection location identification
Copy identification
Request number
Report date item!
·General collection item
Type of unit identifier
Integrity identifier
Acquisition status identifier
Preservation principle identifier
Collection scope item
Unit name
Date of creation or last update of the record collection description1)
GB/T24424—2009 description item
General collection item, unit identifier type
Item identification item
General collection item
Collection data item
Collection notes item
Collection scope item
CNMARC collection record field/subfield
100 $a/0-7
Record header and 1-
Record header character position 7
171$a/5
170$a/0
171$a/0
GB/T36068—2018
Unit range
Special range notes
Collection notes
5.12 Comparison between relevant fields of CNMARC collection records and CNMARC bibliographic records CNMARC collection record fields||t t||004 Related bibliographic record identification number
035 Other system control number
252 Collection location and retrieval number
256 Electronic resource address and retrieval
CNMARC bibliographic record fields
001 Record identification number
035 Other system control number
852 Collection location and retrieval number
856 Electronic resource address and retrieval
Valid CNMARC bibliographic record fields in CNMARC collection records 130 Coded data field: microform
135 Coded data field: electronic resources
141 Coded data field: foreign ancient books - morphological characteristics of the collection 194 Coded data field: Chinese ancient books - morphological characteristics of the collection 300 General notes
301 Identification number notes
302 Coded information notes
310 Binding and acquisition method notes
316 Notes on existing collections
317 Source notes
318 Operation notes|| tt||345 Notes on interview information
702 Personal name - Secondary knowledge responsibility (related to the collection) 712 Group name - Secondary knowledge responsibility (related to the collection) 722 Family name - Secondary knowledge responsibility (related to the collection) 5.13 Explanatory notes
This standard adopts the following conventions:
"$" is used instead of the separator IS1 (1/15 position in the character set) in GB/T1988. As the first symbol of the subfield identifier: The character "#" is used to indicate a blank in the sample. b)
The separator of the field is not displayed in the sample. c
"Undefined" means that there is no defined value assigned to the position where the indicator is located. This position indicates a blank. Some subfields require the use of code tables maintained externally. These code tables are included in Appendix e)
A of GB/T33286-2016.
5.14 Field Description Structure
Chapter 6 describes the names, definitions, occurrences, indicators, subfields and contents of various data fields in detail, and provides application examples. See Appendix A for complete examples. Each data field in this standard is described in the following steps: a) Field Description: A brief description of the contents of each field; 811Comparison between CNMARC collection record fields and GB/T24424-2009 description items CNMARC collection record
Record header
0—Identification block
1—Coding information block
2—Collection location and retrieval block
3—Notes block
5—Collection scope block
7—Knowledge responsibility block
8—Source information block
GB/T24424-2009 item/data element
Item identification item
Collection data item
Institution identification
Branch collection location identification
Copy identification
Request number
Report date item!
·General collection item
Type of unit identifier
Integrity identifier
Acquisition status identifier
Preservation principle identifier
Collection scope item
Unit name
Date of creation or last update of the record collection description1)
GB/T24424—2009 description item
General collection item, unit identifier type
Item identification item
General collection item
Collection data item
Collection notes item
Collection scope item
CNMARC collection record field/subfield
100 $a/0-7
Record header and 1-
Record header character position 7
171$a/5
170$a/0
171$a/0
GB/T36068—2018
Unit range
Special range notes
Collection notes
5.12 Comparison between relevant fields of CNMARC collection records and CNMARC bibliographic records CNMARC collection record fields||t t||004 Related bibliographic record identification number
035 Other system control number
252 Collection location and retrieval number
256 Electronic resource address and retrieval
CNMARC bibliographic record fields
001 Record identification number
035 Other system control number
852 Collection location and retrieval number
856 Electronic resource address and retrieval
Valid CNMARC bibliographic record fields in CNMARC collection records 130 Coded data field: microform
135 Coded data field: electronic resources
141 Coded data field: foreign ancient books - morphological characteristics of the collection 194 Coded data field: Chinese ancient books - morphological characteristics of the collection 300 General notes
301 Identification number notes
302 Coded information notes
310 Binding and acquisition method notes
316 Notes on existing collections
317 Source notes
318 Operation notes|| tt||345 Notes on interview information
702 Personal name - Secondary knowledge responsibility (related to the collection) 712 Group name - Secondary knowledge responsibility (related to the collection) 722 Family name - Secondary knowledge responsibility (related to the collection) 5.13 Explanatory notes
This standard adopts the following conventions:
"$" is used instead of the separator IS1 (1/15 position in the character set) in GB/T1988. As the first symbol of the subfield identifier: The character "#" is used to indicate a blank in the sample. b)
The separator of the field is not displayed in the sample. c
"Undefined" means that there is no defined value assigned to the position where the indicator is located. This position indicates a blank. Some subfields require the use of code tables maintained externally. These code tables are included in Appendix e)
A of GB/T33286-2016.
5.14 Field Description Structure
Chapter 6 describes the names, definitions, occurrences, indicators, subfields and contents of various data fields in detail, and provides application examples. See Appendix A for complete examples. Each data field in this standard is described in the following steps: a) Field Description: A brief description of the contents of each field; 811Comparison between CNMARC collection record fields and GB/T24424-2009 description items CNMARC collection record
Record header
0—Identification block
1—Coding information block
2—Collection location and retrieval block
3—Notes block
5—Collection scope block
7—Knowledge responsibility block
8—Source information block
GB/T24424-2009 item/data element
Item identification item
Collection data itemwwW.bzxz.Net
Institution identification
Branch collection location identification
Copy identification
Request number
Report date item!
·General collection item
Type of unit identifier
Integrity identifier
Acquisition status identifier
Preservation principle identifier
Collection scope item
Unit name
Date of creation or last update of the record collection description1)
GB/T24424—2009 description item
General collection item, unit identifier type
Item identification item
General collection item
Collection data item
Collection notes item
Collection scope item
CNMARC collection record field/subfield
100 $a/0-7
Record header and 1-
Record header character position 7
171$a/5
170$a/0
171$a/0
GB/T36068—2018
Unit range
Special range notes
Collection notes
5.12 Comparison between relevant fields of CNMARC collection records and CNMARC bibliographic records CNMARC collection record fields||t t||004 Related bibliographic record identification number
035 Other system control number
252 Collection location and retrieval number
256 Electronic resource address and retrieval
CNMARC bibliographic record fields
001 Record identification number
035 Other system control number
852 Collection location and retrieval number
856 Electronic resource address and retrieval
Valid CNMARC bibliographic record fields in CNMARC collection records 130 Coded data field: microform
135 Coded data field: electronic resources
141 Coded data field: foreign ancient books - morphological characteristics of the collection 194 Coded data field: Chinese ancient books - morphological characteristics of the collection 300 General notes
301 Identification number notes
302 Coded information notes
310 Binding and acquisition method notes
316 Notes on existing collections
317 Source notes
318 Operation notes|| tt||345 Notes on interview information
702 Personal name - Secondary knowledge responsibility (related to the collection) 712 Group name - Secondary knowledge responsibility (related to the collection) 722 Family name - Secondary knowledge responsibility (related to the collection) 5.13 Explanatory notes
This standard adopts the following conventions:
"$" is used instead of the separator IS1 (1/15 position in the character set) in GB/T1988. As the first symbol of the subfield identifier: The character "#" is used to indicate a blank in the sample. b)
The separator of the field is not displayed in the sample. c
"Undefined" means that there is no defined value assigned to the position where the indicator is located. This position indicates a blank. Some subfields require the use of code tables maintained externally. These code tables are included in Appendix e)
A of GB/T33286-2016.
5.14 Field Description Structure
Chapter 6 describes the names, definitions, occurrences, indicators, subfields and contents of various data fields in detail, and provides application examples. See Appendix A for complete examples. Each data field in this standard is described in the following steps: a) Field Description: A brief description of the contents of each field; 8
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.