Hi,
We have asset list pages that display the last updated dates for the assets in the list. How can I get the last updated date to distinguish between a major and minor update? I often do small changes to the assets - eg fix typos, change format - and don't really want these recorded as the last update. Are there date keywords associated with the version controls I can use?
Thanks
Catherine
There is only one updated date for an asset so you wont be able to print dates for major and minor updates.
When you create an asset the first time you make it live the version number is set to 0.1.0 and a published date is set, I am not sure why it is set as the first minor version rather than major. You then need to manually set the major version in the settings screen. The published date is not updated by macro or minor increments, or major increments, so if you use one of the publish date keywords you should get what you want. When you do what you would consider to be another major update you would need to go through a process that updates the published date, like going through safe edit or make the asset under construction then live again. Oh, and you will need to manually update the major version in the settings again if you want that to keep in step. I suppose you could create a trigger to update the major version if you want to get a bit of automation in there. So, doing all of that will give you exactly what you are after 
Cheers
Shane
Thanks Shane. Unfortunately the review process (ie change status to "up for review", take a look at he page, then change back to "live") republishes the asset, and updates the published date, even though I may not have really changed it. I guess I will have to manually backdate the published date.
It would depend on what corporate governance rules you were bound by but in government I believe that having a set review period for a page, reviewing it on that date and approving it as current would actually mean that it is deemed to be re-published on that date and by the person who approved it on that date, irrespective of whether there were any changes or not.
If you are not bound by that type of governance then using up for review is usually done to manage keeping the site current, in that case you would have to manually set the published date back because the published date is being driven by the status change of the asset and not the content changes.
In any case, using published date and sound logic behind your versioning will get you what you originally asked for, but using last updated date will get you what Greg has verified.
Cheers
Shane