Who are the Corrections Team and why have they altered an OS/NS date to just NS?
John Treble ( K8RW-V27 ) had (August 2021) a baptism date of (visible text)
8 March 1617/18
I also put a note against that item saying "Reason: From parish register. Note this is 1617/18, i.e. 1617 OS, 1618 NS."
The value in the PR appears to have a year of 1617.
On February 6, 2023, the Corrections team altered the date to "8 March 1618" (visible and standardised value).
I presume that they have decided that the visual and standardised date should be set to New Style. Why?
Even more annoying - they did exactly this in July 2021, amending my 1617/18 date to 1618 - I reverted that change, as I am about to do with this one.
If the corrections team is running software, it needs to understand dual dating (OS / NS). If it's being done manually - why? And why don't they understand OS / NS Dual Dating?
Answers
-
This is the reverted value - as can be seen, it's standardised on 1618 (no problem with that) but uses the dual dating mechanism to emphasise that the value in the PR is 1617.
0 -
I would be very suspicious that "Corrections Team" is just another user who has picked a user name to give himself extra weight and standing when people look at something he has done. I highly doubt that he has anything to do with FamilySearch.
This is mainly based on that fact that FamilySearch almost never changes user entered display data. One the rare occasions when they have run some some background routine, it has only affected the linked standardized data. For example, a couple of years ago there was an update on standardized place name that caused a lot of user entered places names to lose their link to a standard and users had to go back and do some re-linking.
You may want to report as abuse the use of an inappropriate user name.
4 -
How intriguing @Gordon Collett - that's certainly not an angle I'd thought of. I will have a further look at their changes and certainly raise the issue with FS Support one way or another.
0 -
Hi have some issues with changes made by the "Corrections Team". Whoever this is, they have done a couple of bad merges in family lines, and they have made changes without noting any reason or explanation. I am in the middle of fixing their errors.
2 -
Hi have some issues with changes made by the "Corrections Team".
I think I just - after several previous attempts - managed to report the name as probable abuse - but since the response flashed up and disappeared so very quickly, I have little confidence it worked!
0 -
I reported the username to be reviewed a bit ago. I will let you know if I hear anything.
4 -
I believe I remember you saying you had done that. My suggestion was that there should be a limited choice in what FamilySearch users are allowed to pick for their usernames. There are a number of these "authoritive" sounding names that appear to relate to ordinary users, rather than to authorised, FamilySearch projects. Just the other day, a Community member came here using a name ending in "Project", this obviously being a personally chosen username. I'm sure FamilySearch has a way of blocking names that include obscenities, so should be able to block certain names - especially if they end in "Team" or "Project"!
2 -
As @Gordon Collett suspected, "Corrections Team" is just an ordinary user. FS Data Admin responded to my report of an abuse of the system and stated that
Despite the official sounding contact name, we can confirm that ‘Corrections Team’ is NOT a part of FamilySearch and is a single contributor. We will be contacting him regarding his Contact ID, pointing out that our terms and conditions state that contributors must not impersonate other users, and request that he change the name.
As I expected, the FS Data Admin declined to get involved in whether the conversion (or even perversion) of the labelled OS/NS date to an unlabelled NS date was correct (that's fine by me, it's not what they're there for). Since I've reverted them to labelled OS/NS display dates, I will await the next time a user alters my dates similarly.
2
