Enterprise Content Services
for Every Platform and Application

 

Input sources   Output targets
     
  • Any system or file storage facility via Web Service interface (SOAP/REST) or Web Service API

Direct, ready-to-use integrations (requires add-on)

  • The Windows file system
  • SharePoint Services / SharePoint Foundation
  • SharePoint Server 2007/2010
  • Domino.Doc
 
  • XML blob returned synchronously (via Web Service) or asynchronously (via file system)

Direct, ready-to-use integrations for asynchronous output (requires add-on)

  • Windows Filesystem
  • SharePoint document libraries
  • SharePoint WCMS page libraries (content published as pages)
  • Domino NSF databases
  • MS SQL Server (with full text index information)
  • Any social network supporting Google's OpenSocial interface
     
Supported input data formats   Built-in output Formats
     
  • ASCII and UNICODE text (any language or character set)
  • RTF
  • HTML
  • XML (requires parser customization to accommodate custom markups)
  • Open Office/Open Document Format (odt, ods, opp)
  • MS Office 97, 2007, 2010 (doc docx docm xls sslx ppt pptx pptm)
  • Legacy authoring formats (WordPerfect, LotusSuite, etc)
  • Infopath 2007, 2010
  • Visio
  • Images (jpg jpeg 2000 gif bmp png tif etc)
  • PDF
  • Multi-page TIF
  • Lotus Domino DXL
  • AutoCAD (requires Hyper.Net add-on)
  • SharePoint lists and items
 

Rich Hypertext (for rich-text-based input documents like Word and RTF)

  • Fully-linked, topic-oriented hypertext
  • Revision marks (publish all, reject before publish, accept before publish)
  • Image thumbnailing
  • Image re-sampling and scaling
  • Hyperlink detection and creation
  • Authored style information (captured from the source file and published as CSS statements)
  • On-the-fly broken link detection and auto-enabled/disabled link generation
  • Tables of contents
  • Index (captured from the index entries in the source file)
  • Global content index (of an entire publication set)
  • Glossary terms (all defined terms or first occurrences automatically published as popups)
  • Footnotes and endnotes (published as anchor links)

PDF

  • PDF generation
  • PDF compounding (merging of N source files of any given type into a single PDF with a table of contents) (requires Hyper.Net Compliance Module)
  • PDF watermarking and calculated metadata stamping


PDF/A (requires Hyper.Net Compliance Module)

  • PDF/A generation (from any source including PDF itself)
  • PDF/A compounding (merging of N source files of any given type into a single PDF with a table of contents)

Flash (for fast loading and/or enhanced document security) (requires add-on)

  • Flash renditions of any document
  • Hyperlinks from source file preserved in Flash
  • Generation of table of contents and related topics lists in Flash

Other formats

  • TIF (for archive purposes)
  • Flat HTML (the flat HTML files generated by MS Office)
  • MP3 (text-to-speech)
  • epub (richly-formatted, hypertext eBooks readable by all standard eBook readers)  (requires add-on)
  • XML (representing a complete publication including all formats, zipped)
  • Search text for full text search engines
  • Simple and complex metadata objects (e.g. , taxonomy)
     
Automated processes   Architectural features
     
  • Complete lifecycle synchronization
  • Conversion/publication request transaction audit trails
  • Mass/batch document processing
  • Configurable publishing rules 
  • On-demand conversion/publishing requests (user interaction)
  • Metadata recognition, extraction, transformation, and mapping
  • Context- and metadata-driven conversion, re-purposing and publishing process (configurable rules)
  • Security data mapping
  • Downloader (local or network file system, SharePoint, HTTP, FTP, with or without credentials, with or without proxy server in between)
  • Load balancing and failover for managed (with audit trails) and unmanaged (Web Services interface) transformation and publishing process
  • Real parallel processing with priority handling
  • Flexible third-party conversion tool integration (command-line level)
  • Load balancing and failover (Workload Manager)
 
  • Web services interface for submitting conversion/publication requests
  • Ready-to-use integrations for today's popular information management platforms (SharePoint, Lotus Notes, Windows File System, etc.)
  • Open Web Services interface API for creating integrations for less commonly used systems
  • Content can be published into a specific output target or returned as a zipped XML blob
  • Requests can be submitted asynchronously (does not wait for a return) or synchronously (waits until the XML blob can be returned or the output target has been populated)