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

Both sides previous revisionPrevious revision
Next revision
Previous revision
Next revisionBoth sides next revision
resources:cerl_thesaurus:editing:newinterface [2020/01/24 13:13] – [3.5 Related Places] jahnkeresources:cerl_thesaurus:editing:newinterface [2020/01/27 12:08] – [3.9 Geographic Coordinates] jahnke
Line 162: Line 162:
 The CERL Thesaurus records the preferred name forms of an entity as they are used in CERL Member libraries. Heading forms differ according to the language used for cataloguing and the cataloguing rules applied. The CERL Thesaurus does not declare one of these name forms as authoritative, but lists them alphabetically indicating the institutions that use that particular form. Thus, there is no "CERL form" for a heading. The name form given as a headline in a record's full display is the first heading recorded within that record, its prominent position does not imply any indication of preference for that form. The CERL Thesaurus records the preferred name forms of an entity as they are used in CERL Member libraries. Heading forms differ according to the language used for cataloguing and the cataloguing rules applied. The CERL Thesaurus does not declare one of these name forms as authoritative, but lists them alphabetically indicating the institutions that use that particular form. Thus, there is no "CERL form" for a heading. The name form given as a headline in a record's full display is the first heading recorded within that record, its prominent position does not imply any indication of preference for that form.
  
-Variant name forms do now have an additional code, indicating the type of the name form (**$0** in **4xx** fields). This code is mandatory. If in doubt, use ''varn'' as a default+Variant name forms do now have an additional code, indicating the type of the name form (**$0** in **4xx** fields). This code is mandatory and defaults to ''varn'' ("variant name")
  
 For a detailed description of the various fields and the input convention applying see: For a detailed description of the various fields and the input convention applying see:
Line 183: Line 183:
 There is no prescribed syntax or a controlled list of abbreviations for reference works in the "Found In" field. There is no prescribed syntax or a controlled list of abbreviations for reference works in the "Found In" field.
  
-The CERL Thesaurus is neither a bibliographic nor a provenance database, so editions and copies should be recorded only as sources of evidence. Complete lists of works printed, written or owned by an entity should be provided elsewhere (e.g. HPB, HPB-Item, MEI etc) and a link should be made from the Thesaurus record instead.+The CERL Thesaurus is neither a bibliographic database nor a provenance database, so editions and copies are recorded only as sources of evidence. Complete lists of works printed, written or owned by an entity can be provided elsewhere (e.g. HPB, HPB-Item, MEI etc) and a link can be made from the Thesaurus record instead.
  
 For a detailed description of the available fields and the input convention applying see: For a detailed description of the available fields and the input convention applying see:
Line 191: Line 191:
   * [[:resources:cerl_thesaurus:editing:format:292]]   * [[:resources:cerl_thesaurus:editing:format:292]]
  
-Sources that apply to a specific piece of information only (such as bibliographic data or an individual variant name form) should be recorded in that particular field.+Sources that apply to a specific piece of information only (such as bibliographic data or an individual variant name form) are recorded in that particular field. 
 + 
 +==== 3.4 Notes and Biographical Data ==== 
 + 
 +There are four categories of (public) notes in a CERL Thesaurus record:  
 + 
 +//**General notes**// can hold any information on the described entity that does not fit in any of the other categories. 
 + 
 +//**Biographical data**// and //**dates of activity**// should always hold the dates mentioned in the note also in machine readable form in a separate subfield, which can then be used for sorting records chronologically or filtering for records from a certain time period. Biographical data can also be given as  dates of existence of a corporate entity. "Founding dates" or similar of places are not given here, though. 
 + 
 +In the form based editor biographical data and date of activities are two separate fields, while in the (Unimarc-based) "CT Internal Format" the same field is used with a different value at the first indicator position. 
 + 
 +Any other information about a person's, printer's or corporate body's academic title / degree, domain of artistic expression, intellectual responsibility for a publication, language(s), profession/occupation, religious affiliation, title(s) of nobility, traded items or any other activity is given as an //**activity note**//. In an activity note it is possible to use controlled vocabulary. When controlled Vocabulary is used, the corresponding URI is given as well, or, in case there is no URI, the source vocabulary is indicated.  
 + 
 +Any aspect of the entity's description relating to geography in any way or form is given as a //**geographic note**//. A geographic note can also hold terms from a controlled vocabulary including their URI or a country code. Place records often indicate the country/province/region the place belongs to nowadays as a means of identification or disambiguation. 
 + 
 +Unless controlled vocabulary or codes are used, all note fields are free-text fields, which means that the language of the note is always indicated. Note fields also provide a subfield to record the source the information is taken from. 
 + 
 +For a detailed description of the available fields and the input convention applying see: 
 +  
 +  * [[:resources:cerl_thesaurus:editing:format:300]] 
 +  * [[:resources:cerl_thesaurus:editing:format:340]] 
 +  * [[:resources:cerl_thesaurus:editing:format:350]] 
 +  * [[:resources:cerl_thesaurus:editing:format:356]]
  
-3.4 Notes and Biographical Data 
  
 ==== 3.5 Related Places ==== ==== 3.5 Related Places ====
Line 208: Line 230:
   * [[:resources:cerl_thesaurus:editing:format:515]]   * [[:resources:cerl_thesaurus:editing:format:515]]
  
-3.6 Other Related Entities (Persons, Printers, Corporate Bodies)+==== 3.6 Other Related Entities (Persons, Printers, Corporate Bodies) ====
  
 +CERL Thesaurus records for persons, printers and corporate bodies can link to other records for any of these entity types to indicate family relationships, predecessors und successors in business, persons being members of a corporate body etc. The type of relationship is always indicated with the link to the target record.
 +
 +Records for places can only link to other places, not to persons, printers or corporate bodies (while any of these can link to a place record). 
 +
 +For a detailed description of the available fields and the input convention applying see:
 + 
 +  * [[:resources:cerl_thesaurus:editing:format:500]]
 +  * [[:resources:cerl_thesaurus:editing:format:510]]
 +  * [[:resources:cerl_thesaurus:editing:format:512]]
 +
 +In the Unimarc-based //CT Internal Format// three different fields are used, depending on the type of entity the link points to. In the form based editor there is only one (complex) data entry field for links to persons, printers and corporate bodies. Here the type of the target entity is selected from the drop down list.
 ==== 3.7 Signs, Marks, Devices ==== ==== 3.7 Signs, Marks, Devices ====
  
Line 240: Line 273:
  
  
-3.10 Other Formats+==== 3.10 Other Formats ==== 
 + 
 +Internally, CERL Thesaurus records are stored as JSON objects. From the web interface, the (actual) internal format of a record can be retrieved in JSON or YAML. For compatiblity reasons the interface also supports the old "CT Internal Format" based on Unimarc Authorities as a working format. Data can be entered and edited equally in either the old or the new format (see below). 
 + 
 +Additionally CT data can be retrieved in RDF as well (RDF/XML, Turtle or JSON-LD) to use it in Linked Data applications. There are, however, a few pieces of information that are currently not translated into RDF, so RDF description sets are marginally less complete than records in the (JSON-based) internal format or the old (Unimarc-based) "CT Internal Format"
  
 ===== 4 Editing the CERL Thesaurus ===== ===== 4 Editing the CERL Thesaurus =====
 resources/cerl_thesaurus/editing/newinterface.txt · Last modified: 2023/12/11 15:13 by jahnke

 

 

Recent changes RSS feed Valid XHTML 1.0 Driven by DokuWiki