The capability of going back to previous versions of the data by adding a version number ... is an absolute must ... Basically "analysts" need to be able to go back in time in terms of data & code.
Alternatively, the analysts would need to create a copy of the data for each project, which kind of works against our "improve the data structure & flow" work as well as can limit the capabilities to assess further things.
What should be covered?
Show one or many ways to achieve the requirements described in "Why is this important". e.g. with Git, GitHub, Azure, pins, memoise, etc.
Discuss if the approaches shown or something else might work.
Suggested speakers or contributors
Database admins, analysts, software developers should be present for the discussion to be useful.
Who is the audience?
Everyone dealing with data at 2DII and beyond.
Why is this important?
What should be covered?
Suggested speakers or contributors
Database admins, analysts, software developers should be present for the discussion to be useful.
Resources
Checklist
2h before
10' before
******Backup (Google) https://meet.google.com/azf-xifn-scdStart