Page 1 of 1

Archive lead to loss of metadata in the file

Posted: Mon Nov 18, 2013 4:36 am
by bx609311029
I will pick up the XML file to PDF file, but after the PDF file(Set the level path then archive level), the metadata will be lost, how to avoid this piece!

thank you!

Archive lead to loss of metadata in the file

Posted: Mon Nov 18, 2013 1:38 pm
by freddyp
When you pick up an XML, what happens is that the XML file is stored somewhere in Switch's application data folder structure and it keeps a link with the job. This is called a dataset.



When the job reaches the end of the flow it usually looses its unique ID. For Switch it is no longer a job, so there is no link anymore between the job and the dataset (often, but not always an XML file). The dataset file is not deleted immediately, but every so often Switch cleans up the job tickets and datasets that are not linked to an active job.



If you want to keep the metadata at the end of the flow, you can use "Export metadata". This will inject the dataset file into your flow along the Log connection and you can then put it alongside the job (which follows the Data connection of Export metadata).



If the metadata file does not change in the flow you can also use two outgoing connections at the beginning of the flow, one that puts the metadata immediately where you want it, and one that moves it into the flow where it gets picked up as a dataset.



A third possibility is that you put the metadata inside the job. This is of course only possible with file formats that support XMP (e.g. PDF). In a post last week I explained how to do that. The advantage is that you do not have two files, so they cannot get disconnected over time (archive/restore).



Freddy