Results page: show unknown if DOB/age blank #604
Comments
|
I suggest that 'not recorded' (or similar) would be more accurate and honest than 'unknown' in most instances. |
|
sure, better then leaving it blank. |
|
Can we show 'Not applicable' for DOB, as well as for Mother's Maiden Name, Spouse's Surname? Blank cells in the table look unclear, either there is no data, or there is an error, or the table is not completed. @nurifreembd @AlOneill @richardofsussex |
|
'Applicable' requires a higher reading age (in English) than 'recorded'. We should opt for the simplest way to express that the data was not collected at that time. 'Unknown' is bad because it is not true. Blank is bad because it looks as if something has gone wrong. |
|
Another option is to leave the cell blank and maybe above the table
consider a line something like ' we have most data on record but there may
be blank records where registration details were unrecorded at the time of
registration.
…On Wed, Dec 4, 2024 at 9:54 AM AlOneill ***@***.***> wrote:
'Applicable' requires a higher reading age (in English) than 'recorded'.
We should opt for the simplest way to express that the data was not
collected at that time. 'Unknown' is bad because it is not true. Blank is
bad because it looks as if something has gone wrong.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72B3UFTP7VLZIUXPO6IT2D3GNLAVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWG4ZTQOBUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
How about 'No data' ? It seems quite simple and clear. |
|
works.
…On Wed, Dec 4, 2024 at 10:39 AM KristinaGadzhieva ***@***.***> wrote:
How about 'No data' ? It seems quite simple and clear.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72B4FBJKB4QZVCK46LJD2D3LVTAVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWHEYTINBTGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@KristinaGadzhieva Yes! Perfect. |
|
@nurifreebmd Too long and complicated. Also, very likely to be missed by a screen reader user who goes straight to the table. |
|
@AlOneill presumably your comment relates to Nuri's suggestion? I was going to suggest 'No data' myself. |
|
To clarify, I think 'No data' is (almost) perfect. (Almost because a user might ask, "and why not?" — my literal brain is on overdrive!! ) |
|
I think that can be addressed in the help, where we can explain that the GRO have changed the information they record in the index over the years, and we can only offer the data actually recorded for any given event. |
|
Sure, we can provide clarification on the Help page. So I think we all agreed on 'No data'. |
|
My personal view is unknown works too as the charity is not responsible for
what is or not registered at the time of registration. we do not maintain
the data.
…On Wed, Dec 4, 2024 at 11:16 AM Richard Light ***@***.***> wrote:
@AlOneill <https://github.com/AlOneill> presumably your comment relates
to Nuri's suggestion? I was going to suggest 'No data' myself.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72B6JQBCMKKU2TQEYZHT2D3QADAVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJXGAZDCNRRGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
OK, now implemented: |
|
Thank you very much everyone! |
|
Those are cells which are not relevant to that particular event type, and so can never contain data (e.g. Mother's Maiden Name and Age at Death for a marriage record). We could put 'No data' in those as well, but personally I think it would make the listing look cluttered. |
|
Yes, it would be cluttered. We can leave as it is for now and wait for user feedback. |
|
All,
My personal view is we go back to drawing room. I do not agree with
inconsistent approach. One other option is for all unrecorded details is
show - and a line above the table somewhere stating - denotes no record
detail found or no record found or no data found
Or have NDF and somewhere above the table state NDF no data found
It looks cluttered and inconsistent with no data and other cells left blank
…On Wednesday, December 4, 2024, KristinaGadzhieva ***@***.***> wrote:
Yes, it would be cluttered. We can leave as it is for now and wait for
user feedback.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72B7YNPE5IB6GRTZUYU32D5GW7AVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGMZDGMRVHA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
We can show ND in each cell and make a note below the table for users explaining the meaning. |
|
Add dashes in currently blank cells. |
|
@AlOneill do you agree with the proposed approach:
|
|
Implemented: |
|
Looks good Richard. Looks presentable with the dash.
…On Tue, Dec 10, 2024 at 8:22 PM Richard Light ***@***.***> wrote:
Implemented:
image.png (view on web)
<https://github.com/user-attachments/assets/c175b9c9-c15b-4bd3-b5d2-76be37f7e9bc>
@Vino-S <https://github.com/Vino-S> please push to test3.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72BZ7IVK63VU7B3FK67D2E5EO7AVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZSG44TAOBQGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Now on test3 - thanks @Vino-S. (BTW, I also changed e.g. 'BIRTHS' to 'Birth' as discussed. Bonus!) |
|
I think it would be worth adding an explanation of the difference between a dash and 'No data' below the table for users. |
|
Yes, I agree.
…On Wed, Dec 11, 2024 at 4:52 PM KristinaGadzhieva ***@***.***> wrote:
I think it would be worth adding an explanation of the difference between
a dash and 'No data' below the table for users.
—
Reply to this email directly, view it on GitHub
<#604 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BDP72B5EWQ6MCNSETHASKKT2FBUVZAVCNFSM6AAAAABSRGNQ3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZWGU2DAMRVHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
If you are going to explain anything about the table, please add a heading to that explanation so that a screen reader user can discover it (without having to read the whole page). |
|
@AlOneill @richardofsussex @nurifreembd |
|
I must say, that starts to sound like [part of] a Help page. Maybe that is where such detailed advice should live? Personally I quite like the FreeReg results page layout, which has a brief summary of what you looked for and what we found, followed by a table of results. (You'll notice there is also a brief summary there of how to sort the results table.) |
|
Commented in #609: I have added information about 'No data' and dash (‘-’) cases to the Help MVP doc. |
Results page: Age at Death/Date of Birth - currently shows blank cell. Suggestion is to show 'unknown' if no record of DOB/age.
The text was updated successfully, but these errors were encountered: