-
Notifications
You must be signed in to change notification settings - Fork 3
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
Produce UI design for crowd source image collection project #52
Comments
For the licensing thing, check with Leonard, he has both an Android dev and an Apple dev license |
I think for now we should keep it at the bare minimum. The UI @DatCorno shared yesterday was good, I would just make the upload and take picture icons bigger and more salient. |
Instead of a description box, I would suggest categories (flood, fire, drought, smog,... talk to @mukkavilli about the different options), and ask people to label the images they upload |
Leonard also brought up a good point yesterday, that we should give people the ability to take back images that they uploaded. He said that it would be necessary if we want ppl from Europe to use it (to be compliant with the new legislation) |
This would require the handling of account creations. Maybe we could have an anonymous no-takeback and the possibility of creating an account to take back your uploads? Because people will be less willing to share their photos I think if they have to go through hoops. |
Yeah I realize it's pretty complicated :-/ just something to keep in mind,
I guess.
…On Wed, May 1, 2019 at 9:56 AM François Corneau-Tremblay < ***@***.***> wrote:
This would require the handling of account creations. Maybe we could have
an anonymous no-takeback and the possibility of creating an account to take
back your uploads? Because people will be less willing to share their
photos I think if they have to go through hoops.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADMMIIWITABFDB4PYLQAP53PTGOPFANCNFSM4HJTRPFA>
.
--
Sasha Luccioni
Postdoctoral Researcher
Climate Change AI
https://mila.quebec/en/person/sasha-luccioni/
|
Yep, being RGPD compliant is going to be painful. Workaround: display an ID to every user and tell them to use it in any request by email they'd have to get their data back/deleted |
That's doable
…On Wed, May 1, 2019 at 10:02 AM Victor Schmidt ***@***.***> wrote:
Yep, being RGPD compliant is going to be painful.
Workaround: display an ID to every user and tell them to use it in any
request by email they'd have to get their data back/deleted
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#52 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ADMMIITOO5X3VJPA6CGX53DPTGPGVANCNFSM4HJTRPFA>
.
--
Sasha Luccioni
Postdoctoral Researcher
Climate Change AI
https://mila.quebec/en/person/sasha-luccioni/
|
I like that. |
Hi there, I spent some time looking for already existing approach to collect an image dataset. Not finding a ready-made solution, I turned to what exists in the open-source community regarding image hosting scripts : photo-hosting-scripts Please have a look at Chevereto. A Flickr-like free image hosting script that already handles account creation with social media, and a lot of features. It has quite a community behind and I believe It could be a good starting point. |
@sashavor @DatCorno thoughts? |
The website for the crowd source image collection project (we need a better name by the way) needs some actual UI design. I have create some basic prototypes just to have something from which to work from but in the grand scheme of things, if we want to use this project for more than floods, we will need to think about this. Here is a list of the main functionality I think the website should possess:
For me, this is the bare minimum. Now, if we want to scale this to other type of natural disasters, my concerns are as follows:
Edit:
Suggestions to be RGPD compliant:
The text was updated successfully, but these errors were encountered: