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; } } }

importing data records

System

Hi, we are looking for some help in importing data records (including associated metadata) from version a. (an interwoven teamsite in location 1) to version b. (an interwoven teamsite in location 2 - which is very far away...)

Can anyone recommend a sensible way of being able to ship the data (ideally on cd!!).

All help would be appreciated, as I have been going round in circles trying to get this to work

Thanks in advance

Find more posts tagged with

Comments

Migrateduser

Put the backing store on a CD.

nipper

>Put the backing store on a CD.

I think you would be better putting an edition (or the Staging area) on a CD.

You will also need the script to get EAs so they can be reattached when the code is imported.

ALso, you may want to make a readonly branch to do the imports. If this content is changed
in 2 places at once, it may require merging, so a different branch will help.

stefanmaier

Hi,
we also had the same problem. We wrote a little perl-script which does the following:

Input Parameter:
Directory to be exported

Function:
go through the directory with File::Find
for each file you get all extended attribs with "iwextattr -ul $yourfilename"
for each extended attribute form the file you print "iwextattr -s $attrib=$value $file"

if you pipe the script output into a file called setattribs.cmd (or setattribs.sh),
you can simply execute this batchfile on your second TS-server and set your attributes there after
you copied the files and dcrs from TS-server 1.

Cheers

Stefan

Adam Stoller

As a follow-on to taalgaard's suggestion - if you have licenses for MultiStore - you can cut an edition on the branch(es) you wish to export, create a new store (iwstoreadm), copy the latest edition of the branch(es) to that new store (iwmigrate) and then put the new store on the CD. The new store should be significanly smaller than the full store, but it will contain all the files and their EAs in the new store.

Put the CD in the other server, transfer the store onto the local disk, register the new store (I believe you can do this with iwstoreadm, otherwise it may be a setting in iw.cfg), and then copy the data from the new store to the default store (iwmigrate).

As licensing for multistore is not cheap (unless relating it to licensing for a new server) - using the methods described by Nipper and stefanmaier is a reasonable way to go.

Another alternative, if you can connect through ports between the servers, is to use OpenDeploy 6 (soon to be released?) which provides for deploying content *and* EAs (without a DNR script).

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com