fixmystreet - This is mySociety's popular map-based reporting platform: easy to install in new countries and regions http://fixmystreet.org/

	Commit message (Collapse)	Author	Age	Lines
*	Remove Open311 endpoint to separate repo.	Matthew Somerville	2016-08-23	-1521/+0
\|
*	[Warwickshire] Integration bits during/after visit	Hakim Cassimally	2014-10-16	-34/+71
\| \| \| \| \| \| \|	- Tweaks required to get things working in WCC environment - update Open311 to onsite changes - updated Open311 parameters after WCC's Bentley and County Highways workshop. - ... including ce_cpr_id
*	Open311 tweaks to get round-tripping working	Hakim Cassimally	2014-10-16	-1/+2
\| \| \| \| \|	If https://github.com/mysociety/fixmystreet/pull/792 is accepted then this should be rewritten in terms of that.
*	Open311 Warwick (Exor) Integration	Hakim Cassimally	2014-10-16	-3/+524
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	::Integration::Warwick subclasses ::Integration::Exor refactor request_class and new_request Exor service Warwickshire updates retrieval, with datetimes stubbing out of Oracle constants, for local testing We also edit FMS's core PopulateServiceList routine to hide system fields from FMS: Bromley/Warwickshire send metadata in their services/FOO.xml advising that you can pass, e.g. attributes[easting]. FMS by default shows all of these to the user to fill in, however we don't want the user to supply these, rather they are added by the cobrand. Bromley had an exception for this (keyed by $body->areas->id). We write this more generally for Warwickshire too, keying instead by $body->name (as this is far less likely to be overridden for installs using global or custom Mapit's)
*	Open311 Role for accepting default config file	Hakim Cassimally	2014-10-16	-0/+30
\| \| \| \| \| \| \| \|	See also MooX::ConfigFromFile, but that's underdocumented and seems overengineered -- may be worth implementing if requirements become more complex however. (See also Config::Any, which is well worth doing in future, using YAML only reflects current usage in FMS though.)
*	Open311 Endpoint mySociety extensions role	Hakim Cassimally	2014-10-16	-2/+268
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Get Service Request Updates This requires a new object ::Service::Request::Update, which of course is not part of standard spec. So, in order to make the core not too contaminated by : * the endpoint should instantiate ::Service::Request::mySociety objects which know about updates * have added a learn_additional_types callback from Schema to Endpoint, so that core doesn't need to know about /open311/service_request_update * (but ::Spark knows about the exception for updates... meh, but is 1-line)
*	Open311 Endpoint	Hakim Cassimally	2014-10-16	-0/+666
	Subsystems include * ::Spark encoding conventions for xml/json * ::Schema using Rx to validate form of inputs and outputs, including validation for, e.g., dates and CSV as part of Open311 Handles following paths: * Open311 attributes for Service Definition http://wiki.open311.org/GeoReport_v2#GET_Service_Definition * POST service request * GET Service Requests * GET Service Request Objects: * ::Service * ::Service::Request