aboutsummaryrefslogtreecommitdiffstats
path: root/perllib/Open311/GetServiceRequests.pm
Commit message (Collapse)AuthorAgeLines
* Record service as Open311 for pulled-in reports.M Somerville2020-10-02-0/+1
|
* [Open311] use staff categories when fetching reportsStruan Donald2020-08-06-1/+1
| | | | | | | At the moment if you fetch a report in a staff category it will still be created but will be in the Other category. Given that some staff categories are marked as private this can allow reports that should be private to be put in a public category.
* Rewrite open311-update-reports to share code.Matthew Somerville2020-07-06-2/+1
| | | | | Make GetUpdates and GetServiceRequestUpdates share a common base; spot all visible states.
* Combine and improve fetch-comments/reports scriptsMatthew Somerville2020-04-02-9/+13
| | | | | Make them take start/end hour arguments, cope if only one given, optional body, and combine them together in one `fetch` script.
* [Hounslow] Don't fetch non_public reports at all from Open311Dave Arter2019-06-04-1/+4
|
* [Open311] Always mark fetched reports non_public for non_public contactsDave Arter2019-06-04-0/+1
| | | | | | This change ensures that a report fetched via Open311 for a non_public category will always be marked as non_public even if its Open311 XML doesn’t explicitly include the non_public tag.
* Fix some incorrect timezone code.Matthew Somerville2019-05-02-6/+2
| | | | | | | | | Times in the database should be stored in the application server's local timezone, by e.g. using `current_timestamp`, or by setting that timezone explicitly before storage (the database columns are all without timezone so any timezone info is silently ignored). Reports & updates fetched via Open311 and offline updates were being put into the TIME_ZONE setting if present, meaning they were stored incorrectly for future usage.
* Factor to common FixMyStreet::MapIt call.Matthew Somerville2019-04-04-6/+2
|
* [Open311] run cobrand description filtering if availableStruan Donald2019-01-04-0/+4
| | | | | When fetching reports run them through the cobrands filter_report_description method if it exists.
* [Open311] handle non_public field when fetching requestsStruan Donald2019-01-04-0/+3
| | | | | | | | | If there is <non_public>1</non_public> tag in an incoming service request then set the created report to non_public.
* [Open311] Improve handling of created/updated datetimes of fetched reportsDave Arter2018-11-20-37/+42
| | | | | This should reduce the incidence of the ‘Problem id X for Y has an invalid time, not creating’ cron errors we’ve been seeing.
* [Open311] No questionnaires on fetched reports.Matthew Somerville2018-09-18-0/+1
|
* Don’t crash when fetching Open311 requests with missing descriptionDave Arter2018-08-17-1/+1
|
* better diagnostics for rejected Open311 problemsStruan Donald2018-04-25-1/+2
| | | | | Add a more helpful error message when a problem fetched over Open311 is rejected for problems with the date.
* [Open311] fetch_all option for open311 problem fetchingStruan Donald2018-04-11-7/+17
| | | | | | | | | If a body has a `fetch_all_reports` setting in the extra metadata then all reports are fetched over Open311 and processed regardless of age. This is useful for bodies where the API endpoint always returns all the reports as it suppresses the error messages you would otherwise get about reports with invalid dates.
* Correctly assign problem categories in GetServiceRequestsDave Arter2018-04-04-1/+1
| | | | | | | | FMS uses the Contact->email field for the Open311 service code, and the Contact->category field is the user-friendly service name. The wrong value was being compared previously, resulting in all fetched problems being assigned to the 'Other' category.
* Default to only one hour for GetServiceRequestsDave Arter2018-04-04-1/+1
| | | | Certain endpoints can be slow, so fetch fewer reports at a time.
* Default to last two hours in GetServiceRequestsDave Arter2018-04-04-1/+7
| | | | Also adds script for fetching the last 24hrs of reports
* add convert latlong option to open311 body adminStruan Donald2018-03-29-0/+1
|
* optionally convert from EPSG:27700 to WGS84 on report importStruan Donald2018-03-29-2/+7
| | | | | | | When pulling reports in over Open311 it's sometimes useful to be able to accept reports with Easting/Northing rather than latitude/longitude. This adds an option to GetServiceRequests to convert them as they come in.
* fetch new problems over open311Struan Donald2018-03-15-0/+168
This enables the display of existing reports from the back end on FMS if the body is configured to do this. Reports will not be created if they are missing an id, a lat or a long, if the lat/long is outside the area covered by the body, if there is already a report with a matching id, or if we can't parse out the request time.
generated by cgit v1.2.3 (git 2.25.1) at 2025-04-26 16:55:38 +0000