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

Documentum Conversion

System

Hello Techies--
Has anyone migrated a documentum docbase over to WorkSite? If so, any caveats, special concerns, etc. to look for? Best practices?

Warm regards,
Paula

Paula DiTallo - Middleware Architect/ .NET Developer
plditallo@metro-design-dev.com

Find more posts tagged with

Comments

Migrateduser

We have done documentum to Worksite conversions before. I believe that the last version we did was 3.17 and the document storage string is extremely convoluted. The solution was taking the negative integer associated with the document and converting that to a hex then parsing for the document.

good luck.

Migrateduser

We are at the near-end of this project with most of our conversion tasks done, including the convoluted versioning issue. I do, however, have one question for the foum for anyone that may be familiar with Documentum conversions or conversions of any doctypes into WorkSite in general.

Documentum is storing Keywords with the document's meta-data. Basically, the Keywords allow for more expedient searches which the end users drive by what gets entered. What would the best practices be for converting the equivalent into WorkSite? I do realize that iManage's powerful indexing engine will all but eliminate the need for entering keywords, however, my first immediate take in the context of a doc-2-doc conversion, involves using one of the unvalidated string custom fields/tables to dump the key words into, then alter the dialogs to accommodate the label/edit box. As I mentioned, it is the end of the project--so not surprisingly, we've used up all of our unvalidated string custom fields/tables!:-) Since this custom table option is not really available, I'm leaning toward heavy end-user training on creating search directories based on keyword searches.

WIth that said, I'm no iManage/WorkSite administrator--so--I'd be very interested in a best practices approach regarding the indexing process.

If some of you have suggestions beyond what I've immediately addressed or have a different approach altogether, I'd like to hear from you! I'm always open to new ideas! (or even old ideas I don't know about!;-) )

Warm regards,
Paula DiTallo

Paula DiTallo - Middleware Architect/ .NET Developer
plditallo@metro-design-dev.com

Edited by plditallo on 09/29/04 09:32 AM (server time).