Skip Headers
Oracle® Content Services Application Administrator's Guide
10g Release 1 (10.1.2)

Part Number B25276-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

Glossary

access roles

Oracle Content Services 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 Services. Each role is made up of a set of permissions — a permission represents the ability to perform a specific Oracle Content Services action or operation.

Administration Mode

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

application administration

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

approver

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

archive

Each Oracle Content Services Site contains an Archive folder. When a file or folder is deleted, the item is moved to the Trash folder of the Library containing the file or folder. When an item is deleted from the Trash folder, the item is moved to the Archive folder. Depending on the Site's configuration, items in the Archive folder may be automatically deleted after a specified period of time. Files and folders in the Archive folder can be recovered and restored by the Site's Content Administrator.

audit event

A record of an Oracle Content Services operation that is stored as a record of an operation or operation attempt in the repository. This includes the information selected when discovered through an audit search.

audit history

A set of audit events that can be searched. Audit history can be used to associate a set of audit events with individual objects.

category

A category is a unit of information by which files and folders may be classified. In Oracle Content Services, 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 your Site by the Oracle Content Services Category Administrator.

category attribute

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

check-out/check-in

One mechanism for creating a new version of a file is check-out/check-in. A user checks out a document to indicate his intention to create a new version. Each document 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 document, 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 Services folder. The Container provides users and Administrators with greater flexibility in organizing files and folders. For instance, Containers could be used to organize an Oracle Content Services Site by a company's business divisions or office locations. Only Libraries and Containers can be stored in a Container.

File Transfer Protocol (FTP)

File Transfer Protocol (FTP) is a standard protocol for transferring files between computers over a network.

global audit history

Global audit history contains a wide set of audit events for all objects. It can be searched by Configuration Administrators and is the source of audit events used when generating a global audit report.

Library

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

metadata

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

object audit history

Object audit history contains audit events associated with a specific object.

Oracle Internet Directory

Oracle Internet Directory is an online directory, which is a specialized database that stores information in a hierarchical format for fast lookup and retrieval. It implements Lightweight Directory Access Protocol (LDAP), an industry-standard protocol for accessing online directory services. Oracle Content Services users are created in Oracle Internet Directory.

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 Services Site.

primary audit information

A collection of information present for all audit events. This includes the following:

quota

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

Site

In Oracle Content Services, a Site is a discrete organizational entity whose users can collaborate on files and folders. Users in one Site do not have access to the content of users in another Site. Oracle Content Services Sites are based on Identity Management realms.

system administration

Oracle Content Services system administration involves the following tasks:

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 process

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:

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.