An issue was identified where /organisations/local-authority:CAB/conservation-area contains records, but the system incorrectly believes that no endpoints have been submitted for Cambridge. As a result, it displays "no conservation areas submitted."
The root cause is that all resources have an end date, (caused by an empty ArcGIS page). While this is straightforward to disable on the dataset page, the dataset overview page is generated from the performance database. That database requires an update so it can include endpoints even when they are linked to retired resources.
An issue was identified where /organisations/local-authority:CAB/conservation-area contains records, but the system incorrectly believes that no endpoints have been submitted for Cambridge. As a result, it displays "no conservation areas submitted."
The root cause is that all resources have an end date, (caused by an empty ArcGIS page). While this is straightforward to disable on the dataset page, the dataset overview page is generated from the performance database. That database requires an update so it can include endpoints even when they are linked to retired resources.