Need help moving Documents from one DB to another while keeping docnum the same.

Hey folks,

Title sais it all. We're trying to build a tool that will move over workspaces and all their contents from one database to another (we're looking at an archive solution)

We've been able to do most of the above using the API. Problem is that when we create new documents in the archive database they get new numbers. Anyone out there do the same but find a way to keep the same numbers?

I can insert and modify the worksite database directly from sql so there's a work around, but would rather use the API.

Thoughts?

Note:
I am trying to find more information on Worksite Archive Manager. In the documentation i have found, i see that if you use multiple databases it will let you put the docnum in a custom field. But in a single live db to single archive db environment, would that mean that the docnum is the same in the archive db that it was in the live db?

Find more posts tagged with

Comments

taibooz

No, that's the limitation of the SDK. You need to purchase the WorkSite archive manager in order to keep document number the same when moving content from one database to the other

DaleN

The Monitor program has the ability to Relocate documents to another library while keeping the same document number. This utility works through the WorkSite Server but the API calls it uses are not exposed and it knows nothing about workspace structures.

This might be too messy but one option could be to use the Monitor program to move the documents and profile information, then have your custom utility build the workspaces, check the folder contents on the source library then match up the folders and documents on the target library.

danielguzman

After speaking with some consultants who offer products that accomplish what worksite archiving offers, it seems they copy the files and during the process go behind the API to change numbers.

probably explore that option, dont endorse bypassing the API but in this case it's the only solution without buying the worksite product.

jny

After speaking with some consultants who offer products that accomplish what worksite archiving offers, it seems they copy the files and during the process go behind the API to change numbers.

probably explore that option, dont endorse bypassing the API but in this case it's the only solution without buying the worksite product.

You cannot use the API's distributed with the WorkSite iToolkit to set document numbers or versions - this is determined by the server as documents are numbered incrementally.