Identity Server Configuration: Crowd Source Scenario
I'm working on building a HTML5 application to gather public feedback on a project. I'm going to have participants create polygons for specific areas of interest on the map and I'd like to have them record their comments etc. I'd like a way to retain their contact info/username while they carry out this task in order to populate editor tracking fields without having to ask them for it every time they create a feature. I'd like to use identity servers (Twitter, Facebook,Google+, etc.) to gather this user info and then be able to pull the user name during the workflow activity when a user creates a new feature (all editing will be carried out through a workflow rather than the freeform editing).
Has anyone ever implemented these other identity providers that would be able to describe the process?
Thanks,
Warren
0
-
This sounds like a good opportunity to use the Set External Value and Get External Value workflow activities. That way the user would only have to enter their info once, which you could store in external values and recall each time they create a new feature.
The one caveat is that the external values will only persist while the user is using the app.0 -
Hi John,
Thanks for the tip! I used those activities to prompt the user to supply their email and stored it in the client for later use in my workflow. Did exactly what I wanted to do without the fickle security settings.
Warren0 -
Hey Warren, I am currently working out how to take a user-uploaded file (GPX or KML etc) and save it to our server along with comments, etc. Your application sounds like it might be very similar! Any chance you would share what you built? 0
Please sign in to leave a comment.
Comments
3 comments