Promoted from WebNative open thread
If you create a new asset from an existing asset, how do you get the metadata to follow into the new asset? I’m using Triple Triangle’s InDesign extensions to track job information: art director, copywriter, etc. This comes from our job management system and populates SLUG fields and XMP data fields in Venture automatically. This data is then searchable in Webnative and Bridge.
I’m also using DALiM TWiST for workflow automation. If I export my PDF from InDesign, my job information travels into the resulting PDF. But if I “print” my PDF via FullPress or DALiM, the data doesn’t travel into the new asset. I’d like to use my PDF as my medium for online approval, but I don’t want to have to manually make a PDF on each round or manually apply a metadata template in an Adobe product. I’d like to know what processes others have found that allow transfer of asset data in this situation. In a fashion that I can work into an automated workflow. Suggestions? Findings? Thanks.
If you “print” the xmp metadata will never make it.
Best way to get it to work is by exporting PDF/EPS files.
However…
In theory, you could modify your PPD – to include various variable data (the data would be set from the print window) which could be read by TWiST. TWiST,in turn, would move the variables into valid XMP fields. Altough, the current incarnation of twist (that I’m using) will only create these variables for the duration of that job instance.
Now, to really ratchet this up in complexity – the twist created xmp metadata could be written out to a database (mysql, postgres) which xinet venture would read and inject into the file (once the file lands in the xinet server).
There are a couple of steps I’m missing – but, you get the idea.
So, creating the above beast is “theoretically” possible – I would suggest just exporting the PDF/EPS with the XMP metadata.
Going Postscript will always result in XMP metadata loss.
The only way to keep your metadata along is to stay PDF all the way.
The current releases of TWiST will maintain XMP throughout the worklfow and can even use / add metadata fields with the InsertMetaData tool.
In conjunction with FullPress PDF-IR you should be able to achieve a complete metadata transparent worflow from beginning to end.
Hello,
I am not sure with .pdf or .eps files that you mention above but we have noticed the following behavior with Xinet when downloading assets that are transformed from the original. When users are downloading assets from Portal and use a Batch Image Order or the JPG download button from the cart in Portal, the assets are downloaded and apparently have all custom XMP data stripped. We have found that upon closer inspection of the raw data in the “new” files the XMP packet is still there (albeit fragmented) and that when the assets are opened and then re-saved by Photoshop, the XMP packet is somehow repaired and the XMP data becomes available once again. I am not sure why Xinet has not addressed this issue, but the fact that the XMP data is still present in the assets seems to suggest that the code Xinet is using to render the new assets is not correctly rebuilding the XMP so that Bridge can interpret. It is only when Photoshop opens and reads this fragmented XMP information that the asset can be re-saved and the XMP is again fully intact. I do hope that Xinet will address this issue soon as the lack of our custom XMP metadata in transformed assets is real deal-breaker.
~David
Какие нужные слова… супер, отличная мысль…
This comes from our job management system and populates SLUG fields and XMP data fields […….