Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow for Suggesting New or Updated Datasets for Non-Authorized User #107

Open
JJediny opened this issue Apr 24, 2016 · 2 comments
Open

Comments

@JJediny
Copy link
Contributor

JJediny commented Apr 24, 2016

The current edit functionality is limited the user to have a github account and that the user has contributor level access in order to post new or updating a .md file within the git repo. This limits the ability of the viewer of the data to participate or directly engage/contribute to the sites content.

However if the read only view still non-authed users to Suggest a New Dataset or Suggest Update to Dataset option/button could re-use a similar process authed users but instead of posting to the repo as a new commit it would redirect the form content to a Github Issue or Pull Request perhaps using a standardized template to ensure rationale/context is passed along with the content. This approach however would still require a github account. Another approach is that Github GIST allows for the anonymous GIST(s) this approach would allow for more open engagement but would have to offer/automate a separate notification (email/sms/twitter) process (and all associated JS for the processing) and/or offer a simple popup message with instructions for manually notifying the site owner.

This issue is only meant for discussion on general utility and feasibility of potential approaches at this time

@timwis
Copy link
Owner

timwis commented Apr 24, 2016

👍 I think the platform JKAN is built on (GitHub) gets us 90% of the way there with its pull request capabilities, so how can we not take advantage of that. I like your outside-the-box thinking on gists; wouldn't have thought of that. But there may be a way to design the user experience where "registering an account on github" isn't too disruptive.

By the way, what about that hypothesis feature you added? How far does that take us?

@OxOpenData
Copy link

I followed the guidance at https://github.com/toperkin/staticFormEmails to incorporate a feedback form on our site. Feels like this is an off-GitHub thing to do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants