It's evident from the example given to us by the Choices team that there's a potential issue with takedown actions not modifying the updated date on comment records (see below)
An example of a deletion is:
<item>
<guid isPermaLink="false">155408</guid>
<author>webservices@nhschoices.nhs.uk</author>
<category domain="commentType">deletion</category>
<title>Item 155408 deleted</title>
<description>Item has been deleted and should be removed from your cache</description>
<pubDate>Tue, 29 Jan 2013 18:01:50 Z</pubDate>
<link rel="related" type="application/xhtml+xml" title="Organisation commented on" length="1000" href="http://v1.syndication.nhschoicespreview.nhs.uk/organisations/hospitals/40238?apikey= "/>
<link rel="related" type="application/xhtml+xml" title="Orthopaedics" length="1000" href="http://v1.syndication.nhschoicespreview.nhs.uk/services/types/srv0073/co90875?apikey= "/>
<updated>2013-01-29T18:01:50Z</updated>
<postingid xmlns="http://syndication.nhschoices.nhs.uk/schemas/comments">155408</postingid>
<postingorganisationid xmlns="http://syndication.nhschoices.nhs.uk/schemas/comments">0</postingorganisationid>
</item>
I'd like @evdb to find a takedown request and either prove or disprove this issue. If it's a genuine issue we'll take it up with the Choices syndication team as this is a production service.
It's evident from the example given to us by the Choices team that there's a potential issue with takedown actions not modifying the updated date on comment records (see below)
An example of a deletion is:
I'd like @evdb to find a takedown request and either prove or disprove this issue. If it's a genuine issue we'll take it up with the Choices syndication team as this is a production service.