Family Tree - Same Verbage - Two different meanings
LegacyUser
✭✭✭✭
gasmodels said: There are two different situations that prevent ordinance completion that have been confused. One is "Not Available" and this occurs when there is an imposed situation by data administration. There are several reasons why this can be imposed and nominal user cannot resolve this issue without support intervention. (sometimes it can be incorrectly applied).
The second situation is "Needs more Information". This is the case where sufficient information is not provided to uniquely identify the individual and therefore the system is advising the user that more information is required. An example might be a record with just a name and a birth year. That is insufficient so the ordinances would show "Needs more Information". The user could add a location and maybe a relationship and then ordinances would be allowed.
In principle these two situations are very different and the process required to resolve is relatively straightforward. In the first situation the user must contact support and in the second situation adding information can resolve the issue.
Now lets look at the situation in Family Tree. The image below is from a record which needs additional information is required.
The records indicates at the top that more information is required and there is detailed information as to what needs to be added to allow the record to qualify for ordinances.
Next is an image from a locked record - I choose a famous person President Harry Truman as an example. This is one of the categories of persons where no changes are allowed.
Everything is reasonable except for the nice message at the top which is noted in the red highlight --- it very clearly says "Needs more Information". This can be very confusing to the average user when they find a record of this type. No matter how much they attempt to correct the record, add information or modify the record (if they can) the situation will stay the same. The record is "Not Available" and the "needs more information" message is incorrect. While this is a minor issue in the overall scheme of things it is very confusing to users and can cause a significant waste of time attempting to resolve the issue. It seems a simple change of wording would resolve the issue.
The second situation is "Needs more Information". This is the case where sufficient information is not provided to uniquely identify the individual and therefore the system is advising the user that more information is required. An example might be a record with just a name and a birth year. That is insufficient so the ordinances would show "Needs more Information". The user could add a location and maybe a relationship and then ordinances would be allowed.
In principle these two situations are very different and the process required to resolve is relatively straightforward. In the first situation the user must contact support and in the second situation adding information can resolve the issue.
Now lets look at the situation in Family Tree. The image below is from a record which needs additional information is required.
The records indicates at the top that more information is required and there is detailed information as to what needs to be added to allow the record to qualify for ordinances.
Next is an image from a locked record - I choose a famous person President Harry Truman as an example. This is one of the categories of persons where no changes are allowed.
Everything is reasonable except for the nice message at the top which is noted in the red highlight --- it very clearly says "Needs more Information". This can be very confusing to the average user when they find a record of this type. No matter how much they attempt to correct the record, add information or modify the record (if they can) the situation will stay the same. The record is "Not Available" and the "needs more information" message is incorrect. While this is a minor issue in the overall scheme of things it is very confusing to users and can cause a significant waste of time attempting to resolve the issue. It seems a simple change of wording would resolve the issue.
Tagged:
0