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

You are here:: Home » CERL Resources » CERL Thesaurus » Editing the CERL Thesaurus » Guide to Editing the CERL Thesaurus 

Editing the CT Format Description Printers' Records Indexing Principles CERL Thesaurus

News|Contact|Index|

 

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 [2018/03/27 15:48] – [4.5 Deduplicating Records] jahnkeresources:cerl_thesaurus:editing:newinterface [2018/06/14 15:30] – [3.2 Headings and Names] jahnke
Line 160: Line 160:
  
 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. 
 +
 +For a detailed description of the various fields and the input convention applying see:
 + 
 +  * [[:resources:cerl_thesaurus:editing:format:200]]
 +  * [[:resources:cerl_thesaurus:editing:format:210]]
 +  * [[:resources:cerl_thesaurus:editing:format:212]]
 +  * [[:resources:cerl_thesaurus:editing:format:215]] 
 +  * [[:resources:cerl_thesaurus:editing:format:400]]
 +  * [[:resources:cerl_thesaurus:editing:format:410]] 
 +  * [[:resources:cerl_thesaurus:editing:format:412]]
 +  * [[:resources:cerl_thesaurus:editing:format:415]]
  
  
Line 175: Line 188:
 3.8 External Resources 3.8 External Resources
  
-3.9 Geographic Coordinates+==== 3.9 Geographic Coordinates ==== 
 + 
 +{{ :resources:cerl_thesaurus:editing:coords1.png?300|Decimal Coordinates}} 
 + 
 +Geographic Coordinates should be given for place name records (cnl) only. Please note that the format of the coordinates varies according to the editing form you are using. In the form-based editor and the YAML editor coordinates are given in decimal form as a floating point number without a degree sign (°). Use positive numbers for north and east and negative numbers for soutch and west. 
 + 
 + 
 + 
 +In the CT internal format editor, the coordinates are given in degrees, minutes and seconds preceded by a letter indicating the hemisphere, see [[:resources:cerl_thesaurus:editing:format:123|123 Coded Data Field: Latitude and Longitude]] for details.  
 + 
 +{{ :resources:cerl_thesaurus:editing:coords2.png?300|Classic style coordinates}} 
 + 
 +Please note that the syntax of field 123 assumes a place is designated by a square-like shape through defining the outermost latitudes and longitudes. In the CERL Thesaurus, the coordinates of a place are that of a single point in or near the center of place - so both coordinates must be recorded twice here. 
 + 
  
 3.10 Other Formats 3.10 Other Formats
Line 247: Line 274:
  
 The editor to merge duplicate records is only shown among the options for choosing and editing client if the record holds an indication of possible duplicates (''#831 #1'' or ''meta.possibleMatch''). The approach the new interface takes to deduplication is slightly different from the one used within the old WinADH client: Instead of showing two records next to each other, the new client shows how the final record would look like, if all possible duplicates were merged together. This is supposed to make comparison between records easier, since all fields that are supposed to hold the same information are shown in the same spot, color coded by the source record it has been derived from. The editor to merge duplicate records is only shown among the options for choosing and editing client if the record holds an indication of possible duplicates (''#831 #1'' or ''meta.possibleMatch''). The approach the new interface takes to deduplication is slightly different from the one used within the old WinADH client: Instead of showing two records next to each other, the new client shows how the final record would look like, if all possible duplicates were merged together. This is supposed to make comparison between records easier, since all fields that are supposed to hold the same information are shown in the same spot, color coded by the source record it has been derived from.
 +
 +To find potential duplicates, search for ''dedup:'' and the record type, e.g. ''dedup:cnp'' for persons. You may combine it with something useful to get smaller resultsets, for example: ''external_id:gnd AND dedup:cnp'' to limit the set to records from the GND file.
  
 The duplicate candidate records are shown in the right column. The first (white) one is the record you started with; sinc this is the record the other are finally merged into, you cannot deselect it from deduplication. The duplicate candidate records are shown in the right column. The first (white) one is the record you started with; sinc this is the record the other are finally merged into, you cannot deselect it from deduplication.
 +
 +//**Please note:** If there are many duplicate candidates it might be easier to check the records one by one. To do that, you start with “Hide all” (which turns all candidates grey) and then re‐activate the first candidate and see if it is a duplicate or not. If it’s not, uncheck it and go to the next. If it is, you could click the other button next to the check mark (the one with the three stripes on it) to switch the record’s colour to white before you proceed with the next record. So you’d know that everything that’s white is checked and “ok” and the amount of different colours is a little less confusing.//
  
 Un‐select the records that are not duplicates to the first one by clicking the green checkmark in the box that represents the record in the right column. The box will turn grey and the fields that belong to that record will no longer be visible in the left column. As long as the box in the right column has a colour (other than grey, that is) the record will be merged into the first one, once you hit save. Un‐select the records that are not duplicates to the first one by clicking the green checkmark in the box that represents the record in the right column. The box will turn grey and the fields that belong to that record will no longer be visible in the left column. As long as the box in the right column has a colour (other than grey, that is) the record will be merged into the first one, once you hit save.
Line 260: Line 291:
 When done, hit //Save//. The first record will receive all the fields of the active (coloured) records, which in turn will get a redirect to the first record's record id. //If you have merge some records and later discover that they are actually not duplicates, inform us accordingly at [[convert@gbv.de]], so that we can restore the original situation. Please note that we can only return to the state before merging - any editing that might have been done on the merged record will be lost.// When done, hit //Save//. The first record will receive all the fields of the active (coloured) records, which in turn will get a redirect to the first record's record id. //If you have merge some records and later discover that they are actually not duplicates, inform us accordingly at [[convert@gbv.de]], so that we can restore the original situation. Please note that we can only return to the state before merging - any editing that might have been done on the merged record will be lost.//
  
-If there are many duplicate candidates it might be easier to check the records one by one. To do that, you start with “Hide all” (which turns all candidates grey) and then re‐activate the first candidate and see if it is a duplicate or not. If it’s not, uncheck it and go to the next. If it is, you could click the other button next to the check mark (the one with the three stripes on it) to switch the record’s colour to white before you proceed with the next record. So you’d know that everything that’s white is checked and “ok” and the amount of different colours is a little less confusing. 
  
  
  
  
 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