New task was created
Community Portal
Remove Dataset as separate model
Created on Sunday 21 February 2021, 16:50
Back to task list-
ID857523
-
ProjectMetabolism of Cities Data Hub
-
StatusCompleted
-
PriorityMedium
-
TypeProgramming work
-
Assigned toPaul Hoekman
-
SubscribersCarolin BellstedtPaul Hoekman
Description
At some point we introduced a Dataset model. It's still present, see models.py. However, the fields we introduced turned out not to be that essential, and it actually made things more complicated than needed - for the end user but also from a programming viewpoint. Datasets are an extension of the LibraryItem, so we must now migrate them back into LibraryItems and remove any Dataset() reference in the system. The class should cease to exist.
Discussion and updates
3 years, 1 month ago
2 years, 10 months ago
I got into a whole migration mess but it's now sorted.
Principally done in commit dfb22f320581a5451a2074aca724e06a08a6a0b2
2 years, 10 months ago
For record keeping, was this what we had used as part of the CityLoops efforts to identify datasets and portals that would give us and other cities a lot of data at once?
Is this one (https://data.metabolismofcities.org/dataportals/) different from it or still a remnant?
2 years, 10 months ago
Yes that is correct, that is the stuff.
The point is that I had technically set up new so-called "models" (tables in the database, basically) in order to manage a set of fields that were going to be unique for these datasets and data portals (like frequency of updating and technology used). These models, however, caused a lot of extra work in many other places and ended up not being used. So what I have done is basically removed those parts of the database. The types still exist as you see, just not those fields and special treatment.
2 years, 10 months ago
Got it. Thanks for clarifying.