Reporting geocache problems

[following5]

Spin-off if issue #408.

What may need further discussion are the "report reasons". This is an internal-ID field in the geocaches report table. Theres are the available reasons for OCPL

• Cache on private property
• Needs archiving
• Copyright violation
• Other

and for OCDE:

• Cache is gone
• Cache on private property
• Copyright violation
• Description is unusable
• Other

I suggest to start with the common reasons, because providing the different reason sets will be expensive, similar to the attributes definitions. "Other" will do well.

[following5]

This is the proposed definition of caches/report_problem:

https://github.com/following5/okapi/tree/feature/report

[following5]

There is a request from the Opencaching.DE support team, which could be resolved by implementing report functionality in OKAPI. I will submit an interface proposal for these new methods as a Pull Request:

• service/caches/reports/submit: submit a new geocache report
• service/caches/reports/status: query the status of a one or more previously submitted reports
• service/caches/reports/reports: query list of pending reports for a geocache

My proposal is to implement the common OCDE/OCPL "report to Opencaching team" functionality. The OCPL-specific functionality "report to the owner" - which would need email sending through OKAPI - could be added later.

[following5]

Added another proposed method service/caches/reports/reasons to cope for the different available report reasons in OCPL and OCDE code.

[wrygiel]

I read this thread after I reviewed to pull-request :) Wrong order of emails :)

[wrygiel]

Anyway, I didn't even know that such functionality is available in OCPL. Good to know!

[deg-pl]

Maybe we can sync report reasons on OC DE and OC PL sites.
"Needs archiving" and "Cache is gone" - I think they are very similar reasons. Maybe we can chose something common for all sites?
"Description is unusable" - I'm nearly sure, that OC PL sites can add this reason.
We have small problem with "Cache on private property" because polish meaning is wider - something like "incorrect location".

[following5]

I think it will be difficult to sync it.

E.g. "needs archiving" doesn't make sense at OC.de: Reporters here describe what is wrong with the cache, and then the support team decides to

• just inform the user, or
• log "cache needs maintenance" or "listing is outdated", or
• disable, archive, lock or lock/hide the cache.

Also, "needs archiving" is somewhat redundant to the other reasons, which may also require archiving.

So what could be a replacement for "needs archiving" at OCPL?

[following5]

(There are lots of cultural differences between Opencaching.PL and Opencaching.DE. PL is more like GC, having review, nonpublic coordinates, N/A logs ... DE is rather different from GC.)