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

Create a campaign builder #16

Open
tobias47n9e opened this issue Sep 17, 2016 · 6 comments
Open

Create a campaign builder #16

tobias47n9e opened this issue Sep 17, 2016 · 6 comments

Comments

@tobias47n9e
Copy link
Member

Just had the idea, that a SPARQL based campaign builder would be a great idea (if and when the campaigns are added back to the app). A simple user interface to choose the campaign duration, and other details would be ideal.

Then a query could select the relevant items and export it to a format the either the app can read or access somehow. A WLM or WLE campaign should not take more than 5 minutes to set up.

@nicolas-raoul
Copy link
Member

Would you mind expanding with a user story? How would the builder work, and who would use it?
Would that be a part of the website, or of the app, or both?
Thanks! :-)

@tobias47n9e
Copy link
Member Author

I think the best thing would be putting it on the same website as soon as we transfer to a web framework. I would like to make it public, so anyone could save campaigns under a campaign id:

commons-app-address.org/campaigns/C1
commons-app-address.org/campaigns/C2
commons-app-address.org/campaigns/C3

Not sure if we should serve the query or the data under that address.

For the app the question are: Which campaigns do we show the the user, or do they see all of them? From this list or filtered list, the user can click on "Participate" and then the app will offer a second "Nearby list" that uses the data of the campaign. I already made some sketches for that, that I will upload later this week.

@nicolas-raoul
Copy link
Member

Letting anyone create campaigns exposes users to spam and buggy SPARQL... how about having all campaigns in a JSON file, and letting people modify the JSON via pull requests?

@tobias47n9e
Copy link
Member Author

Hadn't thought about that. Some restrictions are probably needed. Submitting a campaign could also create an issue on Github, which is easy to close when it is spam. Redirecting to pull requests might scare away potential contributors.

@nicolas-raoul
Copy link
Member

An easy web UI that automatically generates pull requests would be perfect indeed, if you know how to implement it :-)
commons-app.github.io is a static website with no server-side code, so that might limit our options.

@tobias47n9e
Copy link
Member Author

I have now decided to built the campaign manager as a separate tool on labs. Work is progressing well at the moment. We can also use a spatial database, so we can send nearby image requests to users. Hopefully I can have the first implementation online in a few weeks.

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

No branches or pull requests

2 participants