Write help documentation for the new fields.

[Captainkirkdawson]

Priority (2 3 6 3) 14

We need to document the new fields for the transcriber.

Needs #1371

[Captainkirkdawson]

@AlOneill seems like I am running into a problem with the page being too long to store in the mysql database. May have to split the page into sub pages.

[AlOneill]

No worries — separate sub-pages are fine — at least to start with.

I am thinking that there will be some sense in treating fields that are essentially the same, like all the _surname fields, in one entry. But let me think about that some more. When I suggested something similar (aggregating field descriptions) a couple of years ago, no-one seemed too keen, but given the sheer number of fields now available, and the increased duplication of information, a more elegant solution seems sensible.

[Sherlock21]

I am inclined to agree with Kirk. If the fields behave the same way as each other, then no point in yards of text being repeated. The user has to be credited with some mental dexterity after all.

[Captainkirkdawson]

@Sherlock21 it was a suggestion from @AlOneill not me.

I had definitely been inclined to follow that suggestion for the common fields.

However I seem to have run into a size limitation that may force a different solution.

[Captainkirkdawson]

A first draft of the extended baptism fields document
https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-baptism-fields-draft#baptisms

[AlOneill]

@Captainkirkdawson Thanks.

To make for more pleasant reading, the markup needs a bit of an overhaul — I will need to do this offline, in a proper editor. When I take a copy of the page, probably in the next few days, I will leave a note at the top warning that any edits made in Refinery will be overwritten when I paste in the offline edits. If there is no such warning present, then you may edit freely. (Please let me know if that strategy looks ill-thought-out in any way.)

[Captainkirkdawson]

@AlOneill have added your styling to the pages

[AlOneill]

@Captainkirkdawson Thanks. Still a couple of issues — will solve offline.

[Captainkirkdawson]

Have completed marriages

[Captainkirkdawson]

Have completed burials

[Captainkirkdawson]

@SteveBiggs @edickens @Sherlock21

The 4 new flexible csv format and the extended field pages are drafted.

@AlOneill is editing styling and formatting

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/flexible-csv-format-draft

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-baptism-fields-draft

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-marriage-fields-draft

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-burial-fields-draft

[AlOneill]

Question: are the 2 systems, flexible and fixed, going to be used alongside each other, or does flexible replace fixed?

[Captainkirkdawson]

@AlOneill they can and will coexist. BUT once a batch uses flexible it cannot go back

[AlOneill]

@Captainkirkdawson Thanks.

Next question: am puzzled by _status field — if _condition field is for marital status, what kind of status goes in the _status field? Standing wrt 'church' ?? (No examples are given in baptisms.)

[Captainkirkdawson]

@PatReynolds @SteveBiggs
Alison raises a great question. The reason I did not enter an example was I did not understand what the field was all about. Perhaps you can clarify.

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-marriage-fields-draft

[SteveBiggs]

Sorry I don't understand the question. Which field are you asking about? Is this in marriages or baptisms?

[AlOneill]

@SteveBiggs I was asking about the baptism fields: person_condition and person_status

If person_condition is for recording marital status, then what goes in person_status?

https://test3.freereg.org.uk/cms/information-for-transcribers/entering-data-from-registers/extended-baptism-fields-draft#bapQ and following field

[SteveBiggs]

Person status - e.g. Illegitimate, Twin, etc.

[PatReynolds]

@smrr723 @Captainkirkdawson any idea why the download links are failing? If no idea / not fixable, I suggest they are uploaded to the F U G website.

[smrr723]

Searching for "The SHA parameter you gave is incorrect" shows it's a known issue, but I don't see any single, simple solution.

@Captainkirkdawson markevans/dragonfly#387 (comment) seems to be the clearest solution I've found but from what I can see in our Gemfile, we should have the highest working version of the json gem anyway.

[Captainkirkdawson]

@smrr723 As you likely have perhaps perceived I have not the foggiest idea of how to keep the SHA from changing. My solution would be to eliminate it totally and put a straight link to the file and ignore any complaints from dragonfly

[smrr723]

@Captainkirkdawson that's probably the best solution I think.

[Captainkirkdawson]

SHA gets changed by a server restart. Testing a solution

[Captainkirkdawson]

@AlOneill Problem has been fixed by adding a dragonfly secret code to resources. Have sanitized the initialization to use a mongo_config constant rather than hard code. SHA survives a server restart now.

[SteveBiggs]

Can we deploy the help info to production now?

[AlOneill]

There is an outstanding query about the Notes field — link is to the Baptisms page, but also applies to other record types.

See: https://test3.freereg.org.uk/cms/information-for-transcribers/flexible-csv-format-draft/extended-baptism-fields-draft#bapAN

[SteveBiggs]

I would say the answer is no. Leave that comment out as it could cause confusion.

[AlOneill]

@Captainkirkdawson Thank you — looks good.

@SteveBiggs Thank you. Will begin clean-up of new pages.

[AlOneill]

@Captainkirkdawson The 4 new pages are now ready for syncing, as are the other pages in the (Transcriber) Help section that required menu updates.

Please note that the edit required by #1226 has been done as part of the above.

[Captainkirkdawson]

@PatReynolds @richpomfret @lemon-ukgen

Rather than my doing a one off would it not be far better to use this as an opportunity to have you ans lemon test the syncing task envisaged as part of #1371

[SteveBiggs]

When will the sync task be run? We need to get the flexible csv help onto the production site.

[richpomfret]

@lemon-ukgen has been given the go-ahead to create the script to automate this. We will try and roll it out over the next sprint.