Local Guide Best Practice: Submit changes one by one

[This is one of a series of articles originally published on Local Guides Connect]

Sometimes you come across a point of interest where several pieces of information are missing or wrong. Then you click ‘Suggest an edit’, make all the changes and click ‘Submit’, right? Well, my advice is not to do this, but instead submit the changes one by one. Admittedly, it’s a few extra clicks, but I have experienced that if you submit several changes at the same time and for some or other reason one of the suggested changes is not applied, none of the changes get applied.

And for those who are eager to score as much local guide points as possible there is another reason as well: the counter that shows you how many points you have earned always only counts to 5 when clicking submit, no matter how many suggested changes you submitted – just one single or 2, 3 or 4. Compare this to what happens when you post a review for a point of interest: the counter then does produce a different result if you submit a review that is over 200 characters long, as it takes into account the 10 extra points for a long review. So, my interpretation is that ‘Suggest an edit’ brings 5 point per time you run the module, not always 5 points per changed piece of information – unless you submit them one by one.

The original article can be found here

 

Disclaimer: the practices described here as best practice are my personal interpretation, and I don’t claim any level of official endorsement.

One thought on “Local Guide Best Practice: Submit changes one by one

  1. Pingback: Local Guide Best practice: Reporting duplicates | THE SECOND HALF

Feel free to leave a reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.
https://janvanhaver.com/2018/05/26/local-guide-best-practice-submit-changes-one-by-one/
janvanhaver.com
crawl=CC-MAIN-2018-43
250246
application/http; msgtype=response
sha1:SEHAKDNDWB26RTWNHVI6NTZZ7PBJNEB2
<urn:uuid:cd0634ea-1a89-4748-bc60-62d15f3b6218>
2018-10-19T04:32:41Z
192.0.78.24
text/html
sha1:O34VHIFUEPXWSPPAP26L6MTFZVQHLBEN
<urn:uuid:8663a439-326a-42f7-b22d-6b1853f5278b>
https://janvanhaver.com/2018/05/26/local-guide-best-practice-submit-changes-one-by-one/
response
<urn:uuid:7ecd4ab0-1fc8-4473-8c85-7c8787f847d8>
isPartOf: CC-MAIN-2018-43
publisher: Common Crawl
description: Wide crawl of the web for October 2018
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-79-243-28.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 0.11-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/