Geo_ids for datasets should be consistent between repositories #3354
Description
Enhancement Description
In different places, datasets have different names and naming conventions. All datasets should have consistent and clear names throughout their lifecycle, allowing users to identify them logically and avoid bugs. Additionally, our naming was originally set up to support the Netherlands (primarily) and may not properly (or at least logically) account for the various 'levels' of datasets we might support in the ETM. This spread is visible in ETLocal:
def group
if geo_id.start_with?('GM', 'BEGM', 'DKGM')
'municipality'
elsif geo_id.start_with?('WK')
'district'
elsif geo_id.start_with?('BU', 'BEBU')
'neighbourhood'
elsif geo_id.start_with?('RG')
'region'
elsif entso_data_source? || geo_id.start_with?('UKNI') || geo_id.start_with?('GB')
'country'
elsif geo_id.start_with?('RES', 'ES')
'res'
else
'province'
end
Examples:
The dataset GM1961_vijfheerenlanden (ETSource) is referred to as GM1961 in ETLocal. This is a pattern common to all ETLocal datasets