We have lots of experience in this field. We have tools that adapt LiveLink to Documentum and perform export-mapping-import-file transfer functions, either en-mass or selectively and also two way in manual, scheduled or dynamic modes. Open Text has two main interfaces for this. You can use the query language and API to export the objects or you can use a built in exporter to dump content out to a folder structure with XML files. You can either use the export facility and monitor the export folder structure or "reach in" with the api and query language and extract the content. We can handle either mode. From the Open Text admin's perspective it is probably better to use the export function. www . qtility . com or mike . clarke (at) qtility . com

We have lots of experience in this field. We have tools that adapt LiveLink to Documentum and perform export-mapping-import-file transfer functions, either en-mass or selectively and also two way in manual, scheduled or dynamic modes. Open Text has two main interfaces for this. You can use the query language and API to export the objects or you can use a built in exporter to dump content out to a folder structure with XML files. You can either use the export facility and monitor the export folder structure or "reach in" with the api and query language and extract the content. We can handle either mode. From the Open Text admin's perspective it is probably better to use the export function. www . qtility . com or mike . clarke (at) qtility . com