Feature: option to add tags to reports

[JenMysoc]

From Zoja and Dan Brickley working on Sarajevo FMS: "we also noticed that it would be nice to have an option to add sub-categories to a main category"

[kaerumy]

We also don't mind having additional tags/categories.

For example, "Broken playground railing" comes under "Playground Infrastructure", but we would also like to be able to tag it as "Child Safety". One is a maintenance category, the other is an impact/target group category.

[davewhiteland]

Further to @kaerumy's comment (having discussed with him in Jakarta) the core issue here is to be able to assign tags (which is proposed as the most general way of allowing classifications other than the category).

Ideally:

• could be added/removed by a user with add_tag permissions (their use case is this would be done by someone who's logged in but who is not a body's staff user nor an admin, but has one special power of being able to affect tags on any report)
• could be used as a criterion by an API call (hence: get all reports with this tag) -- I'm not convinced this isn't a lot like existing Open311 Server functionality (but I'm not sure how that's accessed/enabled; noting it here while I think of it)

[kaerumy]

@davewhiteland the API that I'm thinking of, is more an open data service, rather than a traditional application API.

From what we've learned from Popit, this sort of feature allows open data users to do alls sorts of mashups for analysis, visualizations or embedded live in other websites for specific queries extending FMS use case from solving problems, to a data source for policy and accountability.

Some use cases:

• pull up all reports with geolocation and using mapit with administrative boundaries, map it to elected representatives.
• pull up all reports tagged with women's safety, pedestrian, disabled etc. as evidence to support policy requests of CSOs

The example I gave in my talk. A broken street light is more than just a local council issue, it can also be a safety issue, especially with joined up data. Is there a correlation between streets with lights that are always broken/requested with crime?

Similarly, one report especially with geolocation + mapit, can be raised at different levels. The urban flats compound, the local council zone, the local council, elected state rep and the parliamentary rep areas.

This tag and or sub-category or better.. additional categories (flat not hier) will allow us to extract more relationships from FMS then just local council categories.

[davewhiteland]

For @kaerumy, thiis isn't exactly about identifying the Minimum Viable "Product" (MVP), but I am interested to know if the general case I describe below looks good and useful to you:

• [ ] tags exist as entities (e.g., tag table in database) (so: tags are a fixed list of words/phrases)
  MVP no internationalisation on these yet, but later need to anticipate tags being presented in multilingual installations
• [ ] add/edit/remove tags (that is, the list of all allowed tags) in the admin, although MVP could manage these (e.g., by INSERT INTO TAGS with SQL in the db)
• [ ] tags can be associated with a report (perhaps, later, on other things too? but MVP: only reports)
• [ ] tags are displayed on the public report (see prettified screenshot, from your (Sinar) live https://aduanku.my/report/842)
• [ ] nominated staff users can add/remove tags on a report
  MVP: any/all tags (later, only nominated tags, e.g. user firedepartment@example.gov can only add or remove "fire hazard" tags)
• [ ] ability to retrieve reports by tag
  MVP this is an SQL query, i.e., a side-effect of the tags being entities in the database, but eventually an API/URL providing access to such lists/data

[leowmjw]

@davewhiteland Looks good for a MVP!

[kaerumy]

The looks good to me too.