search

AnanseGroup / atlas_of_innovation

Interactive map, database, API for all the innovation spaces everywhere
https://www.atlasofinnovation.com
4 stars 5 forks source link

Ability to flag entry for fix from the map #59

Open MakerNetwork opened 6 years ago

MakerNetwork commented 6 years ago

There are many entries that are wrong or outdated. We should provide at the least a boolean flag to mark the entry for review. Preferably, however, would be the ability to let us know what's wrong with that entry.

Preferred to use pre-determined selector (multi-select checkboxes probably best):

...and a free-form entry to add details. Free-form entry should have captcha. Should also require a name and email for contributor.

annawb commented 6 years ago

We should let random users edit the space pages directly, Wikipedia-style, and then take regular backups of the site in case we get hacked.

Otherwise, there will be a lot more work for the moderators who have to approve or make edits... and eventually they’ll forget to make changes, which is the frustration with fablabs.io.

On Jul 5, 2018, at 8:26 AM, MakerNet.work notifications@github.com wrote:

There are many entries that are wrong or outdated. We should provide at the least a boolean flag to mark the entry for review. Preferably, however, would be the ability to let us know what's wrong with that entry.

Preferred to use pre-determined selector (multi-select checkboxes probably best):

wrong location on map address wrong site closed site moved changed name wrong URL other ...and a free-form entry to add details. Free-form entry should have captcha. Should also require a name and email for contributor.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

MakerNetwork commented 6 years ago

We will have to come up with a set of business rules for macro-level functions such as add a space, remove a space, etc...

Also, shouldn't we allow for automation to "claim" a space so that you can control who edits and/or moderate edits. It could be something where an automated email can be sent to the address on file or a moderator can get involved if necessary.
The data model would then be a three-tier user system:

1) logged in (presumably identified via automated email confirmation) member of the public

Lyla-Fischer commented 6 years ago

I like the concept of being able to 'claim' a space. We have generally been trusting that Bad Things will generally not be done by the community, but I can see an edit war happening by a close-by competitor or disgruntled community member. Those two cases seem like they might happen at least once, globally, based off of what I know about competition for resources and community formation. Someone's going to have ill will against some space eventually. We should have something in place to prevent that ill will from spilling onto a space's online presence.

dottiemaej commented 6 years ago

Agreed.

annawb commented 6 years ago

That sounds good! As long as random users can edit most of the fields and also publicly flag for deletion/address change, because otherwise I guarantee you that space moderators won't keep things updated. But having some mechanism in place to prevent edit wars is a good idea.

annawb commented 6 years ago

Lyla and I agree on @MakerNetwork 's data model! The main issue for fablabs.io is actually the lack of admins... so how about allowing all NoM State Ambassadors and all registered space owners to approve general wiki edits to any space? But only the admins (state ambassadors, that space's managers, trusted volunteers) can delete spaces or change addresses.

And anyone can add a new space, but it will be flagged as "unverified" until approved by an admin.

annawb commented 6 years ago

Also, we're going to send our list to state ambassadors for editing before actually publicizing the site.

touchthesun commented 6 years ago

Anna, I really like this idea. It solves nicely the problem of integration with NoM apparatus.

The next steps in implementation of this seem like they ought to involve the following:

Also, if a state lacks an ambassador, or there is an interim period between ambassadors, is there a backup plan for how to resolve such issues, or do they just form a backlog for the incoming ambassador when they step up?

On Fri, Jul 20, 2018 at 8:55 AM, Annawb notifications@github.com wrote:

Also, we're going to send our list to state ambassadors for editing before actually publicizing the site.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-406643623, or mute the thread https://github.com/notifications/unsubscribe-auth/ARrzj7LgWKWyAvCISbZ4XHNvKHZV8AoTks5uIf1igaJpZM4VEFy7 .

-- "The truth dazzles gradually, else the whole world would be blind."

--Emily Dickenson
annawb commented 6 years ago

Thanks for outlining these steps, Nathan!

How about we have a number of trusted Global Ambassadors who can approve anything, anywhere in the world? Or, we could just provide our regional/state ambassadors with global permissions for any longstanding issues needing approval.

Based on the experiences of hackerspaces.org http://hackerspaces.org/ and fablabs.io http://fablabs.io/, I’m more worried about inaction among moderators than I am about malicious actors.

On Jul 20, 2018, at 9:27 AM, Nathan notifications@github.com wrote:

Anna, I really like this idea. It solves nicely the problem of integration with NoM apparatus.

The next steps in implementation of this seem like they ought to involve the following:

  • Create a Role in our system for State Ambassador, with appropriate access privileges.
  • Create a simple UI for Ambassadors to see and resolve all issues up for arbitration
  • Get contact info for each ambassador from NoM and invite them to sign up on this system and claim that Role.
  • Keep an active record of who is acting as Ambassador at any given time, posted publicly on the Atlas and NoM sites (to be mirrored on MakerNet at a later date).

Also, if a state lacks an ambassador, or there is an interim period between ambassadors, is there a backup plan for how to resolve such issues, or do they just form a backlog for the incoming ambassador when they step up?

On Fri, Jul 20, 2018 at 8:55 AM, Annawb notifications@github.com wrote:

Also, we're going to send our list to state ambassadors for editing before actually publicizing the site.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-406643623, or mute the thread https://github.com/notifications/unsubscribe-auth/ARrzj7LgWKWyAvCISbZ4XHNvKHZV8AoTks5uIf1igaJpZM4VEFy7 .

-- "The truth dazzles gradually, else the whole world would be blind."

--Emily Dickenson — You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-406653098, or mute the thread https://github.com/notifications/unsubscribe-auth/ASnZe1P9c9C9rmA0CIReBNGGaxA6uRDiks5uIgT4gaJpZM4VEFy7.

touchthesun commented 6 years ago

Agreed, Anna. It may make more sense to have Regional Ambassadors, rather than specifically State Ambassadors, due to variance in population and makerspace density.

On Fri, Aug 10, 2018 at 7:47 PM Annawb notifications@github.com wrote:

Thanks for outlining these steps, Nathan!

How about we have a number of trusted Global Ambassadors who can approve anything, anywhere in the world? Or, we could just provide our regional/state ambassadors with global permissions for any longstanding issues needing approval.

Based on the experiences of hackerspaces.org http://hackerspaces.org/ and fablabs.io http://fablabs.io/, I’m more worried about inaction among moderators than I am about malicious actors.

On Jul 20, 2018, at 9:27 AM, Nathan notifications@github.com wrote:

Anna, I really like this idea. It solves nicely the problem of integration with NoM apparatus.

The next steps in implementation of this seem like they ought to involve the following:

  • Create a Role in our system for State Ambassador, with appropriate access privileges.
  • Create a simple UI for Ambassadors to see and resolve all issues up for arbitration
  • Get contact info for each ambassador from NoM and invite them to sign up on this system and claim that Role.
  • Keep an active record of who is acting as Ambassador at any given time, posted publicly on the Atlas and NoM sites (to be mirrored on MakerNet at a later date).

Also, if a state lacks an ambassador, or there is an interim period between ambassadors, is there a backup plan for how to resolve such issues, or do they just form a backlog for the incoming ambassador when they step up?

On Fri, Jul 20, 2018 at 8:55 AM, Annawb notifications@github.com wrote:

Also, we're going to send our list to state ambassadors for editing before actually publicizing the site.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-406643623 , or mute the thread < https://github.com/notifications/unsubscribe-auth/ARrzj7LgWKWyAvCISbZ4XHNvKHZV8AoTks5uIf1igaJpZM4VEFy7

.

-- "The truth dazzles gradually, else the whole world would be blind."

--Emily Dickenson — You are receiving this because you commented. Reply to this email directly, view it on GitHub < https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-406653098>, or mute the thread < https://github.com/notifications/unsubscribe-auth/ASnZe1P9c9C9rmA0CIReBNGGaxA6uRDiks5uIgT4gaJpZM4VEFy7 .

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/AnanseGroup/atlas_of_innovation/issues/59#issuecomment-412245924, or mute the thread https://github.com/notifications/unsubscribe-auth/ARrzj5oo657WjR4oFFpN1t_8duKzPdN4ks5uPkW8gaJpZM4VEFy7 .

-- "The truth dazzles gradually, else the whole world would be blind."

--Emily Dickenson
Lyla-Fischer commented 6 years ago

A lot of this conversation is relevant to the moderator ticket (https://github.com/AnanseGroup/atlas_of_innovation/issues/17)