Differences

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

--- resources:cerl_thesaurus:editing:newinterface [2018/03/27 12:27] – [4.4 Using the YAML Editor] jahnke
+++ resources:cerl_thesaurus:editing:newinterface [2018/06/14 15:23] – [3.2 Headings and Names] jahnke
@@ Line 175: / Line 175: @@
 .8 External Resources
-.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.
+{{ :resources:cerl_thesaurus:editing:coords2.png?300|Classic style coordinates}}
+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. 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.
 .10 Other Formats
@@ Line 220: / Line 230: @@
 ==== 4.3 Using the CT Internal Format Editor ====
+{{ :resources:cerl_thesaurus:editing:editing6.png?300|FLC Editor}}
+The "Internal Format" editor allows to edit the CERL Thesaurus data in the same Unimarc based field format as it has been the case in the old Avanti environment. It's called "Internal Format" since this has been the internal format in the old system and is still used for a ingesting and update, although the actual internal format is quite different now (JSON).
+The format description and input conventions can be found [[format|here]]. Different from the old WinADH client, the Internal Format editor is used for editing records only - for merging duplicate records there is now a different editor available (see below).
+In comparison to the form based editor, the display of the information stored in a record is much more compact and easiert to grasp at first glance. For experienced editors typing field numbers and subfields is probably faster than handling a complex form.
+There is also no input validation implemented yet, any invalid fields, indicator positions or subfields will be silently ignored when the data is converted to JSON, so make sure to check from the record's full display if all information has been entered correctly.
 ==== 4.4 Using the YAML Editor ====
@@ Line 233: / Line 254: @@
 If you are trying to save your record, but nothing happens, you have most likely made an error with the YAML-Syntax. Since the editor does not yet return a validation report, you may try copying the record into an external validator (e.g. [[http://www.yamllint.com/]]) to see what went wrong.
 ==== 4.5 Deduplicating Records ====
+{{ :resources:cerl_thesaurus:editing:dedup1.png?300|Deduplication}}
+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.
+//**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.
+Please note that by unchecking a record, you say that it is definitely not a duplicate to the first (white) one and by clicking the checkmark you say it definitely is. There is no "I’m not sure option" as there was in WinADH – if you are not sure then it is not a duplicate.((If you are not sure about that either, hit cancel and try another record))
+Please make also sure to check the biographical dates (340), activity notes (350, 300) and titles (291) to decide if records refer to the same entity or not. If that is not sufficient, try also to look at the source systems the records come from and see to what titles they are linked (this is not always possible, of course). Always bear in mind, that you are most likely the person who is saying the final word about these records being duplicates or not. Once you hit save, the records will no longer show up, when someone checks for duplicates. If you say two records are not duplicates they will probably never again be considered for merging and if you say two records are, they will probably never be separated if they are not.
+Once you've made your decisions and unchecked or checked the non‐duplicates and duplicates, you could change the order of the fields. This might be desirable for the following fields 200, 210, 212, 215, 340, 350. If any of these fields is repeated within a record, the first occurrence is used for generating the short display in the search result set. To change the order of the fields, you can drag and drop a field with the mouse upwards or downwards into a new position.
+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.//

resources/cerl_thesaurus/editing/newinterface.txt · Last modified: 2023/12/11 15:13 by jahnke