Use nodescripts to reduce the footprint of any v2 stuff

[drieJAC]

Background

There are several pain points in the code base and database where we are using v1 and v2 to manage changes in data structure/processes. These are difficult to manage and will be a growing source of pain as we move forward.
We could look to use the following approaches:

• use nodescripts to migrate data from v1 to v2
• set dates when certain v1 versions become redundant so that the code no longer needs to support it and we can remove versioning in those specific areas of the code/db

The following are areas where we use v1/v2 stuff:

• working preferences
• Character Information
• Application form
• Processing version

User Story

As a developer I would like to remove versioning where possible so that we dont need to support multiple versions of the code. It could be really handy to find a script or write one to go through all records in the db and build a json structure using colour coding to show how often/redundant a key is in the db. The script would need to save data in a file so that we dont need to run the script more than once.

Definition of Done

• User stories/acceptance criteria met
• Internal reviews passed (feedback actioned)
• User testing passed
• Relevant technical documentation updated
• User guidance updated
• Deployed and merged without errors

User Testing Steps

Specify for users what is being tested (but not how to test it.)

Feature Champion

[drieJAC]

@nickaddy Initially we will need discussions to work out where this is feasible and how we can do it. We can then write separate tickets for it.

[nickaddy]

Hey team! Please add your planning poker estimate with Zenhub @drieJAC @HalcyonJAC @KoWeiJAC @tomlovesgithub

[HalcyonJAC]

Please add your planning poker estimate with Zenhub @warrensearle

[warrensearle]

I don't think we can estimate this and feel the effort might be better spent, initially at least, on archiving and documenting our data model