4 Capture Management with Oracle WebCenter Content

Oracle WebCenter Capture provides scalable document capture focused on process-oriented imaging applications and image-enabling enterprise applications.

The following topics are discussed in this chapter:

Capture is documented in the following guides:

4.1 About Oracle WebCenter Capture

Oracle WebCenter Capture supports high-volume production scanning from a central location and provides a user-friendly web interface to easily capture images from remote locations. It offers industry-standard image capture from scanners and flexible indexing options. Oracle WebCenter Capture is integrated with Oracle WebCenter Forms Recognition to provide automated extraction of data from captured images, and fully integrated with Oracle WebCenter Content's imaging and Oracle WebCenter Content to provide organizations with one system to capture, store, manage and retrieve their mission critical business content.

Batches and documents are the primary drivers of work in WebCenter Capture. In Capture, documents are scanned or imported and stored in batches. A batch consists of scanned images or electronic document files (such as PDF or Microsoft Office files) that are organized into documents and assigned metadata (index) values. Each document shares a set of metadata values.

WebCenter Capture involves the following main processes:

  • Capture: Scan or import batches into a Capture environment.

  • Conversion: Convert non-image documents to a different format.

  • Classification: Separate a batch into its logical documents and assign a set of metadata values to each document.

  • Release: Queue the batch for processing by a batch processor, or release the user's lock on the batch allowing other users to lock and open it.

  • Commit: Write all of a batch's documents (image and non-image) and their metadata in a selected output format to a specific location or content repository, and then remove them from the Capture workspace. This allows the documents to be located and accessed in the content repository via their metadata or contents.

4.2 Capture Client

The Capture client is the end-user application that a knowledge worker or scan operator uses to create batches using scanners or document files imported from the user's system.

The client's main functionality includes:

  • Scanning and importing documents, using the industry standard TWAIN-compliant interface to scan from desktop scanners or other TWAIN-compliant input devices

  • Reviewing, editing, and indexing documents

  • Releasing documents so they can be further processed, checked in to a content repository, or attached to business application records

4.3 Capture Workspace

A Capture workspace represents a complete Capture system, providing a centralized location for metadata, configuration profiles, and physical data for a particular environment. Capture client users create and access batches within the workspace to which they have been granted access. Workspace managers configure and manage workspaces they have been granted access to and control others' access to the workspace.

The Capture workspace provides these benefits:

  • A separate work area useful for managing document capture for a department or division, or even an organization

  • Shareable elements for re-use in multiple Capture components

  • Secure access to workspaces, provided by Capture's user/group restrictions on workspaces

  • Ability to copy a workspace, for easily adapting its configuration for another environment

  • Ability to restrict access to batches created within a workspace by client profile

4.4 Capture Processors

Capture provides the following processors, which workspace managers configure for automation in the workspace console:

  • Import Processor: Provides automated bulk importing, from sources such as a file system folder, a delimited list (text/ASCII) file, or the inbox/folder of an email server. The import job monitors the source and imports at a specified frequency, such as once a minute, hour, or day.

  • Document Conversion Processor: Automatically converts non-image documents to a specified format in Capture using Oracle Outside In technology. Documents can also be merged in various ways during conversion. For example, the conversion processor can convert document files such as PDFs or Microsoft Office documents to TIFF image format.

  • Recognition Processor: Automatically performs bar code recognition, separation of documents, including patch code separation, and automatic indexing.

  • Commit Processor: Executes commit profiles to automatically output batches to a specified location or content repository, then removes the batches from the workspace. Supported output formats include TIFF, image only PDF/A, and Searchable PDF document. A commit profile specifies how to output the documents and their metadata, and includes metadata field mappings, output format, error handling instructions, and commit driver settings.

4.5 Capture Workspace Console

Capture provides a central configuration console in which workspace managers create and manage workspaces and their elements for use throughout Capture. For example, workspace managers create metadata fields, choice lists, and database lookups in the console, then use them in multiple areas such as client profiles and batch processors.

4.6 Capture Security

Capture's user login, access, and authentication are integrated with Oracle Enterprise Manager and Oracle Platform Security Services (OPSS). After authentication, users' permissions depend on their assigned Capture roles, which the system administrator assigns in Oracle Enterprise Manager.