Doorgaan naar de website
OCLC Support

883 Machine-Generated Metadata Provenance (R)

Find the field definition and scope, indicators, subfield codes, and guidelines for applying content designations for field 883.

Indicators and subfield codes

First Indicator

Method of Machine Assignment

blank         No information provided/not applicable

0         Fully machine-generated

1         Partially machine-generated

Second Indicator

Undefined

blank         Undefined

Subfield Codes

‡a       Generation process (NR)

‡c       Confidence value (NR)

‡d       Generation date (NR)

‡q       Generation agency (NR)

‡u       Uniform Resource Identifier (NR)

‡w      Bibliographic record control number (R)

‡x       Validity end date (NR)

‡0       Authority record control number or standard number (R)

‡1       Real World Object URI (R)

‡8       Field link and sequence number (R)

 

Field definition and scope

This field provides information about the provenance of metadata in data fields in the record, with special provision for machine generation. Field 883 contains a link to the field to which it pertains. Intended for use with data fields that have been fully or partially machine-generated (i.e., generated by some named process other than intellectual creation).

Guidelines for applying content designations

Indicators

First Indicator - Method of machine assignment

blank - No information provided/not applicable

0 - Fully machine-generated

Data in linked field was fully machine-generated.

1 - Partially machine-generated

Data in linked field was partially machine-generated.

Second Indicator - Undefined

blank - Undefined

Subfields

‡a - Generation process

Subfield ‡a contains data that identifies the process used to produce the data contained in the linked field. The subfield may contain a process name or some other description.

082  0  4    ‡8 1/p ‡a 394.12 ‡2 22 ‡q OCoLC-D

883  1         ǂ8 1\p ǂa autodewey ǂd 20120407 ǂq DLC ǂc 1
[AutoDewey is a software program which takes advantage of those places where the Library of Congress Classification (LCC) and DDC are similar enough to facilitate mapping from LCC to DDC]

082      0      0    ‡8 1/p ‡a 829/.3 ‡2 23

082      1            ‡8 1/p ‡a autodewey ‡d 20120407 ‡q DLC ‡c 1
[AutoDewey is a software program which takes advantage of those places where the Library of Congress Classification (LCC) and DDC are similar enough to facilitate mapping from LCC to DDC]

‡c - Confidence value

Subfield ‡c contains a description of the confidence of the agency using the process/activity identified in subfield ‡a to generate the linked field. The subfield contains a floating point value between 0 and 1. Either a comma or a point may be used as a decimal marker. Code 0 means no confidence and 1 means full confidence.

082  0  4    ‡8 1/p ‡a 004 ‡2 22/ger ‡q NO-OsNB

883  0        ‡8 1/p ‡a deweyclassifierv0.1 ‡d 20120101 ‡x 20141231 ‡q NO-OsNB ‡c 0, 75 ‡0 (DE-101)040268942

‡d - Generation date

Subfield ‡d contains the date on which the linked field was generated. This also serves as the beginning of the period validity. Date is recorded in the format yyyymmdd in accordance with ISO 8601, Representation of Dates and Times (http://www.iso.org/iso/iso8601). The mm and dd positions contain zeroes when the data is unknown.

‡q - Generation agency

Subfield ‡q contains the MARC organization code of the institution using the process/activity to convert the data. Code from: MARC Code List for Organizations.

‡u - Uniform Resource Identifier

Subfield ‡u contains the Uniform Resource Identifier (URI), for example a URL or URN, which identifies the process used to convert the data contained in the MARC record.

The URI can lead to a textual or structured description of the process, or the URL that was used to generate the record's content can be provided directly, i.e., a URL invoking a web service or conveying an API call.

‡w - Bibliographic record control number

Subfield ‡8 contains data that identifies linked fields and may also propose a sequence for the linked fields. Subfield ‡8 may be repeated to link a field to more than one other group of fields. The structure and syntax for the field link and sequence number subfield is: ‡8 . \

The linking number is the first data element in the subfield and required if the subfield is used. It is a variable-length whole number that occurs in subfield ‡8 in all fields that are to be linked. Fields with the same linking number are considered linked. A linking number of "0" (zero) is not used in this field.

The sequence number is separated from the linking number by a period "." and may be optional. It is a variable-length whole number that may be used to indicate the relative order for display of the linked fields (lower sequence numbers displaying before higher ones).

The field link type is separated from preceding data by a reverse slash "\". It is a code indicating the reason for the link and it follows the link number or sequence number if present. The following one-character field link type code has been defined for use in subfield ‡8 in OCLC local holdings records: a – Action

Code a is used in a record to link one or more fields with another field to which the processing or reference actions relate. This code is typically used only when there is more than one 5XX that relates to another 5XX field.

‡x - Validity end date

Subfield ‡x contains the date representing expected end of period of validity for the data in the linked field. Date is recorded in the format yyyymmdd in accordance with ISO 8601, Representation of Dates and Times (http://www.iso.org/iso/iso8601). The mm and dd positions contain zeroes when the data is unknown.

082  0  4    ‡8 1/p ‡a 004 ‡2 22/ger ‡q DE-101

883  0        ‡8 1/p ‡a parallelrecordcopy ‡d 20120101 ‡x 20141231 ‡q NO-OsNB

‡0 - Authority record control number or standard number

Subfield ‡0 contains the system control number of the related authority record, or a standard identifier such as an International Standard Name Identifier (ISNI). The control number or identifier is preceded by the appropriate MARC Organization code (for a related authority record) or the Standard Identifier source code (for a standard identifier scheme), enclosed in parentheses. In the latter case, the parenthetical "(uri)" is redundant and should not be included if the identifier is given in the form of a Web retrieval protocol, e.g., HTTP URI, which is self-identifying.

See MARC Code List for Organizations (https://www.loc.gov/cds/products/product.php?productID=59) for a listing of organization codes and Standard Identifier Source Codes (https://www.loc.gov/standards/sourcelist/standard-identifier.html) for code systems for standard identifiers. Subfield ‡0 is repeatable for different control numbers or identifiers. Subfield ‡0 is to be used for recording URIs which represent objects in RDF triple statements.

‡1 - Real World Object URI

Subfield ‡1 contains a URI that identifies a description of an entity, sometimes referred to as a Thing, a Real World Object, or RWO, whether actual or conceptual. When dereferenced, the URI points to a description of that entity. A URI that identifies a name or label for an entity is contained in subfield ‡0.

‡8 - Field link and sequence number

Subfield ‡8 identifies linked fields and may also propose a sequence for the linked fields. Subfield ‡8 may be repeated to link a field to more than one other group of fields. You are responsible for creating and maintaining links in subfield ‡8. The system does not create or maintain these links. Subfield ‡8 generally appears at the beginning of the field.