Currently, the tags in the Data Catalogue feature a few issues which seem worth resolving in a more long-term plan:
satellite-data: almost all Imago data products are related to satellite data, so this looks a bit too broadCLiVE used as both group name and tag - I suppose it should be used only as a group nameboundaries tag includes input LSOA/MSOA boundaries and is a bit ambiguous because this data contains polygons, rather than lines. If we use the same logic for other data products at LSOA/MSOA level, they can also count as 'boundaries'. It could be more meaningful to delete boundaries tag and use only Geographies group to describe these.- the lowercase and uppercase are a bit inconsistent:
Air Pollution and air-pollutionUK,uk, and EnglandMSOA and msoa, LAD and lad
I'd suggest creating an Imago vocabulary that defines strict requirements for which tags can be assigned to records. This vocabulary could then be linked to the CKAN metadata upload validation, so that only approved tags can be used for any records in the Data Catalogue. It doesn't have to be a complex dictionary like INSPIRE or ISO19115, and it could be a simple list of tags - only those may be used for any records in the Data Catalogue.
Currently, the tags in the Data Catalogue feature a few issues which seem worth resolving in a more long-term plan:
satellite-data: almost all Imago data products are related to satellite data, so this looks a bit too broadCLiVEused as both group name and tag - I suppose it should be used only as a group nameboundariestag includes input LSOA/MSOA boundaries and is a bit ambiguous because this data contains polygons, rather than lines. If we use the same logic for other data products at LSOA/MSOA level, they can also count as 'boundaries'. It could be more meaningful to deleteboundariestag and use onlyGeographiesgroup to describe these.Air Pollutionandair-pollutionUK,uk, andEnglandMSOAandmsoa,LADandladI'd suggest creating an Imago vocabulary that defines strict requirements for which tags can be assigned to records. This vocabulary could then be linked to the CKAN metadata upload validation, so that only approved tags can be used for any records in the Data Catalogue. It doesn't have to be a complex dictionary like INSPIRE or ISO19115, and it could be a simple list of tags - only those may be used for any records in the Data Catalogue.