|
|
In 2020 an HTML replacement for the Flash-based GEDCOM review mechanism was developed and deployed. This page is for recording issues that have been noticed about the new implementation.
Bigger issues
- Not all "Early" people being flagged and excluded
- In one file, on the order of 5% of the pre-1750 people that should have been flagged as "Early" and "Excluded" were not.
- Links between a Person and a Family do nothing
- There are links on Person pages which normally would go to the related family page, and on Family pages which would go to referenced Person page. These do nothing now. (In the earlier Flash implementation, they worked.) Without these links it is difficult to navigate to the correct Family or Person for evaluation of the data and relationship (especially needed since these gedcom person pages do not give the basic details for the families like normal WeRelate Person pages do). Since there is no working link, one has to do something like copy the person's surname, switch to family tab, do a search with that name, choose a candidate instance of the name in a family, guessing the spouse's name (if several marriages, or there are several of the searched name. (This works only for the person's own marriages, not for finding a parent since only parents of families are indexed). To facilitate this searching, it can help to open another window into the same Gedcom so that the original Person page can be seen along with a window showing families under the family tab. To navigate to a parent marriage, one may have to first get a person's temporary gedcom identifier from the "gedcomkey" component in the URL the browser displays when hovering over Edit for the person, then on the Families tab examine the candidate marriages one by one and for a matching name in a family display hover over that name and see if the identifier displayed in the popup tooltip has the correct identifier for the person. All such attempted navigation is a substantial inconvenience compared to having the link work.
- Result order when sorted by date column
- Sorting by Birth or Death on the People tab, or by Marriage on the Family tab, does results in a fairly unusable sequence of entries. If a typical user notices it is not right, the sequence would not be obvious. This illustrates aspects of the sequence:
- 1796
- ABT 1739
- ABT MAR 09 1864
- Apr 01 1852
- Apr 1781
- BEF Mar 23 1902
- DEC 01 1736
- Jun 30 1795
- living
- Mar 01 1799
- Sep 30 1911
- It seems to be a case insensitive string order. The only usable characteristic seems to be that the 'living' entries collate together, as do the blank entries. A string order sort on a form rearranged to lead with year, like "1864 ABT, MAR 09", would be an improvement if full date ordering is too much work.
Smaller issues
- Result order when sorted by severity level
- On the Warnings tab, sorting by severity Level orders the groups by alpha sequence: alert, duplicate, error, warning rather than severity sequence (duplicate, error, warning, alert_). (It is a nice touch that the line coloring indicates severity.)
- Rows per page setting
- Most of the tabs use a table of entries with a choice of "Rows per page" of 5, 10, 15, or All. The default is 10, and the setting is reset to 10 each time one switches to the tab. The setting of 10 is a fair compromise between the amount viewable and the amount of time it takes to gather the data for "All", which is noticeable to substantial for large Gedcoms. When you are switching to a tab, it may be to search for a specific entry by entering a name in the search field, or it may be to examine the whole set of entries. In the former case, the default number of 10 is good, as you don't want to wait out the time it takes to fetch all the entries. In the latter case, you want access to all, whatever the cost (which is noticeable only in larger files). When repeatedly switching between tabs (people and families most often) and where the "All" setting is desired, it is a small but repeated burden to have to scroll the upper part of the window to expose the control, click the control, and select the "All" option. (To avoid this, I have resorted to opening the same gedcom in a second window, but I suspect this runs the danger of undisplayed or lost updates of the gedcom because of multiple independent sessions.) Perhaps it would be good if a gedcom-review session could keep all the tabs' rows-settings for the length of the session instead of resetting them to 10 rows each time a tab is switched to.
- "Uploader review: undefined"
- On the Special:Gedcoms page reached via the Admin dropdown menu, listing pending Gedcoms, a Gedcom that the reviewer has returned to the user for correction is listed with the status "Uploader review: undefined" now. I don't recall what the Flash version displayed.
|
|
