Glossary

access roles

Oracle Content DB security is based on access roles, which specify what kind of access a user has to files, folders, Libraries, Containers, and links in Oracle Content DB. Each role is made up of a set of permissions. A permission represents the ability to perform a specific Oracle Content DB action or operation.

Administration Mode

Oracle Content DB Administration Mode provides access to application administration functions, such as allocating quota and assigning roles.

application administration

Oracle Content DB application administration involves managing users, quota, Libraries, security, categories, and content.

approvers

An approver, in a workflow request, is a specified user who must either approve or reject the request.

category

A category is a unit of information by which files and folders may be classified. In Oracle Content DB, users associate metadata with a file or folder by assigning one or more categories to it. Users can use categories to create intelligent searches for files and folders. Categories may be divided into subcategories, and may have one or more category attributes. Categories are created and configured for the Site by Category Administrators.

category attributes

A category attribute is additional information added to define a category in Oracle Content DB.

check-out/check-in

One mechanism for creating a new version of a file is check-out/check-in. Each file can be checked out by only one user at a time, enforced by a locking mechanism. Checking in a file creates a new version from the working copy, and then destroys the working copy. The new version becomes the latest version of the file, and like any document version, is immutable and thus cannot be further updated. The lock acquired at check-out is released, allowing other users to check out the document.

Container

A Container is a special type of Oracle Content DB folder. The Container provides users and administrators with greater flexibility in organizing files and folders. For instance, Containers could be used to organize the Site by a company's business divisions or office locations. Only Libraries and Containers can be stored in a Container.

Library

A Library is a special type of folder in Oracle Content DB. Unlike Containers and regular folders, each Library has a Trash Folder and an allocated quota of disk space.

metadata

Data that provides information about, or documentation of, other data managed within an application or environment. In Oracle Content DB, users associate metadata with a file or folder by assigning one or more categories to the file or folder.

Oracle Workflow

Oracle Workflow is a system that supports business process definition, automation, and integration.

Personal Library

A Personal Library is a Library that is set up for, and managed by, a single user. Personal Libraries may or may not be available, depending on whether or not the User Administrator has enabled Personal Libraries in your Oracle Content DB Site.

quota

Quota is the amount of disk space allocated for a Library.

Site

The Oracle Content DB Site is an organizational entity that is used to manage settings for all Oracle Content DB users. The Site has an allocated quota that specifies the amount of content (in MB, GB, or TB) that can be stored in the Site.

system administration

Oracle Content DB system administration involves the following tasks:

Planning for Oracle Content DB deployment
Installing and configuring Oracle Content DB
Optionally customizing their Oracle Content DB deployment by enabling an antivirus solution, BFILE archiving or aging, and other options
Managing the Oracle Content DB domain, nodes, services, and servers
Performing system tuning and troubleshooting
Managing the Oracle Content DB Site
Managing custom BPEL workflows

UTF-8

A character encoding format used to represent a sequence of 16-bit Unicode characters with an equivalent sequence of 8-bit characters, no one of which is zero. This sequence of characters can be represented using an ordinary C language string. If your operating system does not support UTF-8, you can enter another Distributed Authoring and Versioning (DAV) character encoding format in user preferences.

version-control

A version controlled file has a version history, consisting of a series of versions. Each version has both content and metadata for the document. Updating the document's content or metadata causes a new version to be created. In general, once a version is created it is immutable. If versioning is enabled for a folder or Library, and Manual Versioning is selected for the Versioning Model, users can create a version-controlled document only through explicit check-out and check-in operations. If versioning is enabled for a folder or Library, and Automatic Versioning is selected for the Versioning Model, updates to a file's content or category information will result in the automatic creation of a new version.

version history

Information about the saved versions of a file. Accessible from the Version Properties window for a file, the version history displays the working copy of the file and a table of the file's saved versions.

Web Distributed Authoring and Versioning (WebDAV)

WebDAV is the Internet Engineering Task Force (IETF) standard for collaborative authoring on the World Wide Web. It consists of a set of extensions to the Hypertext Transfer Protocol (HTTP). These extensions facilitate collaborative editing and file management among users located remotely from each other on the Internet.

workflow processes

A workflow process defines a series of events that must be achieved before a certain workflow-enabled action takes place. There are two kinds of workflow processes:

Parallel: In a parallel review workflow process, all approvers review the submitted files or request at the same time. The number of approvals or rejections for a completed approval or rejection is set in the Workflow tab of the folder or Library Properties window.
Serial: In a serial review workflow process, each approver reviews the submitted files or request in turn, one approver at a time. All reviewers must approve the request to complete the approval process; a single rejection ends the review process, and results in the request being rejected.

working copy

A working copy is the editable copy of a file. When a file is checked out, a server-resident working copy is created as a copy of the latest version. Similar to a file version, the working copy has both content and metadata for the document, and can be overwritten by that user any number of times. The working copy is visible only to the user who checked out the document. The user who checked out the document may update the working copy.