 

Home | Resources | Services | Hosting | Publications | Collaboration | Joining CERL | About CERL |

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revision Both sides next revision
resources:cerl_thesaurus:editing:format:290 [2012/08/31 09:57]
127.0.0.1 external edit
resources:cerl_thesaurus:editing:format:290 [2020/01/23 08:12]
jahnke [Application of Content Designators]
Line 1: Line 1:
-====== 290 Source referred to in a record ======+====== 290 Source referred to in a record ​(O;​NR) ​======
    
-\\ 
-<block tableinvisible>​ 
-|  **Mandatory:​** | no  | 
-|  **Repeatable:​**| yes | 
-|  **Related fields:** |[[321|321]]| 
-</​block>​ 
-\\ 
- 
- 
  
 ==== Field Definition and Scope ==== ==== Field Definition and Scope ====
Line 25: Line 16:
 **Indicator 1:** undefined (blank) **Indicator 1:** undefined (blank)
  
-**Indicator 2: Specifies the type of input:** +**Indicator 2:** undefined (blank) ​
- +
-  * **0**  Field has been input or corrected by cataloguer and cannot be overwritten in automated updating processes +
- +
-  * **1**  Field has been input by automated addition; review by cataloguer may be necessary+
  
 === Subfields === === Subfields ===
-** $6 Source File Reference (O;NR) **\\ 
-see the [[numerical subfields|description of numerical subfields]]. 
-\\ 
-\\ 
 **$a Reference work cited in abbreviated form (M;R)**\\ **$a Reference work cited in abbreviated form (M;R)**\\
 This abbreviation should be matched by more extensive information in a 321 record This abbreviation should be matched by more extensive information in a 321 record
Line 44: Line 27:
  
 ==== Input Conventions ==== ==== Input Conventions ====
-There should be only one field 290 per original record repeating the subfield $a as often as necessary.+There should be only one field 290 per <del>original</​del> ​record repeating the subfield $a as often as necessary.
  
 When a reference work is cited for a specific variant name it should be given in one of the 4XX fields in subfield $s. Sources specifically relating to the relationship of the given entity to another one should be given in the subfields $s of the 5XX fields accordingly. When a reference work is cited for a specific variant name it should be given in one of the 4XX fields in subfield $s. Sources specifically relating to the relationship of the given entity to another one should be given in the subfields $s of the 5XX fields accordingly.
  
 When records from CERL members are used for the CT they may not have sources in separate fields (such as [[290|290]] and [[291|291]]). Examples for such a case are found in the ESTC records, where reference works and short titles of works, in which the name of a 2XX is occuring, are all filed in the same field. In this case the CT record will have all this information mapped to field [[290|290]]. When records from CERL members are used for the CT they may not have sources in separate fields (such as [[290|290]] and [[291|291]]). Examples for such a case are found in the ESTC records, where reference works and short titles of works, in which the name of a 2XX is occuring, are all filed in the same field. In this case the CT record will have all this information mapped to field [[290|290]].
 +
 +Repeated fields 290 will be merged into one during ingest.
  
 ==== Mapping ==== ==== Mapping ====
Line 55: Line 40:
 ==== Examples ==== ==== Examples ====
  
-  - 290 #1$aDiercke$aGeo-Duden$aUrso$aSWD +  - 290 ##$aDiercke$aGeo-Duden$aUrso$aSWD 
-  - 290 #1$aBSDNAL$aGK55$aDNB$aNUC$aFES vol.7 p.499-500+  - 290 ##$aBSDNAL$aGK55$aDNB$aNUC$aFES vol.7 p.499-500 
 + 
 + 
 +==== Internal Representation ==== 
 +<code javascript>​ 
 +{"​data":​ {"​foundIn":​ ["​Source ($a)"​]}} 
 +</​code>​ 
 + 
 +==== Change History ==== 
 +  * //​18.07.2017//:​ After migration of the CT into its new environment,​ repeated fields are no longer supported and will be merged into one during ingest. 
 +  * //​18.07.2017//:​ Indicator position 2 changed to undefined, since as the field is no longer repeatable, it must always accept sources from new records. 
 +  * //​18.07.2017//:​ Subfield $6 will no longer be supported, once the CT has been migrated into its new environment.
  
 resources/cerl_thesaurus/editing/format/290.txt · Last modified: 2020/01/23 08:14 by jahnke

 

 

Recent changes RSS feed Valid XHTML 1.0 Driven by DokuWiki
https://cerl.org/resources/cerl_thesaurus/editing/format/290?do=diff&rev2%5B0%5D=1346399852&rev2%5B1%5D=1579763539&difftype=sidebyside
cerl.org
crawl=CC-MAIN-2020-34
26114
application/http; msgtype=response
sha1:L7KSCEFWE4E6U2WA2Y7WLYKHLEHSU6RL
<urn:uuid:b02bb782-b30c-4752-be3e-84297c97f27d>
2020-08-12T19:04:37Z
195.37.138.14
application/xhtml+xml
sha1:SI4XQUBQ5ZUGA5PMDCP56H2PS2WJRTRW
<urn:uuid:3981f63b-9260-4761-8f01-6e090d19dd93>
https://cerl.org/resources/cerl_thesaurus/editing/format/290?do=diff&rev2%5B0%5D=1346399852&rev2%5B1%5D=1579763539&difftype=sidebyside
response
<urn:uuid:dc8f59ef-6c50-486e-9dab-4db914553c04>
isPartOf: CC-MAIN-2020-34
publisher: Common Crawl
description: Wide crawl of the web for August 2020
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-230.ec2.internal
software: Apache Nutch 1.17 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.2-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/