Some standard content:
ICS 35.240.30
National Standard of the People's Republic of China
GB/T40205—2021
Information and documentation
Holdings information format
Information and documentation-Schema for holdings information(ISO 20775:2009.MOD)
Published on 2021-05-21
State Administration for Market Regulation
National Administration of Standardization
Implemented on 2021-12-01
-riKacerKAca-
Normative references
3 Terms, definitions and abbreviations
Terms and definitions
Abbreviations
4 Detailed requirements
From discovery to delivery
Response to collection usage queries||t t||5 Format Overview
5.2 Resources
5.3 Collections
6 Abstract Formats·
7 XMLSchena
Appendix A (Informative Appendix) Detailed description of terms and definitions Appendix B (Informative Appendix) Hierarchical structure of abstract formats References
-rrKaeerkca-
GB/T40205—2021
-riKacerKAca-
This standard was drafted in accordance with the rules given in GB/T1.12009. GB/T40205—2021
This standard was revised using the redrafting method and adopts IS020775:2009 Information and Document Collection Information Format. The technical differences between this standard and IS020775:2009 and their reasons are as follows: Due to the normative references, this standard has been adjusted with technical differences to meet my country's technical conditions. The adjustments are concentrated in Chapter 2 "Normative References". The specific adjustments are as follows:? Replaced IS04217 with GB/T12406, which is equivalent to the international standard. The standard name of the undated normative reference document IS08459 in the international standard was updated (the new version of this standard was released in May 2009. The 5 parts of the old version were merged into a single standard, and the standard name was changed):? Added references to GB3/T33286 and GB13/T36068. 1. In view of the existing domestic (13/36068. In Table 1, the data elements and the mapping of the GB3/T36068 collection format are added. The data elements in Table 1 of the international standard "6 Abstract Format" are edited. This standard has made the following editorial changes:
In order to distinguish holdings from holding, the "holdings" in the international standard "3.1 Terms and Definitions" is changed to "holdingsinformation";
According to Chinese habits, the "MARC21Holdings" and "OpcnlRlRcquest Transler" in the international standard "3.2 Abbreviations" are deleted. Message\:
- In order to enhance readability, some examples in the international standard are replaced with domestic examples while retaining them: the invalid LRL addresses given in \3.2 Details\ and \7 XMLSchema\ in the international standard are updated; the following paragraphs in 5.3.5 are processed:
- The indentation of data elements in the first column of the table in \6 Abstract Format in the international standard is cancelled: the informative Appendix B\hierarchical structure of the abstract format is added. This standard is proposed and managed by the National Technical Committee for Information and Documentation Standardization (SAC/TC4): The drafting units of this standard are: Peking University, National Library (National Museum of Classic Books). This standard Main drafters: Feng Ying, Zhao Yongchao, Gao Bingjie, Li Shan. -rrKaeerkca-
GB/T40205—2021
The collection information format is designed to meet the needs of information transmission and is applicable to responses to collection information queries of resources collected by repositories, libraries and related institutions. This format is also applicable to cultural institutions that own collections (such as museum collections). The information contained in this format includes library usage, availability, accessibility policies and terms, and access rights: the description of the historical use information of the collection is an optional part of this format.
This standard applies to all types of collections, including physical resources and electronic resources. Resources, and also apply to various resource types, such as printed texts, visual images, audio recordings, videos, electronic media, and single-volume resources published once, or monographs published continuously or in installments.
This format is primarily used to respond to queries. Two main types of queries are identified, namely, availability and historical use, of which the description of availability is the focus of this format. The main purpose of this format is to answer the question "Who has one or more copies of this resource or copies of similar resources? Are these copies currently available? What are the conditions for use?" Although this standard can also be used to describe federated metadata repositories such as collections (such as centralized federated monthly catalogs) and meta-search databases, this is not unstandardized. Focus. This standard is intended to facilitate the exchange of a combination of static and dynamic information. Other formats are already in use for the transfer of static information and for the same purpose, such as MODS, MARC collection data formats, COPAC and ONIX. Most of these formats have rich content, especially in the description of continuing resource collections. Therefore, this standard does not describe in detail new issues of continuing resources or report missing issues. Similarly, this standard does not apply to link resolution databases, although it may contain information about the known location of resources and be sent to the resolver during processing to declare the known location, request a change of location, or provide more information about the known location. Resolvers use this format to pass information to another resolver. How the data is collected and packaged to fit the collection information format is not within the scope of this standard. Data may be scattered in different places, such as joint monthly records, local and monthly records, policy monthly records or warehouses, and multiple standards may be adopted accordingly, including VCIP for local collection descriptions, XACML and LDAP for policy, certification and authorization information, and SRU and Z39.50 protocols for various retrieval and query descriptions.
The collection resources described in this format can correspond to one or more bibliographic resources. This format is used for query responses of bibliographic collections, and the bibliographic resources are known. Therefore, detailed resource description is beyond the scope of this standard. This format can be used in combination with other XML bibliographic resource descriptions, such as MOI)S
-riKaeerKAca-
1Scope
Information and Documentation Collection Information Format
GB/T 40205—2021
This standard defines the collection information format used for query responses. It is applicable to various collection resources including physical resources and electronic resources, and also to various resource types, such as printed texts, visual images, audio recordings, videos, electronic media, as well as single-line resources published once, or monographs published continuously or in parts. Although this standard is designed to define the format of query responses, it does not specify the query and response content that includes retrieval attributes and index definitions (such as SRU, Z39.50 or penSearch protocols). This standard promotes the interaction of static information and dynamic information. How data is collected and organized to be suitable for collection information formats is not within the scope of this standard. Detailed resource descriptions, continuous resource descriptions, and descriptions of missing information for continuous resources are not within the scope of this standard. 2 Normative references
The following documents are essential for the application of this document: For all dated references, only the dated version applies to this document. For all undated references, the latest version (including all revised versions) applies to this document. GB/T12406 Codes for currency and funds (GB/T12406-2008.IS04217:2001.IDT) GB/T33286 China Machine Readable Book Date Format
GB/T36068 China Machine Readable Library Collection Format
ISO8459 Information and Documentation-Bibliographic Data Clement Directory for USC in Data Exchange and CNQuery 3 Terms, Definitions and Abbreviations
3.1 Terms and Definitions
The following terms and definitions apply to this document. For detailed explanation, see Appendix A. 3.1.1
enumeration
An alphanumeric symbol that identifies a component of a multi-part resource, such as a volume or issue. 3.1.2
accessaccess
The ability to open and view electronic resources, including electronic documents and database indexes. 3.1.3
Copycopy
The physical or electronic tangible instance of a resource or collection consisting of one or more items. 3.1.4
holdings inforimationInformation that describes, analyzes, and controls copies associated with a bibliographic resource. 1
rKaeerkAca-
GB/T 40205—2021
setset
A collection of multiple component resources (including multi-volume publications and serials), usually obtained through standing subscription.
piece
A unit of copy that can be transacted, such as a physical part that can be printed out or reserved, or an electronic file that can be downloaded and accessed. 3.1.7
chronology
The publication or release date of a component of a multi-part resource, used to distinguish it from other components of the same resource. 3.1.8
bibliographicresourceA continuous or non-continuous entity that forms the basis of a single resource description. 3.1.9
component
a non-repeating part of a collection, such as a serial or a volume of a multi-volume work. 3.2 Abbreviations
The following abbreviations apply to this document
Abbreviations
COUNTER
DanBib
OpenSearch
British University Journal
Online Resource Usage Statistics
Danish Joint Journal
Interlibrary Loan
German State Public Library Network
Interlibrary Loan
Lightweight Library Access Protocol
Metadata Access Object Description Format
ANSI/NISO Z39.83-1 Circulation Exchange Protocol Part 1: Protocol
Online Information Exchange Protocol for Book Products
Online Public Monthly Catalog Query System, a common term for libraries and library software vendors
A simple format set for sharing search results KaeerkAca-
URL address
http://copac.ac.uk/
http://projcctcounter.org/http://danbib.dk/index.php?docenglish
http:/ /gbv.de/en/
http://tools.ictf.org/html/rfc4510/htip://loc.gov/standards/mods//htip://niso.org/standards/http://editur.org/8/ONIX/htip://.opensearch.org/Specifications/OpenSearch/l.1#OpenSearchdescription_document
Abbreviations
OpenURL| |tt||WorldCat
4 Detailed requirements
ANSI/NIS739.88 Context-sensitive Service Open Linking Framework
SRU search protocol launched by the Library of Congress of the United States French Academic Library Day System
Extensible Access Control Markup Language launched by the OASIS Standards Organization
Extensible Markup Language of W3C
World Library Book Day launched by the Online Computer Library Center OCLC
From discovery to delivery
4.1.1 Overview
GB/T40205—2021
URL address
http://alemc. oclc., org/opcnurl/scrvlet/OAIHancller? verh=-ListSets
http://loc.gov/standards/sru/http://sudoc.abes.fr/LNG=EN/http://xml.covcrpagcs.org/xacml.htmlhtlp://w3.org/TR/2006/RECxml1120060816/
http://worldcat.org/
Today, metadata for resources can be obtained from different sources, and resource discovery has become decentralized. People no longer rely solely on library public access catalogs (OPACs) to discover resources, but also search for resources through Internet search engines, joint repositories, and freely accessible joint catalog public interfaces (such as WorldlCat, Australian Library Resource Sharing System, SUDOC, GIBV, and DanBih). Increasingly, all data is no longer stored in the same place, and resource description information is more decentralized than detailed collection information. A trend is that more and more libraries choose to use comprehensive union catalogs as the main entry point for providing collection resources, and for this reason, resource description information is gradually separated from its management information. Therefore, the discovery-to-delivery service system needs to collect the collection information required for delivery in a seamless way, which matches the metadata of the discovered resources. This requires a standardized format containing collection delivery and access information in the query response: some of this information is dynamic, that is, the information may change each time the collection is delivered. For example, the loan policy may be relatively stable, but the availability status of the collection is variable and needs to be constantly updated. The service policy is not completely immutable and may change with different user groups, so the data about the policy in the query response corresponds to a request. For delivery, the information provided by the collection response about a single copy or group of copies needs to be sufficient and accurate to indicate whether the delivery request can be successfully executed: The collection format can provide this information so that the system can narrow the result set to only those items that are immediately available. Examples of requests for collection availability information include: Is there a copy available on the shelf now? (Single resource) Is there a copy of any version available? (Related bibliographic resource group) Is there an unrestricted copy? (Related bibliographic resource group) Can I reserve the next available copy of any version? What is the current queue status? (Related bibliographic resource group) Group) I (the requester) live far away. Can I borrow or view an electronic copy, or can you help me digitize it, or can you provide me with reference consulting services? As mentioned above, the query part of resource discovery is beyond the scope of this format. The query may or may not contain user attributes that allow the system to determine specific service policies and resource availability information. 3
-rKaeerkca-
GB/T40205—2021
4.1.2 Relationship with existing standards
This format attempts to serve as (G13/T27702201I The goal is to provide a more comprehensive and better defined alternative to the OPAC format defined in ANSI/NISO739.50 and the collection format that has not been widely used in ANSI/NISO739.50. The format defined by the previous NCIP (ANSI/NISO739.83-1) protocol partially meets this need, but can only provide information about a single copy rather than a set of copies of one or more resources. This format is derived from the collection format of ANSI/NIS039.50, with the following modifications: To ensure that the format is fully understood, this format provides detailed element definitions that are as consistent as possible with ISO8459. Use cases are given to provide The complexity of the format was reduced by: · Reducing the seven levels (B1-4, C1-3) to one, clearly indicating the optional and required elements: · Eliminating the differences between the BC levels by providing optional brief information in all cases: · Reducing unnecessary levels in the structure;
. Uncommon elements were removed.
This format allows for some identification and description information of the resource (such as ISBN or other international identifiers, DOI or LRL, etc.) when used as a stand-alone format; this format can also be used as part of other formats.As an extension of MODS.
——Simplify the element name to make it as consistent as possible with ISO8459. The format is used as part of other formats. It has been included in the structure of the "Possible Supplier" element in the OpcnURI request transmission message of VIS.
4.2 Response to Collection Usage Queries
4.2.1 Overview
Increasingly, the system is expected to provide users with some evaluation information required for operating result sets. This information includes: Historical circulation information:
The last time a copy or a set of copies was borrowed or accessed - within a given time range: the number of times a copy or set of copies was circulated or accessed; the last time a physical copy was located (with the increasing use of RFII systems. This will make it easier to obtain and update inventory information).
Collection usage information always helps resource managers make decisions related to resource acquisition, digitization, retirement, renewal and re-shelving. It can also provide information about the effects of using the digitized version in the context of using the physical copy. Examples of requests for collection usage information include: Has this copy or set of copies been used extensively? (If so, I want to purchase a copy for my collection.) Has this copy or set of copies been used recently? (If so, I want to purchase or digitize one: otherwise, forget it, even though it was once popular.)
If this copy or set of copies is not widely used, or has recently been used in another collection resource, I will withdraw my copy to central storage (or remove it);
Can sort the result set by relevance, putting the most popular titles first: - compare my statistics on the use of a certain electronic resource with the use of the same resource in other collection resources; - how did all copies of a work circulate before and after its digitized version became available? A collection's usage information is always dynamic, and the collection information provided each time is different, and needs to be kept up to date to be valuable. It is important to note that there are many differences in the actual collection of historical information on collection use. Many library systems avoid collecting this type of usage history information at the transaction level to avoid potential risks that endanger user privacy. The system can collect this type of information only for specific borrowers (such as those who do not visit the library): This system collects usage information by resource rather than by user or borrower, and this system can hide the user's identity in historical transactions.
Note: This format is becoming increasingly important and is included in this recommendation as an option. 4.2.2 Relationship with existing standards
The commonly used formats at present fail to meet the needs of responding to online queries of physical resources and electronic resources at the same time: It is reported that some standards already exist, such as ANSI/NISO Z39.7 and COUNTER, etc. 5 Format Overview
5.1 Overview
This format mainly focuses on the response requirements of collection delivery and user query combining static information and dynamic information: (The query attributes and inquiries in the actual query request are not explained here.) At the top level. For a resource or resource, there may be multiple collection structures. Create a new \collection instance for each different "institution identifier". The top-level structure of this format is shown in Figure 1. Collection Information
Holdings information
Resource
Resource identifier
Resourceidentifier
5.2 Resource
Resource form
Figure 1 Holding information
Holding
Part detail
Partdetail
"Resource" can be repeated, so that the related collections in "Collection" can be associated with a single monthly resource or a group of monthly resources. The common characteristics of the resources are different. For example, the group of resources may include: a serial publication (representing multiple issues) published within a specified time period or a time period with a specified end time; a work in all its existing forms, such as all translations, all versions; a resource retrieved by a search condition and represented as a search result set. Since this format can be embedded in a format containing book information, "resource" is optional. "Resource" simply identifies a resource or resource group with an identifier or pointer (such as a URL address): its optional information includes "resource form" and "division details"
When "resource" is repeated, it means that there are multiple book resources. These resources are considered to be interchangeable, that is, connected by " or ". The comparison information of all copies associated with all resources is recorded in the "copy summary". 5
-rKaeerKa-
GB/T40205—2021
5.3 Collections
5.3.1 Overview
Figure 2 shows the top level elements of "Collections". "Collections" are mandatory and repeatable: Each independent institution needs its own "Collections_Instance": "Collections_information includes the holding institution and three other information blocks:
"Simple Collections_" or "Structured Collections"; "Policy Summary"; and
Optional "Historical Summary"
Holdings Information
Holdings information
Resource
Institution identifier
Physical location
Physical location(s)
Electronic address
Electronic address(es)
Physical address
Physical address(es)
Simple collection
Holding simple
Holding Structured
Either/or
Figure 3, Figure 6
Holding
Summary policy
Figure 2 Collection
Historical summary
Summary history
Under "Collection", whether "Simple Collection" or "Structured Collection", the element "Institution Identifier" is required. The appropriate collection representation (Simple Collection or Structured Collection) is based on the way the server responds to queries. The reason is that a resource may be collected as a whole unit in one institution and as multiple parts in another institution, or a requester may think that the resource it is requesting is a single part, but it is actually a multi-part resource. Therefore, if you want to indicate that multi-part resources are not equivalent and that copies are not interchangeable under a particular use case, then use "Structured Collection". For the query system, such requirements provide guidance for the scope of the query request. "Simple Collection", "Structured Collection", "Collection Summary" and "Historical Summary" all contain summary information about the copies and items associated with an individual or group of resources, or when this format is part of another format, information about the copies associated with the book resource described in the historical format.
5.3.2 Collection Institution
The data tuple ("Institution Identifier", "Physical Location", "Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or group of resources. The address can be repeated and can be in plain text or from a standard (such as NIP)-rrKaeerKa-This makes it easier to obtain and update inventory information).
Collection usage information always helps resource managers make decisions about acquisition, digitization, retirement, renewal, and restaging of resources. It also provides information on the effectiveness of using digitized versions when physical copies are used. Examples of requests for collection usage information include: Is this copy or group of copies widely used? (If so, I would like to purchase this copy for my collection.) Has this copy or group of copies been used recently? (If so, I want to buy or digitize it: otherwise, forget it, even though it was once popular.)
If the copy or group of copies is not widely used, or has recently been used in other collection resources, I will withdraw my copy to central storage (or remove it);
The result set can be sorted by relevance, with the most popular titles at the top: - compare my statistics on the use of a certain electronic resource with the use of the same resource in other collection resources; - how did all copies of a work circulate before and after its digitized version became available? A library's usage information is always dynamic, and the collection information provided each time is different, so it needs to be kept up to date to be valuable. It should be noted that there are many differences in the actual collection of historical information on collection use. Many library systems avoid collecting this type of usage history information at the transaction level to avoid potential risks that endanger user privacy. The system can collect this type of information only for specific borrowers (such as those who do not visit the library): This system collects usage information by resource rather than by user or borrower, and this system can hide the user's identity in historical transactions.
Note: This format is becoming increasingly important and is included in this recommendation as an option. 4.2.2 Relationship with existing standards
The commonly used formats at present fail to meet the needs of responding to online queries of physical resources and electronic resources at the same time: It is reported that some standards already exist, such as ANSI/NISO Z39.7 and COUNTER, etc. 5 Format Overview
5.1 Overview
This format mainly focuses on the response requirements of collection delivery and user query combining static information and dynamic information: (The query attributes and inquiries in the actual query request are not explained here.) At the top level. For a resource or resource, there may be multiple collection structures. Create a new \collection instance for each different "institution identifier". The top-level structure of this format is shown in Figure 1. Collection Information
Holdings information
Resource
Resource identifier
Resourceidentifier
5.2 Resource
Resource form
Figure 1 Holding information
Holding
Part detail
Partdetail
"Resource" can be repeated, so that the related collections in "Collection" can be associated with a single monthly resource or a group of monthly resources. The common characteristics of the resources are different. For example, the group of resources may include: a serial publication (representing multiple issues) published within a specified time period or a time period with a specified end time; a work in all its existing forms, such as all translations, all versions; a resource retrieved by a search condition and represented as a search result set. Since this format can be embedded in a format containing book information, "resource" is optional. "Resource" simply identifies a resource or resource group with an identifier or pointer (such as a URL address): its optional information includes "resource form" and "division details"
When "resource" is repeated, it means that there are multiple book resources. These resources are considered to be interchangeable, that is, connected by " or ". The comparison information of all copies associated with all resources is recorded in the "copy summary". 5
-rKaeerKa-
GB/T40205—2021
5.3 Collections
5.3.1 Overview
Figure 2 shows the top level elements of "Collections". "Collections" are mandatory and repeatable: Each independent institution needs its own "Collections_Instance": "Collections_information includes the holding institution and three other information blocks:
"Simple Collections_" or "Structured Collections"; "Policy Summary"; and
Optional "Historical Summary"
Holdings Information
Holdings information
Resource
Institution identifier
Physical location
Physical location(s)
Electronic address
Electronic address(es)
Physical address
Physical address(es)
Simple collection
Holding simple
Holding Structured
Either/or
Figure 3, Figure 6
Holding
Summary policy
Figure 2 Collection
Historical summary
Summary history
Under "Collection", whether "Simple Collection" or "Structured Collection", the element "Institution Identifier" is required. The appropriate collection representation (Simple Collection or Structured Collection) is based on the way the server responds to queries. The reason is that a resource may be collected as a whole unit in one institution and as multiple parts in another institution, or a requester may think that the resource it is requesting is a single part, but it is actually a multi-part resource. Therefore, if you want to indicate that multi-part resources are not equivalent and that copies are not interchangeable under a specific user, then use "Structured Collection". For the query system, such requirements provide guidance for the scope of the query request. "Simple Collection", "Structured Collection", "Collection Summary" and "Historical Summary" all contain summary information about the copies and items associated with an individual or group of resources, or when this format is part of another format, information about the copies associated with the book resource described in the historical format.
5.3.2 Collection Institution
The data tuple ("Institution Identifier", "Physical Location", "Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or group of resources. The address can be repeated and can be in plain text or from a standard (such as NIP)-rrKaeerKa-This makes it easier to obtain and update inventory information).
Collection usage information always helps resource managers make decisions about acquisition, digitization, retirement, renewal, and restaging of resources. It also provides information on the effectiveness of using digitized versions when physical copies are used. Examples of requests for collection usage information include: Is this copy or group of copies widely used? (If so, I would like to purchase this copy for my collection.) Has this copy or group of copies been used recently? (If so, I want to buy or digitize it: otherwise, forget it, even though it was once popular.)
If the copy or group of copies is not widely used, or has recently been used in other collection resources, I will withdraw my copy to central storage (or remove it);
The result set can be sorted by relevance, with the most popular titles at the top: - compare my statistics on the use of a certain electronic resource with the use of the same resource in other collection resources; - how did all copies of a work circulate before and after its digitized version became available? A library's usage information is always dynamic, and the collection information provided each time is different, so it needs to be kept up to date to be valuable. It should be noted that there are many differences in the actual collection of historical information on collection use. Many library systems avoid collecting this type of usage history information at the transaction level to avoid potential risks that endanger user privacy. The system can collect this type of information only for specific borrowers (such as those who do not visit the library): This system collects usage information by resource rather than by user or borrower, and this system can hide the user's identity in historical transactions.
Note: This format is becoming increasingly important and is included in this recommendation as an option. 4.2.2 Relationship with existing standards
The commonly used formats at present fail to meet the needs of responding to online queries of physical resources and electronic resources at the same time: It is reported that some standards already exist, such as ANSI/NISO Z39.7 and COUNTER, etc. 5 Format Overview
5.1 Overview
This format mainly focuses on the response requirements of collection delivery and user query combining static information and dynamic information: (The query attributes and inquiries in the actual query request are not explained here.) At the top level. For a resource or resource, there may be multiple collection structures. Create a new \collection instance for each different "institution identifier". The top-level structure of this format is shown in Figure 1. Collection Information
Holdings information
Resource
Resource identifier
Resourceidentifier
5.2 Resource
Resource form
Figure 1 Holding information
Holding
Part detail
Partdetail
"Resource" can be repeated, so that the related collections in "Collection" can be associated with a single monthly resource or a group of monthly resources. The common characteristics of the resources are different. For example, the group of resources may include: a serial publication (representing multiple issues) published within a specified time period or a time period with a specified end time; a work in all its existing forms, such as all translations, all versions; a resource retrieved by a search condition and represented as a search result set. Since this format can be embedded in a format containing book information, "resource" is optional. "Resource" simply identifies a resource or resource group with an identifier or pointer (such as a URL address): its optional information includes "resource form" and "division details"
When "resource" is repeated, it means that there are multiple book resources. These resources are considered to be interchangeable, that is, connected by " or ". The comparison information of all copies associated with all resources is recorded in the "copy summary". 5
-rKaeerKa-
GB/T40205—2021
5.3 Collections
5.3.1 Overview
Figure 2 shows the top level elements of "Collections". "Collections" are mandatory and repeatable: Each independent institution needs its own "Collections_Instance": "Collections_information includes the holding institution and three other information blocks:
"Simple Collections_" or "Structured Collections"; "Policy Summary"; and
Optional "Historical Summary"
Holdings Information
Holdings information
Resource
Institution identifier
Physical location
Physical location(s)
Electronic address
Electronic address(es)
Physical address
Physical address(es)
Simple collection
Holding simple
Holding Structured
Either/or
Figure 3, Figure 6
Holding
Summary policy
Figure 2 Collection
Historical summary
Summary history
Under "Collection", whether "Simple Collection" or "Structured Collection", the element "Institution Identifier" is required. The appropriate collection representation (Simple Collection or Structured Collection) is based on the way the server responds to queries. The reason is that a resource may be collected as a whole unit in one institution and as multiple parts in another institution, or a requester may think that the resource it is requesting is a single part, but it is actually a multi-part resource. Therefore, if you want to indicate that multi-part resources are not equivalent and that copies are not interchangeable under a specific user, then use "Structured Collection". For the query system, such requirements provide guidance for the scope of the query request. "Simple Collection", "Structured Collection", "Collection Summary" and "Historical Summary" all contain summary information about the copies and items associated with an individual or group of resources, or when this format is part of another format, information about the copies associated with the book resource described in the historical format.
5.3.2 Collection Institution
The data tuple ("Institution Identifier", "Physical Location", "Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or group of resources. The address can be repeated and can be in plain text or from a standard (such as NIP)-rrKaeerKa-For a resource or resource collection, there may be multiple holdings structures. A new \collection instance is created for each different "institution identifier". The top-level structure of this format is shown in Figure 1. Holding information
Holdings information
Resource
Resource identifier
Resourceidentifier
5.2 Resource
Resource form
Figure 1 Holding information
Holding
Part detail
Partdetail
"Resource\" can be repeated, so that related holdings in a "collection" can be associated with a single monthly resource or a group of 5-day resources. The common characteristics of the resources are different. For example, the group of resources may include: a series of publications (representing multiple issues) published within a specified time period or a period with a specified end time; all the existing forms of a work, such as all translations, all versions; retrieved by a search condition A resource that is retrieved and represented as a search result set. Since this format can be embedded in a format that contains library information, "resource" is optional. "Resource" simply identifies a resource or resource group with an identifier or pointer (such as a URL address): its optional information includes "resource form" and "division details". When "resource" is repeated, it means that there are multiple library resources. These resources are considered interchangeable, that is, connected by "or", and the comparison information of all copies associated with all resources is recorded in the "copy summary". 5
-rKaeerKa-
GB/T40205—2021
5.3 Collection
5.3.1 Overview
Figure 2 shows the upper layer elements of "collection". "Holdings" is required and repeatable: each independent institution must have its own "Holdings_Instance": "Holdings_information includes the holding institution and three other blocks of information:
"Simple Collections_" or "Structured Collections"; "Policy Summary"; and
Optional "Historical Summary"
Holdings information
Resource
Institution identifier
Physical locationWww.bzxZ.net
Physical location(s)
Electronic address(es)
Physical address(es)
Simple holdings
Holding simple
Structured holdings
Holding Structured
either/or
Figure 3, Figure 6
Holding
Policy summary
Summary policy
Figure 2 Collection
Historical summary
Summary history
Under "Collection", whether "Simple Collection" or "Structured Collection", the element "Institution Identifier" is required. The appropriate collection representation (Simple Collection or Structured Collection) is based on the way the server responds to queries. The reason is that a resource may be collected as a whole unit at one institution and as multiple parts at another institution, or a requester may think that the resource he is requesting is a single part, but it is actually a multi-part resource. Therefore, if you want to indicate that multi-part resources are not equivalent and that copies are not interchangeable under a particular user, then "Structured Collection" is selected. For the query system, such requirements provide guidance for the scope of the query request. "Simple Collection", "Structured Collection", "Collection Summary", and "History Summary" all contain summary information about the copies and files associated with an individual or group of resources, or when this format is part of another format, information about the copies associated with the book resource described in the history format.
5.3.2 Collection Institution
The data tuple ("Institution Identifier"\Physical Location"\"Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or resource group. The address may be repeated and may be in plain text or from a standard (such as NIP) -rrKaeerKa-For a resource or resource collection, there may be multiple holdings structures. A new \collection instance is created for each different "institution identifier". The top-level structure of this format is shown in Figure 1. Holding information
Holdings information
Resource
Resource identifier
Resourceidentifier
5.2 Resource
Resource form
Figure 1 Holding information
Holding
Part detail
Partdetail
"Resource\" can be repeated, so that related holdings in a "collection" can be associated with a single monthly resource or a group of 5-day resources. The common characteristics of the resources are different. For example, the group of resources may include: a series of publications (representing multiple issues) published within a specified time period or a period with a specified end time; all the existing forms of a work, such as all translations, all versions; retrieved by a search condition A resource that is retrieved and represented as a search result set. Since this format can be embedded in a format that contains library information, "resource" is optional. "Resource" simply identifies a resource or resource group with an identifier or pointer (such as a URL address): its optional information includes "resource form" and "division details". When "resource" is repeated, it means that there are multiple library resources. These resources are considered interchangeable, that is, connected by "or", and the comparison information of all copies associated with all resources is recorded in the "copy summary". 5
-rKaeerKa-
GB/T40205—2021
5.3 Collection
5.3.1 Overview
Figure 2 shows the upper layer elements of "collection". "Holdings" is required and repeatable: each independent institution must have its own "Holdings_Instance": "Holdings_information includes the holding institution and three other blocks of information:
"Simple Collections_" or "Structured Collections"; "Policy Summary"; and
Optional "Historical Summary"
Holdings information
Resource
Institution identifier
Physical location
Physical location(s)
Electronic address(es)
Physical address(es)
Simple holdings
Holding simple
Structured holdings
Holding Structured
either/or
Figure 3, Figure 6
Holding
Policy summary
Summary policy
Figure 2 Collection
Historical summary
Summary history
Under "Collection", whether "Simple Collection" or "Structured Collection", the element "Institution Identifier" is required. The appropriate collection representation (Simple Collection or Structured Collection) is based on the way the server responds to queries. The reason is that a resource may be collected as a whole unit at one institution and as multiple parts at another institution, or a requester may think that the resource he is requesting is a single part, but it is actually a multi-part resource. Therefore, if you want to indicate that multi-part resources are not equivalent and that copies are not interchangeable under a particular user, then "Structured Collection" is selected. For the query system, such requirements provide guidance for the scope of the query request. "Simple Collection", "Structured Collection", "Collection Summary", and "History Summary" all contain summary information about the copies and files associated with an individual or group of resources, or when this format is part of another format, information about the copies associated with the book resource described in the history format.
5.3.2 Collection Institution
The data tuple ("Institution Identifier"\Physical Location"\"Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or resource group. The address may be repeated and may be in plain text or from a standard (such as NIP) -rrKaeerKa-2 Collection Institution
The data tuple ("Institution Identifier"\Physical Location"\"Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or resource group. The address may be repeated and may be in plain text or from a standard (such as NIP) -rrKaeerKa-2 Collection Institution
The data tuple ("Institution Identifier"\Physical Location"\"Physical Address" and "Electronic Address") contains the simple identification and address details of the collection institution that holds two or more copies of a resource or resource group. The address may be repeated and may be in plain text or from a standard (such as NIP) -rrKaeerKa-
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.