Issue tracking for project migrating FreeCEN to FreeCEN2 genealogy record database and search engine architecture. Code developed here is based on that developed in MyopicVicar
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.
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.