Generalise the harmonise file for reference

[Ben-Hodgkiss]

Overview
The harmonise file currently defines the mandatory fields for the ODP datasets. We want to generalise this ahead of the Manage Service/Config Manager being introduced that will check all datasets (not just ODP).

We should alter the Mandatory Field Dictionary so that it checks reference for all datasets. All other fields in the dictionary should stay associated to their particular dataset.

Tech Approach
A bullet pointed list with details on how this could be technically worked.

• Include links to relevant webpages, github files, user guides etc...
• Person raising the ticket to have a first pass at this (if they know the approach) - Owen will then review and bring to refinement session.

Acceptance Criteria/Tests

• There is no apparent change to the Check tool - it processes as it does now and raises the same issues when appropriate
• The tool however is generalised for all datasets to future proof it ahead of the implementation of the Manage Service Check

[Ben-Hodgkiss]

Following chat with @eveleighoj - decided to make this just for reference for all datasets. Will have subsequent ticket to define geometry for all datasets with geography typology (NB - we need to work out how this will work with brownfield-land given this uses GeoX and GeoY) as that is a more complex task.

[DJG-DS]

I have updated harmonise.py and test_harmonise.py files. I just need to fix an issue with an error with build 3.9 and then I will create a draft PR for @eveleighoj to check. I will upload documentation of the changes I made here in this ticket.

[DJG-DS]

@eveleighoj looking into this. Will leave it in block until this is has been done.

[DJG-DS]

Created draft pull request (422)

[Ben-Hodgkiss]

PR: digital-land/digital-land-python#422