Probem in moving files including version history

SoulReaver

Hi ,
We need to archive the files depending on the expiry date(EA). The file gets expired if expiry date is less than current date. The expired files has to be moved to a folder including version history and EA of the files and delete the original files. We tried using 'iwcp' command which copies the file and OS del command to delete the original file . Everything is working file, but the version history is lost . Is there any way to move the files including the version history.

ISCBorisB

Hi , We need to archive the files depending on the expiry date(EA). The file gets expired if expiry date is less than current date. The expired files has to be moved to a folder including version history and EA of the files and delete the original files. We tried using 'iwcp' command which copies the file and OS del command to delete the original file . Everything is working file, but the version history is lost . Is there any way to move the files including the version history.

TS maintains History per Branch. The mechanism is Edition Publising.
In other words, you create a collection of Historical references
(a snap-shot of current STAGING State) every time you Publish new Edition.

I hope it is clear from above that there is absolutely no way to really "Copy
File Versions History" anywhere. Main reason it, File history is an integral part
of the Branch History (Staging + Editions). Individual File Versions can be extracted
separately but they can not be (re)created independently from other Files.

In theory, you can perhaps "mimic" Branch A History in the Branch B. For example, you can
intercept A Publishing event, identify "Edition(N) / Edition(N-1) Deltas, copy or Deploy
them to some "B" Workarea, Submit to Staging and Publish Edition(N) in "B" as well.

In practice however this is IMO an exercise in futility. TS already has elaborated Versioning
mechanisms for you. Use them correctly. Assets belong to the Branch, history and all. If you need
an ability to extract them for compliance or whatever, come up with API / GUI to do that.

If you want to maintain history in the dedicated Branch, come up with Workflows (or any other
mechanisms of your liking) to copy/submit/publish modified collections there (eg, use Staging
but never Publish in the *Transitional* Branches, only in the *History* Branch). This way when
you finally remove a File from the *Transitional* it's history would be already accumulated in
*History* Branch - along with the Versions of other Files, etc

Makes sense?