Far easier to update /delete

Om

“fluid intelligence” - The ability to find meaning in confusion and to solve 
new problems, independent of acquired knowledge.
On Oct 25, 2018, 08:05 -0400, hot-requ...@openstreetmap.org, wrote:
> Send HOT mailing list submissions to
> hot@openstreetmap.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.openstreetmap.org/listinfo/hot
> or, via email, send a message with subject or body 'help' to
> hot-requ...@openstreetmap.org
>
> You can reach the person managing the list at
> hot-ow...@openstreetmap.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of HOT digest..."
>
>
> Today's Topics:
>
> 1. What's the best way for users to edit erroneous GIS data?
> (Yosem Companys)
> 2. Re: What's the best way for users to edit erroneous GIS data?
> (Mr. Stace D Maples)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 24 Oct 2018 11:31:14 -0700
> From: Yosem Companys <ycompa...@gmail.com>
> To: Progressive Exchange <disc...@progressiveexchange.org>,
> Liberation Technologies <liberationt...@lists.stanford.edu>,
> hot@openstreetmap.org, crisismapp...@googlegroups.com, UW Change
> Group <cha...@change.washington.edu>, UC Berkeley Tier
> <t...@tier.cs.berkeley.edu>
> Subject: [HOT] What's the best way for users to edit erroneous GIS
> data?
> Message-ID:
> <CANhci9Hoo5WOrQKeQ8q=C8Hc4jYT-ja=1z-lq0x5wzdod6q...@mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Hi All,
>
> I have a technical question that I was hoping one of you could answer.
>
> I'm working with an organization that has a Drupal website and is doing GIS
> mapping.
>
> The users have usernames and passwords on Drupal. They will use a data
> uptake tool to upload GIS data. Should the users make a mistake, however,
> we'd like to give them the option of editing or updating their data. We're
> trying to figure out how to do that while protecting user privacy.
>
> One possibility is to use some form of authentication. I recommended using
> the IETF's OAuth. Because we have a Drupal website, however, one of our
> developers recommended using HybridAuth
> <https://www.drupal.org/project/hybridauth> instead.
>
> Or, in case of a mistake, would it be easier for the user to upload the
> data again and have the new entry replace the old one?
>
> Any best practices in this area?
>
> Thanks,
> Yosem
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.openstreetmap.org/pipermail/hot/attachments/20181024/fb7db8b0/attachment-0001.html>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 24 Oct 2018 18:36:06 +0000
> From: "Mr. Stace D Maples" <stacemap...@stanford.edu>
> To: Yosem Companys <ycompa...@gmail.com>, Progressive Exchange
> <disc...@progressiveexchange.org>, Liberation Technologies
> <liberationt...@lists.stanford.edu>, "hot@openstreetmap.org"
> <hot@openstreetmap.org>, "crisismapp...@googlegroups.com"
> <crisismapp...@googlegroups.com>, UW Change Group
> <cha...@change.washington.edu>, UC Berkeley Tier
> <t...@tier.cs.berkeley.edu>
> Subject: Re: [HOT] What's the best way for users to edit erroneous GIS
> data?
> Message-ID: <c833b87f-8129-4ebe-ba4e-4a063c7ec...@stanford.edu>
> Content-Type: text/plain; charset="utf-8"
>
> Without seeing or knowing more about the workflow, I would say you should 
> avoid the rabbit hole of creating editing infrastructure, and use the 
> re-upload and overwrite method.
>
> In F,L&T,
> Stace Maples
> Geospatial Manager
> Stanford Geospatial Center
> @mapninja
> G+, Skype, Hangout: stacey.maples
> 214.641.0920
> Find GeoData: 
> https://earthworks.stanford.edu<https://earthworks.stanford.edu/>
> Get GeoHelp: https://gis.stanford.edu/
> stanfordgis Listserv: 
> https://mailman.stanford.edu/mailman/listinfo/stanfordgis
>
> "I have a map of the United States... actual size.
> It says, "Scale: 1 mile = 1 mile."
> I spent last summer folding it."
> -Steven Wright-
>
>
> From: Yosem Companys <ycompa...@gmail.com>
> Date: Wednesday, October 24, 2018 at 11:32 AM
> To: Progressive Exchange <disc...@progressiveexchange.org>, Liberation 
> Technologies <liberationt...@lists.stanford.edu>, "hot@openstreetmap.org" 
> <hot@openstreetmap.org>, "crisismapp...@googlegroups.com" 
> <crisismapp...@googlegroups.com>, UW Change Group 
> <cha...@change.washington.edu>, UC Berkeley Tier <t...@tier.cs.berkeley.edu>
> Subject: [HOT] What's the best way for users to edit erroneous GIS data?
>
> Hi All,
>
> I have a technical question that I was hoping one of you could answer.
>
> I'm working with an organization that has a Drupal website and is doing GIS 
> mapping.
>
> The users have usernames and passwords on Drupal. They will use a data uptake 
> tool to upload GIS data. Should the users make a mistake, however, we'd like 
> to give them the option of editing or updating their data. We're trying to 
> figure out how to do that while protecting user privacy.
>
> One possibility is to use some form of authentication. I recommended using 
> the IETF's OAuth. Because we have a Drupal website, however, one of our 
> developers recommended using 
> HybridAuth<https://www.drupal.org/project/hybridauth> instead.
>
> Or, in case of a mistake, would it be easier for the user to upload the data 
> again and have the new entry replace the old one?
>
> Any best practices in this area?
>
> Thanks,
> Yosem
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: 
> <http://lists.openstreetmap.org/pipermail/hot/attachments/20181024/6dcd50e4/attachment-0001.html>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> HOT mailing list
> HOT@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/hot
>
>
> ------------------------------
>
> End of HOT Digest, Vol 104, Issue 15
> ************************************
_______________________________________________
HOT mailing list
HOT@openstreetmap.org
https://lists.openstreetmap.org/listinfo/hot

Reply via email to