nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to move MKS files with version info into TeamSite?

citizen

I've got an MKS repository filled with gigs of content in XML format and related "properties" files in XML format. Most of these have extensive version history. I've got to get these files into TeamSite and wonder if the MKS adapter in OD 6.0.2 SP1 could make this easy to do.

I'm not as yet familiar with MKS and how it versions files -and- do not see anything in the OD602SP1.RN PDF regarding MKS "versions" per se. Has anyone had any experience with this yet or enough background in this to advise if the the adapter could support automagically copying a file with version info from MKS into TeamSite? The ideal result would be to see "version" info for any given files migrated from MKS just as if it were submitted to TeamSite staging the same number of times it was versioned in MKS... and to be able to revert to any earlier version.

The next question is: How will the size of the resulting TeamSite repository compare to the MKS repository give the different ways both systems store file deltas?

Thanks in advance to anyone chiming in on this...
-Gene

Find more posts tagged with

Comments

Adam Stoller

I've got an MKS repository filled with gigs of content in XML format and related "properties" files in XML format. Most of these have extensive version history. I've got to get these files into TeamSite and wonder if the MKS adapter in OD 6.0.2 SP1 could make this easy to do.

I'm not as yet familiar with MKS and how it versions files -and- do not see anything in the OD602SP1.RN PDF regarding MKS "versions" per se. Has anyone had any experience with this yet or enough background in this to advise if the the adapter could support automagically copying a file with version info from MKS into TeamSite? The ideal result would be to see "version" info for any given files migrated from MKS just as if it were submitted to TeamSite staging the same number of times it was versioned in MKS... and to be able to revert to any earlier version.

The next question is: How will the size of the resulting TeamSite repository compare to the MKS repository give the different ways both systems store file deltas?

Thanks in advance to anyone chiming in on this...
-Gene

I don't think OD, by itself, is going to help you too much here - if you want to preserve the history you're going to have to do a lot of scripted steps and the date/time-stamps on the historical versions will not be transferred as such.

In many ways this is like trying to switch from using TS on Windows to TS on Unix (or vice-versa) and trying to preserve all historical information where there is no mecahnism for migrating the backing store as a whole - it essentially comes down to something like this (off the top-of-my-head, some steps may be missing):

Repeat the above process for each version of each file you wish to transfer.Depending on your needs you may be able to batch things together a bit, but basically you're dealing with file-by-file / version-by-version transferring. If you do this in a breadth-first manner instead of depth-first, you may also want to include the creation of editions for "named" or "labeled" versions from the source repository.I'd suggest spending a bit of time becoming familiar with the tools for the source repositoy, as well as those available for TS (if you aren't already) and then spend more time creating a thorough design document performing little tests along the way to validate your design - and then start doing larger and larger tests until you feel reasonably confident in your implementation before actually doing the whole thing for "real".Where OD's adapters (and/or DNR scripts) might come into play is being able to somehow automate the interactions on both the source and target side of the transfer ... but I haven't had any experience using the adapaters so I'm not sure how well they lend themselves to this.

Bill Klish

I will add to ghoti's reply that you can use the MKS adapter to retrieve tagged versions of files and or releases/versions. We use the cvs adapter to pull project sets out of cvs and take snapshots of them as we perform application builds.

I am not sure you would be able to retain all of the who submitted it, etc. information and comments without some heavy scripting, but if all you care about is the various histories of the files, I believe an opendeploy script that utilizes the adapter could work pretty well, but you would have to recursively retrieve from the repository.

I am pretty sure this will not be an easy process, but the adapters should make it a little less "painful"

citizen

Thank you ghoti and bk99nd for chiming in. If I've got to do some "heavy lifting" to create a little system to do a "deep copy" of an MKS repository into TeamSite it's good to have independent opinions and suggestions to guide me (and help justify the effort to management)... another one of the great things about DevNet.

-Gene