admin interface

[jywarren]

We should think about the kinds of activities site admins would regularly need to do, and what access such admins need to have. @shapironick -- thoughts?

[shapironick]

I really don't know, having not been an admin to anything before, let alone something like this. Maybe we can model it after the PL or spectral workbench admin interface?

-An ability to download survey data is the primary thing that admins would need to be able to do. -Some analytics might be nice to see but a combination of google analytics and offline/non automatized statistical analysis might be fine.
-I guess it would be good to be able to see maybe the 10 most recent submissions? -I think we can keep this pretty minimal for now but I also don't have much foresight when it comes to what we might want as i've never done anything like this.

[jywarren]

An ability to download survey data is the primary thing that admins would need to be able to do.

This will already be available to users (and perhaps the public though we haven't decided yet I think?) so we can just add an additional "full download" plus a privacy/security warning to that page/interface which only admins can see.

Some analytics might be nice to see but a combination of google analytics and offline/non automatized statistical analysis might be fine.

On this particular project, I'm not sure we want to use Google Analytics, as it will collect more information (esp. geographic information) than we want to on users. Perhaps we can use some kind of password-protected version of Pivik or whatever that open source one is called.

I guess it would be good to be able to see maybe the 10 most recent submissions?

But anyone would be able to see those. Perhaps an interface to see ones which are not public, in a list view. This could just be an alternate list view (and extra link) which only admins can see. Not much of a separate interface, which is good.

We don't currently have private messaging, but we could expose (with privacy warnings) email addresses of users only to admins. Does this constitute a privacy risk?

There will presumably be very few admins, like 1 or 2, for privacy/security reasons.

[jywarren]

What about a user list page, that only admins can see? Would we want the public to see a list of users, or is this an area we want to do our best to make it harder for individuals (even those who have come forward publicly) to be tracked?

[shapironick]

All these features sounds great. Thanks very much and sorry for not being more informed about what we might need.

Sound good to avoid google analytics and exposing email addresses to admins sounds like a reasonable thing to do, without being too risky.

Maybe also it would be good for admins to be able to see users who registered but never filled out a form or those who answered a few questions but never got through the hole survey--as it might be nice for the administrator or an outreach member to reach out to them. I guess this could be automated.

A public list of users feels a little more risky than beneficial to users. Maybe we can make the conversational space between sections of the survey accessible in their dashboard after they have completed the survey so they can use those topic specific places to maintain conversations and make a space for organizing that will eventually overflow those spaces and necessitate other spaces for collective organizing.

On Fri, Jul 4, 2014 at 1:24 PM, Jeffrey Warren notifications@github.com wrote:

What about a user list page, that only admins can see? Would we want the public to see a list of users, or is this an area we want to do our best to make it harder for individuals (even those who have come forward publicly) to be tracked?

— Reply to this email directly or view it on GitHub https://github.com/publiclab/wherewebreathe/issues/22#issuecomment-48038009 .

[jywarren]

re-assigning for Phase 2.