Hi,
I work for mySociety in the UK and I've been adding support to FixMyStreet for
posting Open311 requests to other systems. Having been working with it for a
bit
there's a few things I can't see how to do in the current version and we'd be
quite keen on seeing added to Open311 in the future.
One of the things we'd like to be able to use Open311 for is to get updates
about
requests back into FixMyStreet from the system we're reporting it to. I see
there
was a discussion on the list a while back about adding an update request call
and
that would certainly be useful for us to send updates made on FixMyStreet into
a council/authority system, however I don't think it's quite the same thing as
we're
looking for.
What would be nice is a way to tell a system we're posting a service request to
what our
internal id was and where it could send updates to and then the update
mechanism discussed
earlier could be used to post back updates. Clearly this would require us to
provide an
api key to that system but as we'd have to ask for one to post requests in the
first place
I don't see that as a barrier. I'm not sure if all the information to make the
update should
be included in the service request, or if just enough to identify where it was
from and
the rest was stored else where.
Is this something that other people would use?
At the moment I've got round this by polling /requests.xml but this is not
likely to
be a very scalable solution, particularly as there's no way to query by update
time.
On which note it would be handy to be able to limit it by update time, and
indeed to
have a way of requesting the status history of a particular request. Something
like
GET /history/service_request_id.xml
<updates>
<update>
<datetime>2011-08-14T09:21:24-00:00</datetime>
<status>open</status>
<status_notes>Scheduled for repair w/c Sep 5th</status_notes>
</update>
<update>
<!-- etc -->
</update>
</updates>
Do these seem like the sort of things that would be useful in a future version
of Open311?
Having said all that I'd like to add that the spec as it stands is very helpful
and been very pleasant to implement.
Thanks
Struan
I work for mySociety in the UK and I've been adding support to FixMyStreet for
posting Open311 requests to other systems. Having been working with it for a
bit
there's a few things I can't see how to do in the current version and we'd be
quite keen on seeing added to Open311 in the future.
One of the things we'd like to be able to use Open311 for is to get updates
about
requests back into FixMyStreet from the system we're reporting it to. I see
there
was a discussion on the list a while back about adding an update request call
and
that would certainly be useful for us to send updates made on FixMyStreet into
a council/authority system, however I don't think it's quite the same thing as
we're
looking for.
What would be nice is a way to tell a system we're posting a service request to
what our
internal id was and where it could send updates to and then the update
mechanism discussed
earlier could be used to post back updates. Clearly this would require us to
provide an
api key to that system but as we'd have to ask for one to post requests in the
first place
I don't see that as a barrier. I'm not sure if all the information to make the
update should
be included in the service request, or if just enough to identify where it was
from and
the rest was stored else where.
Is this something that other people would use?
At the moment I've got round this by polling /requests.xml but this is not
likely to
be a very scalable solution, particularly as there's no way to query by update
time.
On which note it would be handy to be able to limit it by update time, and
indeed to
have a way of requesting the status history of a particular request. Something
like
GET /history/service_request_id.xml
<updates>
<update>
<datetime>2011-08-14T09:21:24-00:00</datetime>
<status>open</status>
<status_notes>Scheduled for repair w/c Sep 5th</status_notes>
</update>
<update>
<!-- etc -->
</update>
</updates>
Do these seem like the sort of things that would be useful in a future version
of Open311?
Having said all that I'd like to add that the spec as it stands is very helpful
and been very pleasant to implement.
Thanks
Struan