GCI Power Tools for Content Export

The real leverage and value of ECM systems are driven by the way the contents of the system are used. Faster business processes, better business decisions, more effective collaboration are all dependent on ECM system outputs. Those data deliveries come by way of user interfaces in business applications and other means such as printed reports. Sometimes, the value of those system outputs is found in the ability to extract data (documents, files, images, etc.) for use in a system managed by an entirely different organization. The keys to success in such a setting are found in the ease with which the data objects can be selected and the level of control over how the final data set is formed. GCI Power Tools for Content Export (PTCE) is designed to exactly meet these requirements.

PTCE facilitates the extraction of documents and metadata from Livelink in a format that can be provided to clients or other stakeholders. For example, a Contract Research Organization (CRO) or a Pharmaceutical Services Company could easily aggregate their scientific findings and results and prepare them for delivery, further extending the value they provide to their clients. Another example is when companies need to submit a collection of documents to a governmental body for compliance to a regulation. Downloading the collection and its metadata in an intact XML can facilitate the
delivery of such a collection.

PTCE’s user interface is similar to that of GCI Power Tools for Deployments and is designed for end user use. PTCE allows end users to mark files for export, define data transformation parameters in a style sheet, and then export the data and move them to a location chosen by the end user. Also available is an Agent Scheduler Extension that supports the advanced scheduling of exports (monthly, for example).

PTCE v2 Supports:

• A user-friendly interface for ease of export configuration
• Complete control for the end user to define the Livelink documents or containers to be exported
• Optional end user specification of an XSL style sheet to transform the metadata format
• The ability for the end user to initiate the export after defining requisite parameters
  Error corrections of characters that could cause OS naming conflicts by being replaced with underscores during the export
• Placing the individually selected documents at the root directory containing the export after completion of the export. The selected containers will maintain their taxonomy structure and consist of all documents and containersfrom the selected container on down
• The production of an XML file of metadata. If an optional XSL style sheet was specified, another document will be produced by applying the XSL file to the XML file
• The ability to designate a location to which the exported content may be moved in preparation for delivery of the data to their intended recipient after the export is done
• Exporting compound documents and shortcuts
• Filtering the export based on a date range, category attribute value and/or mime type
• Additional logging that shows an export summary
• Document versioning and audit trails are optional to include with export
• Files are reserved at export time and unreserved when export is completed

System Requirements

• Open Text Content Server Version 9.7.0 or later
• Database: Oracle or MS SQL in versions supported by Open Text Content Server 9.7.0 or later
• GCI Performance Agent 1.1 or later

Also please download our GCI Power Tools for Content Export document
and/or contact us.

<< back