When a LPA submits a local plan such as Southampton they provide a datasets column, this then has a semi colon seperated list which informs the service which rows need to be applied to other datasets. For example, Minerals Plan, this works however when running it through as minerals plan it does not apply any of the mandatory fields required for minerals plan - such as document count.
So when a Jira ticket comes through with local plan dataset submission for Southampton, as a data admin comes to then separately submit it as whichever sub-datasets this should be broken down into, as per the above example submit it as minerals plan, they are then blocked by the mandatory field of document count being needed, but it has never raised this issue when the dataset was provided as a local plan dataset.
Likely needs a initial SPIKE on how possible this is, currently it will be processed as local plan through the pipeline, how can we explore in dl python checking for the other mandatory fields being pulled in based on that datasets semicolon separated list.
When a LPA submits a local plan such as Southampton they provide a datasets column, this then has a semi colon seperated list which informs the service which rows need to be applied to other datasets. For example, Minerals Plan, this works however when running it through as minerals plan it does not apply any of the mandatory fields required for minerals plan - such as document count.
So when a Jira ticket comes through with local plan dataset submission for Southampton, as a data admin comes to then separately submit it as whichever sub-datasets this should be broken down into, as per the above example submit it as minerals plan, they are then blocked by the mandatory field of document count being needed, but it has never raised this issue when the dataset was provided as a local plan dataset.
Likely needs a initial SPIKE on how possible this is, currently it will be processed as local plan through the pipeline, how can we explore in dl python checking for the other mandatory fields being pulled in based on that datasets semicolon separated list.