RDA 4.8 - Revision history

Casey: Added 340 $p

2021-08-25T16:53:16Z

Added 340 $p

Casey: Edited 34X "fields used" descriptions

2020-02-26T18:23:01Z

Edited 34X "fields used" descriptions

Casey: /* 340 field: Physical Medium */

2017-08-08T15:48:38Z

‎340 field: Physical Medium

Casey: /* 348 field: Format of Notated Music */

2017-07-27T17:49:35Z

‎348 field: Format of Notated Music

Casey: /* RDA 4.8: 34X Field Additions */

2017-07-27T16:53:42Z

‎RDA 4.8: 34X Field Additions

Casey: /* RDA 4.8: 34X Field Additions */

2017-07-27T16:00:28Z

‎RDA 4.8: 34X Field Additions

Casey: /* 340 field: Physical Medium */

2017-07-27T15:59:24Z

‎340 field: Physical Medium

Casey: /* 340 field: Physical Medium */

2017-07-27T15:59:03Z

‎340 field: Physical Medium

Casey: /* 348 field: Format of Notated Music */

2017-07-27T15:53:50Z

‎348 field: Format of Notated Music

Casey: /* 347 field: Digital File Characteristics */

2017-07-27T15:50:34Z

‎347 field: Digital File Characteristics

@@ Line 42: / Line 42: @@
 |-
 | o || Polarity ([http://access.rdatoolkit.org/rdachp3_rda3-4604.html RDA 3.14]) || 007, 300ab, 533 ||
 |}

@@ Line 4: / Line 4: @@
 Backstage can attempt to add the 34X fields outlined below to your bibliographic records.  We utilize the MARC fields mapped to the RDA elements as well as other fields and subfields if they exist within the MARC record, these bibliographic fields are used alone or in combinations.  Where the RDA instructions include a vocabulary, we use those terms but when particular terms are not specified, we search for the most common terms in usage.  In most cases, it may be possible to have terms added to our parameters.  With the exception of the 348 field, we do not add a $2 to the end of the field because not all subfields use terms from an RDA vocabulary.
 DISCLAIMER: There are several obstacles to adding these fields by automated means. Differences in practice and changes in definitions of fields and codes over time have resulted in inconsistencies in application. A machine cannot always tell when this happens, like when an 007 field is for a different format rather than the main resource. Sometimes there is additional information in the record that the system can use, but there are times when fields may be added erroneously. We ''do not'' try to add these fields when there are multiple instances of information bearing fields like the 007 and 300. We will not always be able to add all subfields, but we will attempt to add as many as possible.
@@ Line 13: / Line 15: @@
 ! '''340 subfield''' !! '''Description''' !! '''Fields used''' !! '''Backstage notes'''
 |-
-| a || Material base and configuration ([http://access.rdatoolkit.org/rdachp3_rda3-3755.html RDA 3.6]) || 007, 338 || We only add material base
+| a || Material base and configuration ([http://access.rdatoolkit.org/rdachp3_rda3-3755.html RDA 3.6]) || 007, 300ab, 338 || We only add material base
 |-
-| b || Dimensions ([http://access.rdatoolkit.org/rdachp3_rda3-3150.html RDA 3.5]) || 007, 300a and 300c, 337, 533 ||
+| b || Dimensions ([http://access.rdatoolkit.org/rdachp3_rda3-3150.html RDA 3.5]) || 007, 300ac, 337, 533 ||
 |-
 | c || Materials applied to surface ([http://access.rdatoolkit.org/rdachp3_rda3-3882.html RDA 3.7]) || 007, 300b ||
 |-
-| d || Information recording technique ([http://access.rdatoolkit.org/rdachp3_rda3-4017.html RDA 3.9]) || 007, 300b, 533 ||
+| d || Information recording technique ([http://access.rdatoolkit.org/rdachp3_rda3-4017.html RDA 3.9]) || 007, 300bc, 344c,345b ||
 |-
 | e || Support ([http://access.rdatoolkit.org/rdachp3_rda3-3961.html RDA 3.8]) || 007 ||
 |-
-| f || Production rate/ratio ([http://access.rdatoolkit.org/rdachp3_rda3-4637.html RDA 3.15], [http://access.rdatoolkit.org/rdachp3_rda3-4786.html RDA 3.16.4], [http://access.rdatoolkit.org/rdachp3_rda3-4969.html RDA 3.17.3]) || 007, 344c, 345b, 300b ||
+| f || Production rate/ratio ([http://access.rdatoolkit.org/rdachp3_rda3-4637.html RDA 3.15], [http://access.rdatoolkit.org/rdachp3_rda3-4786.html RDA 3.16.4], [http://access.rdatoolkit.org/rdachp3_rda3-4969.html RDA 3.17.3]) || 007, 300b, 344c, 345b ||
 |-
-| g || Color content || ''n/a'' || Not currently mapped to RDA
+| g || Color content || 007, 300b || Not currently mapped to RDA
 |-
 | h || Location within medium || ''n/a'' || Not currently mapped to RDA
 |-
-| i || Technical specifications of medium ([http://access.rdatoolkit.org/rdachp3_rda3-5468.html RDA 3.20]) || 300a, 538 ||
+| i || Technical specifications of medium ([http://access.rdatoolkit.org/rdachp3_rda3-5468.html RDA 3.20]) || 538 ||
 |-
 | j || Generation ([http://access.rdatoolkit.org/rdachp3_rda3-4165.html RDA 3.10]) || 007 ||
@@ Line 37: / Line 39: @@
 | m || Book format ([http://access.rdatoolkit.org/rdachp3_rda3-4434.html RDA 3.12]) || 300c ||
 |-
-| n || Font size ([http://access.rdatoolkit.org/rdachp3_rda3-4570.html RDA 3.13]) || Leader/05, 300a and 300b ||
+| n || Font size ([http://access.rdatoolkit.org/rdachp3_rda3-4570.html RDA 3.13]) || Leader/06, 300ab ||
 |-
-| o || Polarity ([http://access.rdatoolkit.org/rdachp3_rda3-4604.html RDA 3.14]) || 007, 533 ||
+| o || Polarity ([http://access.rdatoolkit.org/rdachp3_rda3-4604.html RDA 3.14]) || 007, 300ab, 533 ||
 |}
@@ Line 47: / Line 49: @@
 ! '''344 subfield''' !! '''Description''' !! '''Fields used'''
 |-
-| a || Type of recording ([http://access.rdatoolkit.org/rdachp3_rda3-4742.html RDA 3.16.2]) || Leader/06, 007, 300b, 538
+| a || Type of recording ([http://access.rdatoolkit.org/rdachp3_rda3-4742.html RDA 3.16.2]) || Leader/06, 007, 300abc, 336a, 338a, 538
 |-
-| b || Recording medium ([http://access.rdatoolkit.org/rdachp3_rda3-4771.html RDA 3.16.3]) || Leader/06, 007, 300b, 538
+| b || Recording medium ([http://access.rdatoolkit.org/rdachp3_rda3-4771.html RDA 3.16.3]) || Leader/06, 007, 300abc, 338a, 538
 |-
-| c || Playing speed ([http://access.rdatoolkit.org/rdachp3_rda3-4786.html RDA 3.16.4]) || 007, 300b, 340f
+| c || Playing speed ([http://access.rdatoolkit.org/rdachp3_rda3-4786.html RDA 3.16.4]) || 007, 300abc, 338a, 340f
 |-
 | d || Groove characteristic ([http://access.rdatoolkit.org/rdachp3_rda3-4834.html RDA 3.16.5]) || 007, 300b, 538
@@ Line 57: / Line 59: @@
 | e || Track configuration ([http://access.rdatoolkit.org/rdachp3_rda3-4869.html RDA 3.16.6]) || 300b, 538
 |-
-| f || Tape configuration ([http://access.rdatoolkit.org/rdachp3_rda3-4892.html RDA 3.16.7]) || 007, 300b, 538
+| f || Tape configuration ([http://access.rdatoolkit.org/rdachp3_rda3-4892.html RDA 3.16.7]) || 007, 300ab, 538
 |-
 | g || Configuration of playback channel ([http://access.rdatoolkit.org/rdachp3_rda3-4908.html RDA 3.16.8]) || 007, 300b, 538
@@ Line 71: / Line 73: @@
 | a || Presentation format ([http://access.rdatoolkit.org/rdachp3_rda3-5001.html RDA 3.17.2]) || 007, 300b, 538
 |-
-| b || Projection speed ([http://access.rdatoolkit.org/rdachp3_rda3-5027.html RDA 3.17.3]) || 300b, 340f, 538
+| b || Projection speed ([http://access.rdatoolkit.org/rdachp3_rda3-5027.html RDA 3.17.3]) || 300bc, 340f, 538
 |}
@@ Line 81: / Line 83: @@
 | a || Video format ([http://access.rdatoolkit.org/rdachp3_rda3-5098.html RDA 3.18.2]) || 007, 300b, 538
 |-
-| b || Broadcast standard ([http://access.rdatoolkit.org/rdachp3_rda3-5137.html RDA 3.18.3]) || 300b, 538
+| b || Broadcast standard ([http://access.rdatoolkit.org/rdachp3_rda3-5137.html RDA 3.18.3]) || 300c, 538
 |}

@@ Line 15: / Line 15: @@
 | a || Material base and configuration ([http://access.rdatoolkit.org/rdachp3_rda3-3755.html RDA 3.6]) || 007, 338 || We only add material base
 |-
-| b || Dimensions ([http://access.rdatoolkit.org/rdachp3_rda3-3150.html RDA 3.5]) || 007, 300a and 300c, 337, 553 ||
+| b || Dimensions ([http://access.rdatoolkit.org/rdachp3_rda3-3150.html RDA 3.5]) || 007, 300a and 300c, 337, 533 ||
 |-
 | c || Materials applied to surface ([http://access.rdatoolkit.org/rdachp3_rda3-3882.html RDA 3.7]) || 007, 300b ||

@@ Line 111: / Line 111: @@
 | b || Format of notated music code || ''No attempt to code''
 |}
-*''While we use the list of terms at RDA 7.20.1.3, it is not always possible to determine which RDA term is correct since there is not always a direct correspondence between terms and codes used in BIB records and RDA vocabulary. When the field cannot be added, it will be reported. When the field is added, it will be followed by $2rda''
+*''While we use the list of terms at RDA 7.20.1.3, it is not always possible to determine which RDA term is correct since there is not always a direct correlation between terms and codes used in BIB records and RDA vocabulary. When the field cannot be added, it will be reported. When the field is added, it will be followed by $2rda''
 ==Default==

← Older revision		Revision as of 16:53, 27 July 2017
Line 3:		Line 3:


−	Backstage can attempt to add the 34X fields ~~listed~~ below to your bibliographic records. We utilize the MARC fields mapped to the RDA elements as well as other fields and subfields if they exist within the MARC record~~. The fields used to add each 34X field are listed below;~~ these bibliographic fields are used alone or in combinations. Where the RDA instructions include a vocabulary, we use those terms~~. When~~ particular terms are not specified, we search for the most common terms in usage. In most cases, it may be possible to have terms added to our parameters. With the exception of the 348 field, we do not add a $2 to the end of the field because not all subfields use terms from an RDA vocabulary.	+	Backstage can attempt to add the 34X fields outlined below to your bibliographic records. We utilize the MARC fields mapped to the RDA elements as well as other fields and subfields if they exist within the MARC record, these bibliographic fields are used alone or in combinations. Where the RDA instructions include a vocabulary, we use those terms but when particular terms are not specified, we search for the most common terms in usage. In most cases, it may be possible to have terms added to our parameters. With the exception of the 348 field, we do not add a $2 to the end of the field because not all subfields use terms from an RDA vocabulary.

	DISCLAIMER: There are several obstacles to adding these fields by automated means. Differences in practice and changes in definitions of fields and codes over time have resulted in inconsistencies in application. A machine cannot always tell when this happens, like when an 007 field is for a different format rather than the main resource. Sometimes there is additional information in the record that the system can use, but there are times when fields may be added erroneously. We ''do not'' try to add these fields when there are multiple instances of information bearing fields like the 007 and 300. We will not always be able to add all subfields, but we will attempt to add as many as possible.		DISCLAIMER: There are several obstacles to adding these fields by automated means. Differences in practice and changes in definitions of fields and codes over time have resulted in inconsistencies in application. A machine cannot always tell when this happens, like when an 007 field is for a different format rather than the main resource. Sometimes there is additional information in the record that the system can use, but there are times when fields may be added erroneously. We ''do not'' try to add these fields when there are multiple instances of information bearing fields like the 007 and 300. We will not always be able to add all subfields, but we will attempt to add as many as possible.

← Older revision		Revision as of 16:00, 27 July 2017
Line 5:		Line 5:
	Backstage can attempt to add the 34X fields listed below to your bibliographic records. We utilize the MARC fields mapped to the RDA elements as well as other fields and subfields if they exist within the MARC record. The fields used to add each 34X field are listed below; these bibliographic fields are used alone or in combinations. Where the RDA instructions include a vocabulary, we use those terms. When particular terms are not specified, we search for the most common terms in usage. In most cases, it may be possible to have terms added to our parameters. With the exception of the 348 field, we do not add a $2 to the end of the field because not all subfields use terms from an RDA vocabulary.		Backstage can attempt to add the 34X fields listed below to your bibliographic records. We utilize the MARC fields mapped to the RDA elements as well as other fields and subfields if they exist within the MARC record. The fields used to add each 34X field are listed below; these bibliographic fields are used alone or in combinations. Where the RDA instructions include a vocabulary, we use those terms. When particular terms are not specified, we search for the most common terms in usage. In most cases, it may be possible to have terms added to our parameters. With the exception of the 348 field, we do not add a $2 to the end of the field because not all subfields use terms from an RDA vocabulary.

−	DISCLAIMER: There are several obstacles to adding these fields by automated means. Differences in practice and changes in definitions of fields and codes over time have resulted in inconsistencies in application. A machine cannot always tell when this happens, like when an 007 field is for a different format rather than the main resource. Sometimes there is additional information in the record that the system can use, but there are times when fields may be added erroneously. We ''do not'' try to add these fields when there are multiple instances of information bearing fields like the 007 and 300. We will not always be able to add all subfields, but we will attempt to ad as many as possible.	+	DISCLAIMER: There are several obstacles to adding these fields by automated means. Differences in practice and changes in definitions of fields and codes over time have resulted in inconsistencies in application. A machine cannot always tell when this happens, like when an 007 field is for a different format rather than the main resource. Sometimes there is additional information in the record that the system can use, but there are times when fields may be added erroneously. We ''do not'' try to add these fields when there are multiple instances of information bearing fields like the 007 and 300. We will not always be able to add all subfields, but we will attempt to add as many as possible.

@@ Line 19: / Line 19: @@
 | c || Materials applied to surface ([http://access.rdatoolkit.org/rdachp3_rda3-3882.html RDA 3.7]) || 007, 300b ||
 |-
-| d || Information recording technique ([[http://access.rdatoolkit.org/rdachp3_rda3-4017.html|RDA 3.9]]) || 007, 300b, 533 ||
+| d || Information recording technique ([[http://access.rdatoolkit.org/rdachp3_rda3-4017.html RDA 3.9]]) || 007, 300b, 533 ||
 |-
 | e || Support ([http://access.rdatoolkit.org/rdachp3_rda3-3961.html RDA 3.8]) || 007 ||

@@ Line 107: / Line 107: @@
 ! 348 subfield !! Description !! Fields used
 |-
-| a || Format of notated music term (RDA 7.20.1.3)* || Leader/06 (must be 'c' or 'd'), 008, 300a, 650, 655
+| a || Format of notated music term ([http://access.rdatoolkit.org/rdachp7_rda7-1533.html RDA 7.20.1.3])* || Leader/06 (must be 'c' or 'd'), 008, 300a, 650, 655
 |-
 | b || Format of notated music code || ''No attempt to code''

@@ Line 89: / Line 89: @@
 ! '''347 subfield''' !! '''Description''' !! '''Fields used'''
 |-
-| a || File type (RDA 3.19.2) || Leader/06, 007, 008, 256, 300a and 300b, 336, 337, 352q, 516, 538
+| a || File type ([http://access.rdatoolkit.org/rdachp3_rda3-5230.html RDA 3.19.2]) || Leader/06, 007, 008, 256, 300a and 300b, 336, 337, 352q, 516, 538
 |-
-| b || Encoding format (RDA 3.19.3) || 007, 256, 300b, 352q, 516, 538
+| b || Encoding format ([http://access.rdatoolkit.org/rdachp3_rda3-5264.html RDA 3.19.3]) || 007, 256, 300b, 352q, 516, 538
 |-
-| c || File size (RDA 3.19.4) || 256, 300a or 300b
+| c || File size ([http://access.rdatoolkit.org/rdachp3_rda3-5314.html RDA 3.19.4]) || 256, 300a or 300b
 |-
-| d || Resolution (RDA 3.19.5) || 538
+| d || Resolution ([http://access.rdatoolkit.org/rdachp3_rda3-10189.html RDA 3.19.5]) || 538
 |-
-| e || Regional encoding (RDA 3.19.6) || 538
+| e || Regional encoding ([http://access.rdatoolkit.org/rdachp3_rda3-5302.html RDA 3.19.6]) || 538
 |-
-| f || Encoded bitrate (RDA 3.19.7) || 300, 538
+| f || Encoded bitrate ([http://access.rdatoolkit.org/rdachp3_rda3-5332.html RDA 3.19.7]) || 300, 538
 |}
 ===348 field: Format of Notated Music===