PDCT 395/id generation family

[diversemix]

Description

• some minor type / linting fixes
• Update and extend the family DTOs
• Generate the family import_id
• Change the update endpoint to include the import_id
• update tests
• Start to introduce "Protocol" for the FamilyRepo

Type of change

Please select the option(s) below that are most relevant:

• Bug fix
• New feature
• Breaking change

How Has This Been Tested?

Please describe the tests that you added to verify your changes.

Reviewer Checklist

• The PR represents a single feature (small driveby fixes are also ok)
• The PR includes tests that are sufficient for the level of risk
• The code is sufficiently commented, particularly in hard-to-understand areas
• Any required documentation updates have been made
• Any TODOs added are captured in future tickets
• No FIXMEs remain

[linear]

PDCT-395 Id generation for entities

We will need to construct "import" ids for newly created entities in the form:

<data_source>.<type>.<x>.<y> as we currently do - but the xy components of this id needs storing somewhere or calculating for when we need to generate a new one.

Option 1

Due to the fact that a "data source" is not represented in the database - instead we use organisation… We could change the format to be <organisation>.<type>.<x>.<y> . We would still need some sort of counter table in the backend but this would be linked (and think may be a soft link) to the organisation.

Option 2

We could go the whole-hog and introduce datasources now 🤔

[katybaulch]

Looks good, thanks for raising those tickets for my comments 👍