Allow citizen adding/editing of profiles until claimed by privileged users

[patcon]

Firstly, this is awesome.

For a citizen group looking to re-deploy this app for their local municipal government (say, in Toronto, Canada), it might be simpler to bootstrap the usefulness of that deployment if management of social media profiles was more liberal and public to begin with.

So the thought is that there could be an option to make the site work a little more like Google Maps Places: Any citizen [who creates an account] can add a social media profile for a department or organization that they're aware of, and any citizen can then update that profile. But a privileged user (for example, with a toronto.ca email address) can then "claim" the profile, and start managing it directly.

Would this be something you were consider accepting a pull request for?

[dvito]

It would be great to accept a pull request if it could be handled with configuration changes. We currently integrate with a CAS service the enforces said authentication style (and that can not be changed).

My only concern would be the want for a very different public front end and branding as well. But if a sensible way to make these configuration driven could be devised, it would be welcome!

[patcon]

Thanks @dvito. I expect this will be significant effort, so I'm not able to take it on right now. But it's great to know there's willingness for when my project backlog clears out :)

I've also added it as a potential project for someone to tackle at our brigade chapter hacknights!

[JustinHerman]

That's amazing @patcon -- thanks for taking notice and sharing this idea. We'd love to work with anyone who can use this data to improve the trust and authenticity of sharing and engaging with our digital public services!

[ryanwoldatwork]

While this issue isn't readily actionable or feasible as written - Allow citizen adding/editing, I do think something can be done along these lines that gets most of the way there while keeping the existing system boundary (official public staff logins only).

For example, something like: a User could report an account that is not listed in the Registry, for triaging; where a valid account could become a verified entry. Minimally viable: Adding accounts to consider, as an Issue here, could work.