So, currently the metadata output has a lot of empty fields, either because we lack the information from the data/DSD to fill them or because I simply don't know what they are.
We need to figure out which of these fields are a capital R Requirement for the API/Application Profile (meaning fields that MUST have information in them for minimal viable product) and in general gather information on the rest of them where possible.
What to do:
The main work of this task will be communicating with someone who knows the nitty gritty details on the API/Application Profile (If I remember correctly Andrew Fergusson offered to convene on this) and writing up as much information as possible that we can then use to adjust the transform where necessary or plan steps to get hold of the required information (adding required information to the config specification etc)
Acceptance Criteria
[ ] Documentation on the various fields in the metadata output
and depending on what the requirements end up being either:
[ ] Implement changes to the transform to include any missing required information if its something we can get from the data/DSD
[ ] Add details of these changes to the code documentation
or:
[ ] Write up which required information we are missing along with recommendations as to where would could get it (eg config file/supplemental metadata file)
What is this?
So, currently the metadata output has a lot of empty fields, either because we lack the information from the data/DSD to fill them or because I simply don't know what they are.
We need to figure out which of these fields are a capital R Requirement for the API/Application Profile (meaning fields that MUST have information in them for minimal viable product) and in general gather information on the rest of them where possible.
What to do:
The main work of this task will be communicating with someone who knows the nitty gritty details on the API/Application Profile (If I remember correctly Andrew Fergusson offered to convene on this) and writing up as much information as possible that we can then use to adjust the transform where necessary or plan steps to get hold of the required information (adding required information to the config specification etc)
Acceptance Criteria
and depending on what the requirements end up being either:
or: