Hmmm.... That does look interesting. Let me dig into this and find out.
Are you assuming that the act of adding a post to a blog should change the updated timestamp on the blog? The characteristics of the blog itself (like it's title) are not updated by the act of adding a blog post. So, the updated timestamp accurately reflects that you have not adjusted any characteristics on the blog itself since it was originally created.
Each post will have its own "published" and "updated" timestamp that reflect when that particular post was created or last updated -- but this has no effect on the updated field on the blog itself. By the way, the same principle applies to adding content to a group or space or project -- the content object has its own date, but adding (say) a document does not affect the updated timestamp of the place itself.
"adding (say) a document does not affect the updated timestamp of the place itself."
A lot of places are updated daily, so either Ryan has to too much time ar a lot of people are starting or stopping to follow or (un-)liking places. I'll look for more details.
https://community.jivesoftware.com/community/developer/plugins/clearspace/content are a good examples.
REST API: "updated" : "2013-03-19T16:41:35.925+0000"
Web page: Jive Gamification Module.How do we enable this feature? ... March 19, 2013 5:41 PM (the 1h offset may be due to my locale settings).
REST API: "updated" : "2013-03-26T20:36:32.583+0000"
Web page: Customizing the Search Bar ... March 26, 2013 9:36 PM
While there is the very small possibility that one did modify the "Jive Forum" and the "Clearspace" space at the same time as one did create a post I do not believe that this was the case.
I am not understanding what you are asking.
- The ".../support/jive_forums/content" and ".../plugins/clearspace/content" links retrieve content, not places.
- The "Jive Gamification Module: How do we enable this feature?" is a discussion, not a place.
- The "Customizing the Search Bar" page is a discussion, not a place.
So, in none of these cases would the updated field of the corresponding place actually get rendered in the UI.
Also, the UI will typically report timestamps of the latest activity in a place, because that tends to be what people are interested in. If you want to know that through the API, the simplest thing to do is poll the activity stream for that place and use the timestamp of the first returned activity (which will be the latest, since they are in reverse chronological order).
It seems that the 'updated' field of spaces is updated to match the last activity update.
For blogs this is not the case.
So there is a different behaviour of places regarding the 'updated' field. That's odd.
To avoid additional API calls it would be great if 'updated' would always contain the date of the latest activity.
Using the activity stream does not work out of the box - one may need to add a filter. It returns also activity which did not occur in the place. For example:
The activity stream contains as the last update the message above where I did @mention the place.
The contents link https://community.jivesoftware.com/api/core/v3/contents?filter=place%28https%3A%2F%2Fcommunity.jivesoftware.com%2Fapi%2F… seems to be the better choice, and then the updated dates of place and content do match ("updated" : "2013-03-19T16:41:35.925+0000" vs. "updated" : "2013-03-19T16:41:35.884+0000")