Data Provenance Code List
List identifier: dataprov
Code List
This list was originally developed for use in the Data provenance subfields in the MARC 21 Format for Bibliographic Data and the MARC 21 Format for Authority Data, described in Appendix J (Bibliographic format) and Appendix H (Authority format).
Data Provenance Category Codes
- bcp47
- Data provenance element BCP 47 tag
BCP47 use in MARC: BCP47 is a reference to a specification that encodes human languages and scripts in contemporary data structures, especially those designed for the web. The specification is published by the Internet Engineering Task Force (IETF). BCP47 components are separated by hyphens and are identifiable by length and position in the overall code. The first two or three characters are the language: "ko" or "en" or "sgn". The 2-character ISO 639 codes (i.e., ISO 639 Set 1) are preferred, but the 3-character ISO 639 codes (i.e., ISO 639 Set 2, ISO 639 Set 3, or ISO 639 Set 5) may be used. If the second component (after a hyphen) is four characters, it is a script (i.e., ISO 15924) reference: "ko-hang". If the script can be inferred from the language, it is not included since it is considered unnecessary information. For example, the "latn" in "en-latn" is unnecessary because for English, Latin script is assumed. language/script codes will be included in Data Provenance subfields of 880 fields and in other fields as deemed appropriate by a cataloger. The BCP47 codes will reference the entire MARC field. The bcp47 code will identify a string with both non-Latin and Latin text as being entirely non-Latin. For example: 880 1 $6100-01/$1 $a김 동찬$c(Cartographer)$e cartographer $7(bcp47)ko. BCP47 codes will be all lowercase.
- dpeaa
- Data provenance element author agent
- dpecou
- Data provenance element context of use
- dpeloe
- Data provenance element language of expression
- dpenmw
- Data provenance element note on metadata work
- dpermw
- Data provenance element related manifestation of work
- dpertow
- Data provenance element related timespan of work
- dpes
- Data provenance element script
- dpesc
- Data provenance element source consulted
- dpets
- Data provenance element transliteration scheme
Data Provenance Relationship Codes
- dpsfa
- Data provenance relates to $a
- dpsfb
- Data provenance relates to $b
- dpsfc
- Data provenance relates to $c
- dpsfd
- Data provenance relates to $d
- dpsfe
- Data provenance relates to $e
- dpsff
- Data provenance relates to $f
- dpsfg
- Data provenance relates to $g
- dpsfh
- Data provenance relates to $h
- dpsfi
- Data provenance relates to $i
- dpsfj
- Data provenance relates to $j
- dpsfk
- Data provenance relates to $k
- dpsfl
- Data provenance relates to $l
- dpsfm
- Data provenance relates to $m
- dpsfn
- Data provenance relates to $n
- dpsfo
- Data provenance relates to $o
- dpsfp
- Data provenance relates to $p
- dpsfq
- Data provenance relates to $q
- dpsfr
- Data provenance relates to $r
- dpsfs
- Data provenance relates to $s
- dpsft
- Data provenance relates to $t
- dpsfu
- Data provenance relates to $u
- dpsfv
- Data provenance relates to $v
- dpsfw
- Data provenance relates to $w
- dpsfx
- Data provenance relates to $x
- dpsfy
- Data provenance relates to $y
- dpsfz
- Data provenance relates to $z
- dpsf0
- Data provenance relates to $0
- dpsf1
- Data provenance relates to $1
- dpsf2
- Data provenance relates to $2
- dpsf3
- Data provenance relates to $3
- dpsf4
- Data provenance relates to $4
- dpsf5
- Data provenance relates to $5
- dpsf6
- Data provenance relates to $6
- dpsf7
- Data provenance relates to $7
- dpsf8
- Data provenance relates to $8
List Maintenance
The Library of Congress is the maintenance agency for this value list. Questions and requests for information should be sent to: Network Development and MARC Standards Office, Library of Congress, 101 Independence Avenue, S.E., Washington, DC 20540-4402; Fax: +1-202-707-0115; Internet: [email protected]. Requests for additions to the value list should include an explanation and justification.
