New task was created
Discuss and decide + write rules for importing of Eurostat datasets
Created on Thursday 11 February 2021, 09:48Back to task list
TypeGeneral Research Work
Assigned toCarolin Bellstedt
SubscribersAristide AthanassiadisCarolin BellstedtPaul Hoekman
We have our great Eurostat manager and have invested lots of time to go through most of the 9949 Eurostat datasets, 472 are still pending, to decide if they are relevant from a UM/CL perspective or not.
Now we are in the situation, where the CL cities who find those datasets too, will add the same one, on their own. It could be that they all add "Gross domestic product (GDP) at current market prices by NUTS 3 regions" (especially because there is no name check for a dataset, when adding one, which normally makes sense). Do we want to have 7 instances of the same dataset? Probably not, right? So we should decide rather sooner than later, if we do import the Eurostat datasets or instead see what the cities will actually do.
Of course, there is no need to import all 9,949 Eurostat records, but we could discuss if it makes sense to import if not the
800 accepted records, then perhaps the 155 accepted NUTS records:
- 155 accepted NUTS, https://cityloops.metabolismofcities.org/eurostat/?q=nuts&show=accepted
- 155 is made up of 40 accepted NUTS 3 (incl. NUTS3) https://cityloops.metabolismofcities.org/eurostat/?q=nuts+3&show=accepted
- and 114 accepted NUTS 2 (plus 1 NUTS2) https://cityloops.metabolismofcities.org/eurostat/?q=nuts+2&show=accepted
We will again run into the issue of having MoC and CL tags, there is no way around it, but for now we could use CL tags and have the cities tag them. OR we add the CL tags in addition and the cities as spaces, which is possible in the backend, as I've just tested it.
In any case, first we should decide: to import or not to import? Aris, Paul, what do you think?