Cleanup Functionality

[phummelen]

Introduction

There is a lot happening in the world of cleanup the world (or your own street).
Most of these activities are nearly known. Maybe in the (close) neighborhood, sometimes it reached a (regional) newspaper.

What if we have a central location where we can store cleanup actions? So we can see where people are taken action, what their impact is and when the next action is going to be.
Or, from a more activism point of view, we want to show the government, companies, citizens and/or the politicians that there is too much waste!

To be able to work with this in a flexible way, we need four main parts:

1. Management Tool
2. Front-end (mobile and web clients)
3. Back-end (to store the pictures and the meta-data)
4. Visualization tooling

ad 1. Management Tool

Within this tool we have to manage the (recurring) cleanup action.
So we need some data per cleanup action, like

• long name
• description
• short name, as is main tag
• one extra tag (optional)
• owner (needs to be a user in the app)
• sponsor / stakeholder(s)
• attending members (this is a risky one, also from GDPR perspective)
• recurring (yes / no)
• start date / start time
• end date / end time
• data hidden till certain date (for if it's a activism action)
• api key (auto generated, for client app)
• app id (unique id per client app)

When the action is running the owner of the action can do follow up tasks on the action.
Like checking the photos on quality and/or if those belong to the action. If not, remove the action tags. The photo's can stay in the system, still having a date/time stamp and a GPS location. So if a "litter-tagger" sees the untagged photo's those can be tagged later on. That's out of scope for the cleanup functionality.

ad 2. Front-end (mobile and web clients)

If we have one (or more) client that retrieves it's data from the cleanup table, this app does not need any update.
Within the app we have to manage the upcoming, current and archived actions.
An example app that's working this way is the Plastic Avengers app.

ad 3. Back-end (to store the pictures and the meta-data)

We have a back-end (database) that needs an API in front, so the client app(s) can communicate directly with the back-end.
All needed actions (REST calls) should be available within the API.
Main REST calls are:

• retrieve (new) actions
• update current actions
• user attend status (will be there or ow, no longer able to attend)
• send photo with two tags (retrieved from the cleanup-table)

ad 4. Visualization tooling

On the dashboarding solution we are going to implement we can have different data visualizations.
An overview of all cleanups could be there. And a per cleanup details page with the status, the count of uploaded items.
Also if an (activism) action is done, some stats about the action. This part could be only available after the date that was mention as "till hidden" date.