-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Store different report types in different collections #15
Comments
in particular: currently waterpoints are stored as reports, this does not make sense as they are not reports, belong in separate db, outside of core taarifa |
What exactly are we trying to achieve? Currently Waterpoints are a subclass of the generic baseclass report in the ODM. Do you want to change this? |
Its just subtle semantics. See my (crappy) picture I emailed a couple days ago about the high level picture. Right now submitting a new report is equivalent to submitting a new waterpoint (you enter location, ward name, technology, village, etc). While actually a report about about a waterpoint should contain, for example, waterpoint id, who reported by, date, problem recorded, comments, ... So ideally a Taarifa report just refers to a particular waterpoint (by id) as stored in openstreetmap (where the waterpoint data should ideally end up) and does not duplicate waterpoint attributes in the reports collection. Of course for now we have to store the waterpoint CSV data somewhere. We can keep it in the same db but I would store it in a separate collection to keep the semantic distinction. |
Just to detail, given an empty, raw, database the upload script should:
|
No description provided.
The text was updated successfully, but these errors were encountered: