-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update of the validation process step 2 #1786
Comments
@geoffj-FUG this is ready for testing on Test3 |
Only one item left for this step. see end of this test log. See also test 1 for Upload problem. Geoff Test 1 – check upload of a file being validated (old style) when file is not on system as being validated. HO107_1925 is a file where validation is almost complete. Uploaded as a new file. It should reject as a file that is not currently being validated. Not uploaded and no email received. Does not appear in list of files. Problem, no email or response in this situation. Test 2 – Upload a file that is not being validated Test 3 – Mark HO107_1925A as ready for validation. Test 4 - Download validation spreadsheet. Test 5 – Reload validation spreadsheet. Test 6 Display Warning messages. OK 227 entries need validation. Correct. Test 7 – Display entries needing validation. |
@geoffj-FUG |
Anne Test 1 now OK. Just making the Propagate button disappear to go. We could wait until step 3 ready and deploy all 3 steps together. Geoff |
Geoff |
Test 7 now OK. Hold deployment until step 3 is available. |
This is part of the Epic #1783. Please read the document linked to #1783 when considering this story.
Step 1 of this Epic introduces Pre-validation to the validation process.
Step 2 allows future validation to update and build on the existing pre-validation data that was established during revalidation of the vld data collection.
Once a piece has been transcribed and proofread it may or may not contain information in the alternative Place of Birth fields. Pre-validation will populate some alternative Place of Birth fields that have not yet been populated. testing the piece will set all the records as true in the warning or error field that is associated with POBs. Therefore if a verbatim place of birth entry exists in the Gazetteer it will not need to be further validated and the flag set to true. This is the current process when a file is being validated.
When the current validation screen is displayed it does not show the Propagation Actions unless they have been edited. This should be amended so that they are shown if:
The verbatim Place of Birth is not the same as the Alternative Place of Birth then the Propagate POB action is available.
The Notes field is not null, then the Propagate Notes action is available.
At this point these actions will propagate through the piece as currently happens.
This change can be deployed once it has been tested.
Geoff
The text was updated successfully, but these errors were encountered: