Asset updated date discrepancy

#1

I'm finding discrepancies between an asset's "Updated:" date on the details screen and the date printed on the front end via %asset_updated_readabledate%.

 

The Details screen shows me the true date when the asset was last updated and the keyword replacement shows me today's date.

 

Some changes were made to the assets metadata today, so confused why the front end doesn't still print the updated date displayed on the details screen.

 

Cheers in advance for any help to clear up my (mis?) understanding. 

(Bart Banda) #2

What type of asset is it? Can you provide a bit more information about your implementation and how and where you are printing the keyword? I think only file assets display the updated date on the details screen, and this is not the updated date of the asset, this is just the date the file itself was last updated. 

#3

What type of asset is it? Can you provide a bit more information about your implementation and how and where you are printing the keyword? I think only file assets display the updated date on the details screen, and this is not the updated date of the asset, this is just the date the file itself was last updated. 

 

Thanks Bart,

 

To answer your questions:

 

PDF asset, being displayed via an Asset listing, keyword is coded within Asset Listing's default type format.

 

Hoping to replicate the PDF's last updated date indicated on the details screen as I need to reflect when the document was last up-loaded/updated with a new version. 

(Bart Banda) #4

Ah ok, well the date you see on the details screen is the date it was last uploaded against the asset, so if you change status or change metadata, the standard asset updated date will get updated. Not sure if you can do it with a trigger somehow instead and change a metadata value every time a new file is uploaded. 

#5

Thanks Bart, I've used a trigger to manipulate dates before. But had to do these singularly for each unique date which is painful. Just wish there was a keyword that would simply mirror the date on the asset's details screen.

 

To explain my situation, I have 100's of PDFs loaded in our system. As I aim to provide additional details via metadata for each document, I'm retro-fitting metadata schemas to these PDFs.

 

Problem is, as soon as I add the metadata schema or update the actual metadata on a PDF - this is interpreted as the asset being updated and prints the current date on the front-end (via %asset_updated_readabledate%).

(Bart Banda) #6

You could try creating a trigger that changes a metadata date field when asset attributes are changed. That should only change the date value when attributes on the details screen are changed and not when metadata is changed. But offcourse, it will also trigger if you change the asset name or status as well. But might be worth looking into. 

#7

Thanks Bart, I'll have to look into this and will add the keyword replacement %asset_updated_asPerDetailsScreen% to my wishlist.

#8

You could try creating a trigger that changes a metadata date field when asset attributes are changed. That should only change the date value when attributes on the details screen are changed and not when metadata is changed. But offcourse, it will also trigger if you change the asset name or status as well. But might be worth looking into. 

 

I gave it a go Bart, but from what I can figure I won't be able to get this to work due to:

a: You still need to specify a date to change the metadata field to, within the trigger action. 

b: Not all our assets have a metadata schema attached.

 

I have modified 'front-end' publish dates via a trigger in the past, but requires each asset to be done individually.