Update of validation process step 4 (final step)

[AnneV-Learn]

When the freecen1_vld_entry_propagations collection was first created in was not envisaged that these pob propagations would be used by CSVProc data, so as the final step (Step 4) of the Strengthening of the Validation Process #1783 epic it would be advisable to rename the collection to freecen_pob_propagations to avoid future confusion.

This is likely to entail:

Renaming/migrating the freecen1_vld_entry_propagations collection data to freecen_pob_propagations and creating an index as was applied to freecen1_vld_entry_propagations.

Rename references in the associated model, views, controller and library entires (including Rakes) throughout all the project code.

[AnneV-Learn]

@geoffj-FUG
I am thinking it might be an idea to also add a 'Manage POB Propagation Records' Action in 'Your Actions' where POB Propagations could be viewed by anyone(?) and deleted by Data Manager or System Administrator (for hopefully the rare case were propagations are created by mistake)

[geoffj-FUG]

Anne Yes please. I have been working blind with what is in the propagation data. That will be very useful. It should be read only for Validators and Coordinators and read / write for the Data Manager and System Administrator. Can we make it sortable by county? Geoff From: Anne Vandervord ***@***.***> Sent: Saturday, August 3, 2024 12:47 AM To: FreeUKGen/FreeCENMigration ***@***.***> Cc: Geoff J ***@***.***>; Mention ***@***.***> Subject: Re: [FreeUKGen/FreeCENMigration] Update of validation process step 4 (final step) (Issue #1790) @geoffj-FUG <https://github.com/geoffj-FUG> I am thinking it might be an idea to also add a 'Manage POB Propagation Records' Action in 'Your Actions' where POB Propagations could be viewed by anyone(?) and deleted by Data Manager or System Administrator (for hopefully the rare case were propagations are created by mistake) — Reply to this email directly, view it on GitHub <#1790 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKCPIFI74A65RUW7G6BKN2LZPOLVHAVCNFSM6AAAAABJYHYVRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRVGU3TCMBSGQ> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/AKCPIFL526MCUIILLF6EPBLZPOLVHA5CNFSM6AAAAABJYHYVRSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUHBHPNA.gif> Message ID: ***@***.*** ***@***.***> >

[AnneV-Learn]

@geoff I recommend that we delay this until the new CSV POB validation functionality (#1787 etc) has been live for at least a month, so that any 'teething' issues can be ironed out first.

[geoffj-FUG]

I am happy with that delay.
I have issued a preview of the changed instructions for validation and asked for feedback. One month should allow us to evaluate these instructions and any tweaking to do.
Once we are stable and the validation is up and going then we can implement this change.
Geoff

[AnneV-Learn]

@geoffj-FUG
The renaming of the POB Propagations collection has been successfully implemented on Test3.
I have also added a 'Manage POB Propagations' Action for County Coords, System Administrators and Data managers. It appears as an Action after having chosen the County to Manage. Only the POB Propagation records for Verbatim Birth County matching the County are displayed and the 'Show' screen offers a Delete button.
Not sure exactly what you want for 'Checkers/Validators' - just a View List of Propagations option as an action?.
Anyway, perhaps you can take a look and report back. Thanks.