Contents

Title and Copyright Information

Preface

Audience

Documentation Accessibility

Related Documents

Conventions

1 Introduction

1.1 About This Guide

1.2 About This Product

1.3 What's New

1.3.1 Conceptual Changes in this Product

1.3.2 Documentation Changes in this Product

1.4 Using Help

1.4.1 Tooltips

1.4.2 Quick Help

2 Understanding Retention Management

2.1 Management of Retained Items

2.1.1 What To Retain

2.1.2 Lifecycle for Retained Content

2.1.3 Types of Retained Content

2.1.3.1 Internal and External Retained Content

2.1.3.2 Classified, Unclassified, Declassified Content

2.1.3.3 Non-Permanent, Transfer or Accession, and Reviewed Content

2.2 Basic Retention Management Concepts

2.3 Physical Content Management

2.4 Interaction with Oracle WebCenter Content

2.5 Basic Retention Processes

3 Interface Overview

3.1 Interface Overview

3.1.1 Configuring The System

3.1.2 Configuring Reports

3.1.3 Configuring PCM

3.2 Individual Page and Actions Menu

3.3 Menus

4 Screening and Updating Content

4.1 Screening Functionality

4.1.1 Enabling or Disabling User-Friendly Captions

4.2 Updating Information

4.2.1 Scheduling Updates

5 Managing Content

5.1 Managing Content

5.1.1 Viewing Content Item Information

5.1.1.1 Viewing Content Life Cycles

5.1.1.2 Viewing Content Review History

5.1.1.3 Viewing Content Item Metadata History

5.1.1.4 Viewing Classified Metadata History

5.1.1.5 Viewing an Item's Freeze Details

5.1.2 Freezing, Rescinding, and Other Content Actions

5.1.2.1 Deleting Metadata History of Content Items

5.1.2.2 Freezing or Unfreezing an Item

5.1.2.3 Canceling, Rescinding or Expiring Content

5.1.2.4 Marking an Item as Obsolete or Removing Obsolete Designation

5.1.3 Reviewing Items

5.1.4 Deleting, Moving, and Changing Content Items

5.1.4.1 Moving an Item to Another Category or Record Folder

5.1.4.2 Deleting an Item

5.1.4.3 Assigning Disposition Schedules to Content Items

5.2 Managing Classified Content

5.2.1 Reviewing Classifications

5.2.2 Upgrading or Downgrading Classification

5.2.3 Declassifying Content

5.2.4 Undoing a Cutoff

6 Managing Physical Content

6.1 Managing Physical Items

6.1.1 Deleting a Physical Item

6.1.2 Freezing and Unfreezing a Physical Item

6.1.3 Printing a Label for a Physical Item

6.2 Importing Physical Content Manually

6.2.1 Required File Format

6.2.1.1 LocalDataProperties

6.2.1.2 ImportExportManifest

6.2.1.3 ExternalItemsExtItems

6.2.2 Sample File

6.3 Processing Physical Content

6.3.1 Retention Schedules for Physical Items

6.3.2 Disposition Events for Physical Items

6.3.3 Pending Options for Physical Items

6.3.4 Audit Log Files for Processed Events

7 Managing Reservations and Barcodes

7.1 Reservation Details

7.1.1 Reservations History

7.2 The Reservation Process

7.2.1 Reservation Request Properties

7.2.1.1 Request Status

7.2.1.2 Transfer Method

7.2.1.3 Priority

7.2.1.4 Request Item Actions

7.3 About Barcodes

7.3.1 Barcode Files

7.3.1.1 Barcode File Actions

7.3.2 The Barcode Utility Software

7.4 Managing Barcodes

7.4.1 Programming the Barcode Scanner

7.4.2 Uploading Barcode Data Directly to PCM

7.4.3 Saving Barcode Data to a File

7.4.4 Uploading Previously Saved Barcode Data to PCM

7.4.5 Processing a Barcode File

8 Setting Up PCM Offsite Storage

8.1 Using Offsite Storage

8.2 Managing Offsite Storage

8.2.1 Setting Up Default Customer Information

8.2.2 Mapping New Districts

8.2.3 Creating Manual Pickup Requests

8.2.4 Browsing Uploaded Files

8.2.5 Browsing Processed Files

8.2.6 Transferring Files to Offsite Storage

9 Scheduled Tasks

9.1 Using Scheduled Tasks

9.1.1 Changes in Scheduling From Previous Product Versions

9.2 Managing Scheduling

9.2.1 Scheduling Screening Reports

9.2.2 Editing Recurring Screening Reports

9.2.3 Viewing Recurring Screening Report History

9.2.4 Scheduling and Unscheduling Freezes

9.2.5 Viewing Scheduled Job Information

10 Processing Retention Assignments

10.1 Retention Assignment Overview

10.1.1 Items Subject to Review

10.1.2 Approval and Completion

10.1.3 Frozen Items and Event Processing

10.1.4 Searching Retention Steps and Actions

10.1.5 Using Batch Processing

10.1.6 Specifying an Alternate Reviewer

10.2 Managing Disposition Tasks

10.2.1 Screening for Retention Steps

10.2.2 Viewing Failed Dispositions

10.2.3 Viewing Pending Reviews and Dispositions

10.2.4 Marking Content Items as Reviewed

10.2.5 Editing Review Information

10.2.6 About Disposition Processing

10.2.6.1 Accessing the Pending Approval Interface

10.2.6.2 Event Processing

10.2.6.3 Pending Approvals

10.2.6.4 Pending Review

10.3 Processing Dispositions

10.3.1 Multi-Step Disposition Processing

10.3.1.1 Approval Step

10.3.1.2 Completion

10.3.2 Single Step Disposition Processing

10.3.2.1 Approving Events

11 Generating Reports

11.1 Configuring Report Options

11.2 User and Group Reports

11.2.1 User Report

11.2.2 User Barcode Reports

11.2.3 User Roles Report

11.2.4 Group Report

11.2.5 Group-User Report

11.3 Content and Physical Item Reports

11.3.1 Creating a Report

11.3.2 Internal Item Detail Report

11.3.3 Search Results Report

11.3.4 Records Destruction Certificate Report

12 Monitoring, Customizations and Audit Tools

12.1 Using Performance Monitoring

12.1.1 Enabling Performance Monitoring

12.1.2 Checking Performance Results

12.1.3 Viewing Performance Alerts and Details

12.2 Using Custom Scripts

12.2.1 Creating or Editing Scripts

12.2.2 Deleting a Custom Script

12.2.3 Viewing Script Information

12.3 Using the Audit Trail

12.3.1 Configuring the Audit Trail

12.3.2 Specifying Metadata Fields to Audit

12.3.3 Searching within the Audit Trail

12.3.4 Setting Default Metadata for Checking In Audit Trails

12.3.5 Checking In and Archiving the Audit Trail

12.3.6 Searching an Archived Audit Trail

12.3.7 Viewing an Archived Audit Trail

12.3.8 Creating an Audit Trail Report

13 Archiving and Transferring Information

13.1 The Archive Process

13.1.1 Exporting Auxiliary Metadata Sets

13.1.2 The Export/Import Process

13.1.3 Archive Import/Export Rights and Permissions

13.2 Managing Imports and Exports

13.2.1 Exporting an Archive

13.2.2 Importing an Archive

13.2.3 Importing a Batch-Created Storage Hierarchy

13.3 XSD Data Transfer

13.3.1 Important Considerations Before Exporting

13.3.1.1 Special Handling of <choice> Elements

13.3.1.2 Required Fields on Import

13.3.1.3 Target Namespace and Qualified Locals

13.3.2 Configuring XSD for Importing and Exporting

13.3.3 Exporting and Importing XSD Data

14 FOIA and Privacy Act Tracking

14.1 FOIA and DB2 Databases

14.2 About Workflows

14.3 The FOIA/Privacy Act Workflow

14.3.1 Processing Details

14.3.2 Initial Required Setup

14.3.3 Begin Request Processing

14.3.3.1 Create a Request Folder

14.3.3.2 Create a Request

14.3.4 First Decision Point: Expedited or Non-Expedited

14.3.4.1 Review Request Form and Route

14.3.4.2 Send Acknowledgements

14.3.5 Second Decision Point: Service or Denial

14.3.5.1 Servicing a Request

14.3.5.2 Denying a Request

14.3.6 Third Decision Point: Denial Processing

14.3.6.1 Refusing a Denial

14.3.6.2 Approve Denial

14.3.7 Fourth Decision Point: Appeal and Decision

14.3.7.1 Initiating an Appeal

14.3.7.2 Acknowledging an Appeal

14.3.7.3 Reviewing the Appeal

14.3.8 Final Actions

15 Using Federated Search and Freeze

15.1 Federated Searches

15.1.1 Federated Search Query Builder

15.2 Performing a Search

15.2.1 About Returned Content

15.2.2 Checking Search Progress

15.2.3 Subscribing to a Search

15.2.4 Deleting a Search

15.3 Federated Freeze

15.3.1 Freezing Search Results

15.3.2 Viewing Scheduled Freezes

A User Interface

A.1 Configure Retention Settings Page

A.2 Configure Physical Content Management Page

A.2.1 Physical Item Information Page

A.3 Update Interface

A.3.1 Define Query Page

A.3.2 Query Schedule Section

A.3.3 Scheduled Update Page

A.3.4 Update Preview Page

A.4 Classified Content Interface Pages

A.4.1 Review Classification Page

A.4.2 Upgrade or Downgrade Classification Page

A.4.3 Declassify Page

A.5 Barcode Interface

A.5.1 Main Barcode Utility Screen

A.5.2 Barcode Upload Screen

A.5.3 Configure Host List Screen

A.5.4 Barcode Upload Results Screen

A.5.5 Program Videx Barcode Wand Screen

A.5.6 Barcode Processing Page

A.5.7 Barcode File Processed Page

A.6 Offsite Storage Interface Pages

A.6.1 Offsite Storage General Setup Page

A.6.2 District Mapping Pages

A.6.2.1 Choose District Mapping Page

A.6.2.2 Map Metadata Pages

A.6.3 Create Manual Pickup Page

A.6.4 Browse Uploaded Files Page

A.6.5 Browse Processed History Page

A.7 Subject to Review (Vital) Interface Pages

A.7.1 Edit Review Information for Retention Category/Folder Page

A.8 Scheduling Interface Pages

A.8.1 Scheduled Screening Reports Page

A.8.2 View History Page

A.8.3 Job Information Page/Edit Job Information Page

A.8.4 Scheduled Freezes Page

A.8.5 Edit Recurring Report Schedule Page

A.8.6 Scheduled Jobs Listing Page

A.9 Retention Assignment Interface Pages

A.9.1 Retention Step Search Page

A.9.2 Schedule Retention Step Audit Report Page

A.9.3 Failed Dispositions Page

A.9.4 Pending Dispositions Page

A.9.5 Pending Reviews Page

A.9.6 Disposition Information Page

A.9.7 Disposition Parameter Dialog

A.10 Configure Report Settings Page

A.11 Customization, Monitoring and Audit Pages

A.11.1 Configure Performance Monitoring Page

A.11.2 Performance Processing Results Page

A.11.3 Configure Custom Script Page

A.11.4 Create or Edit Custom Script Page

A.11.5 Custom Script Information Page

A.11.6 Configure Audit Page

A.11.7 Audit Fields Page

A.11.8 Checked-in Audit Entries Page

A.11.9 Default Metadata for Checked-In Audit Entries Page

A.11.10 Search Audit Trail Page

A.12 Import/Export Interface Pages

A.12.1 Import/Export Archive Page

A.12.2 Configure Import/Export Schema Page

A.12.3 Create Import/Export Schema Page

A.12.4 Configure Top Level Schema Nodes Page

A.12.5 Configure Mappings Page

A.12.6 Import with Schema Page

A.12.7 Export with Schema Page

A.13 FOIA and PA Interface Pages

A.13.1 FOIA/PA Processing Pages

A.13.1.1 Active Workflows Page

A.13.1.2 Assignments in Queue Page

A.13.1.3 Amendment Record Form

A.13.1.4 Disclosure Request Form

A.13.1.5 Access Request Form

A.13.1.6 Request Fee Table

A.13.1.7 Workflow Content Page

A.13.1.8 Workflow Review Page

A.13.1.9 Denial Record Form

A.13.1.10 Appeal Request Form

A.13.1.11 Final Result Dialog

A.13.2 FOIA/PA Data Pages

A.13.2.1 Access Record Form

A.13.2.2 Accounting Record Form

A.13.2.3 Disclosure Record Form

A.13.2.4 Dispute Record Form

A.13.2.5 Exemption Record Form

A.13.2.6 Matching Program Records Form

A.13.2.7 Privacy Act File

A.13.2.8 System of Records Form

A.14 Federated Search and Freeze Pages

A.14.1 Federated Search Pages

A.14.1.1 Federated Query Builder Page

A.14.1.2 Federated Searches List Page

A.14.1.3 Federated Search Details Page

A.14.1.4 Federated Search Results Page

Index

Oracle® WebCenter Content

Administrator's Guide for Records

11g Release 1 (11.1.1)

E10789-02

November 2011

Oracle WebCenter Content Administrator's Guide for Records, 11g Release 1 (11.1.1)

E10789-02

Copyright © 2010, 2011 Oracle and/or its affiliates. All rights reserved.

Primary Author: Jean Wilson

Contributor: Brian Carlson, Brian Johnson, Lisa Jones, Tok Hui Mackenthun, Rene Madsen, Jason Ogaard, Victor Owuor, Alex Sanchez

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Preface

This guide provides instructions to administer and maintain Oracle WebCenter Content: Records software.

Audience

This guide provides instructions to configure and administer the product. The guide is intended mainly for administrators, records managers, and privileged users responsible for managing retention policies.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

The following documentation is available:

Installation Guide for your product: This document provides information about installing the software on your system.

Oracle WebCenter Content Setup Guide for Records: This document provides information about setting up the software.

Oracle WebCenter Content Administrator's Guide for Records: This document provides information about administering and managing the software.

Oracle WebCenter Content User's Guide for Records: This document provides information about common tasks performed by users when using the software.

In addition to these guides, you can also access information about the product with context-sensitive tooltips, quick help, and help menu.

Conventions

The following text conventions are used in this document:

Convention | Meaning
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.
IntradocDir/ucm/urm/config | The default location for configuration files mentioned in this documentation. IntradocDir is used to refer to the root directory for the actual configuration and data files specific to an instance deployed on the Oracle WebCenter Content domain on an Oracle WebLogic Server.

1 Introduction

This section covers the following topics:

Section 1.1, "About This Guide"

Section 1.3, "What's New"

Section 1.4, "Using Help"

1.1 About This Guide

This guide provides instructions to administer the product software. In general, it does not contain details about setting up the product. For example, this guide contains instructions for processing dispositions (those rules used to manage content life cycles), but it does not contain instructions for creating those dispositions. Details about setting up the software is contained in the Oracle WebCenter Content Setup Guide for Records.

A glossary of frequently used terms is also included in the Oracle WebCenter Content Setup Guide for Records.

Details about processes are contained in either this guide or the Oracle WebCenter Content User's Guide for Records. If a task can only be accomplished by users with administrative privileges, that task is discussed in the Administrator's Guide. If the task can be accomplished by users with administrative or user privileges, it is discussed in the User's Guide.

The information contained in this document is subject to change as the product technology evolves and as hardware, operating systems, and third-party software are created and modified.

This guide assumes you are using the Trays layout and that you have some familiarity with Oracle WebCenter Content and its use. References to appropriate documentation are made throughout this documentation to assist in finding the information.

In this document and other documents in this product set, the terms "content" and "record" are synonymous and can be used interchangeably.

1.2 About This Product

Oracle WebCenter Content: Records is an enterprise-wide 5015.2 Chapter 2 and Chapter 4 certified electronic and physical records management system. It provides a single application that can be used to create and administer the information life cycle for both physical and electronic information. It allows organizations to apply retention policies as well as legal discovery and holds to relevant content across the enterprise, from e-mail attachments and content stored in file servers to physical records in a warehouse. It also has a framework for extension to other repositories via adapters.

The following options are available after installing the software:

Minimal: Installs a small amount of the Records system metadata fields and a limited subset of disposition actions. This is the initial default when the software is enabled.

Typical: Enables Physical Content Management as well as all disposition actions and all features except for DoD Configuration (Department of Defense), Classified Topics, FOIA/PA tracking (Freedom of Information Act/Privacy Act), and Email.

DoD Baseline: Enables the features from a Typical installation with the addition of DoD Configuration and Email.

DoD Classified: Enables all features except for FOIA/PA.

Custom: Enables a variety of feature options. Note that some disposition actions are dependent on other actions. If such an action is selected, dependent actions are also automatically selected.

This documentation describes features available in the majority of configuration scenarios. The features available at your site will vary depending on the options chosen during configuration.

1.3 What's New

The 10g version (and older versions) of this software were divided into two editions:

Records Manager DoD Edition, which was used for DoD compliance tracking

Corporate Edition, which did not contain many of the features included in Records Manager DoD Edition.

As of the 11g release, much of the product functionality has been merged and functionality can be chosen after installation by selecting different features for configuration.

The classification scheme hierarchy functionality for use with the Model Requirements for the Management of Electronic Records (MoReq2) specification is also new for this release. This functionality can be enabled by setting a configuration variable.

Sites that are upgrading from previous versions of the software will see increased flexibility and functionality. Specific differences are available in the Installation Guide for the product.

The following list discusses some specific changes to the product from previous releases. The features will vary depending on the options chosen at installation:

The definition of a record is now configurable. Options on the Create Retention Category page allow a records administrator to choose whether items in that category can be revised, deleted, edited, or will be permanent.

Setting up the software now consists of three main steps:

Initial choices: this should be done immediately after installation. Depending on the choices made, specific components will be enabled for use.

Initial configuration of global settings: This includes setting configuration variables, configuring the time periods used in the software, setting up triggers, and other global settings used for retention management.

Configuring the retention elements of the software: This includes setting options to use custom security fields, to use classification guides, and to choose how revisions, deletions, and edits to content are handled.

Physical Content Management documentation is incorporated into this documentation at this release. Separate documentation no longer exists for Physical Content Management.

Page navigation menus on the Search Results Page have changed. If more results are returned than are configured in the User Profile page, the page navigation menu indicates that other pages of information are available for viewing.

A print option is now available on every screen.

When using Physical Content Management offsite storage of content can be configured.

Menus have been extensively changed. Most options are now available by using the Records or the Physical menu options on the Top menu.

You can easily view your assigned rights by going to the My Profiles page. Retention administration rights are shown there as are the assigned roles.

A dashboard is now available that can be used to quickly organize product features for easy access and use. This is discussed in detail in the Oracle WebCenter Content User's Guide for Records.

A new interface is provided to manage reports. Templates can be created for reports and can be checked in to the repository in the same way other content can be checked in.

Out of date content (not the current version) is now designated as such with a line through the content name in search results. Any item that is obsolete, canceled, rescinded, and so on is designated in this manner.

A Favorites listing can be created, similar to bookmarked browser Favorites. Users and aliases as well as categories, freezes and other retention objects can be added to the Favorites menu. Favorites items are used to populate option lists, such as when creating freezes. For example, if an item is on your Favorites list, it appears on the option list when you choose a freeze name. This helps to narrow the choices when using this functionality.

When creating disposition rules involving moves (such as Archive, Accession, Transfer, and Move), a location can be specified. If a location is chosen, content is copied to the specified location as part of the disposition step. In previous releases, a zip file of the copied content was created; the content was not copied to a location.

Disposition rules can now be reviewed in a workflow before implementation.

Content stored in folders can now be transferred to volumes. When a volume is created, all content in the folder is moved to a newly created volume folder.

Services used in this product are now documented in the Oracle WebCenter Content Services Reference Guide. See that guide for details about the services used and how to implement new services.

Screening can now be accessed through the search menu.

Performance monitoring can now be done to track batches processes, items, and other processes.

Folios can be used to easily manage content. With this release, when a folio is locked (either by freezing or filing in a category that prohibits edits), the folio and its content are automatically cloned, and the bundle is locked, thus preventing the folio from being edited.

Categories and disposition rules can be copied from existing categories to a new category, making retention schedule creation easier and less prone to error.

Related content links for items can be created as needed on the content checkin page.

Oracle WebCenter Content: Records, in conjunction with Oracle WebCenter Content, has been verified by a third party to be compliant with the technical elements of FDA 21 CFR Part 11, specifically the electronic signature portion of that specification.

1.3.1 Conceptual Changes in this Product

In previous releases of this product, the term record was used to designate those items of content that could not be revisioned. Therefore, a designation was made between content and records.

In this release, any item of content can be revisioned if revisioning is allowed. One of the initial setup choices is to allow revisions or to prohibit revisions of content. You can now finely tune which categories, folders, and content are revisionable, editable, or that can be deleted. Content, categories, and folders are no longer designated as record categories or record folders.

1.3.2 Documentation Changes in this Product

The documentation set for this product has been substantially revised to reflect new functionality and changes.

In addition, several task descriptions have been moved from the administrative guides. Any task that can be performed by either a user or a privileged user (administrator or user with other administrative privileges) is now documented in the Oracle WebCenter Content User's Guide for Records.

1.4 Using Help

In addition to the guides provided with the product, you can access information about product functionality with context-sensitive tooltips, quick help, and the help menu.

1.4.1 Tooltips

If the mouse cursor is held over a field label in a web browser, context-sensitive information on the field label is displayed. A question mark is displayed then the tooltip appears.

Figure 1-1 Field Label Tooltip

When using Netscape or Firefox as a web browser, tooltips are also available for items in options lists, provided the list items are not custom entries.

Figure 1-2 Option List Item Tooltip (Only Supported by Netscape and Mozilla Browsers)

1.4.2 Quick Help

Click Quick Help (where available) to view context-sensitive help for that page or screen.

2 Understanding Retention Management

This section covers the following topics:

Section 2.1, "Management of Retained Items"

Section 2.2, "Basic Retention Management Concepts"

Section 2.3, "Physical Content Management"

Section 2.4, "Interaction with Oracle WebCenter Content"

Section 2.5, "Basic Retention Processes"

2.1 Management of Retained Items

Oracle WebCenter Content: Records effectively manages content items on a retention schedule. The focus of records management tends to be the preservation of content for historical, legal, or archival purposes while also performing retention management functions.

The focus of retention management tends to be the scheduled elimination of content based on a schedule designed by a record administrator.

This software combines both record and retention management into one software system. It can track and preserve content as needed, or dispose of content when it is no longer required.

This section covers the following topics:

Section 2.1.1, "What To Retain"

Section 2.1.2, "Lifecycle for Retained Content"

Section 2.1.3, "Types of Retained Content"

2.1.1 What To Retain

Items for retention are any form of information, both physical and electronic, that is important enough for an organization so they must be retained for a specific period and may be disposed of when no longer needed. However, it can be revisioned, retained and can be managed on a disposition schedule. An organization may choose to manage content to eliminate outdated and misleading information and track documents related to legal proceedings.

Many organizations are subject to regulations that require the retention of information for a specified period:

Sarbanes Oxley:

Applies to all publicly traded corporations or companies that may become public

Audit-related working papers, communications, and correspondence must be retained for five years after the audit

Government organizations: DoD 5015.2, General Records Schedule

Pharmaceutical/health care industry: HIPAA, FDA regulations

Financial services: SEC Rule 17a

Telecommunications industry: 47 CFR 42, and so on

There may be litigation-related needs for effective and efficient retention management:

Policy-based retention of content:

Retain information needed for litigation (for example, a contract and any communication relating to it).

Centralized searching and retrieval of that information.

Systematic disposition of eligible content:

Less material to search through during discovery.

Less material to give to opposing counsel.

Suspend/freeze disposition of content relating to pending litigation:

Avoid appearance of cover-up and possible liability when content relating to pending litigation is destroyed.

There may be business-related needs for effective and efficient retention management:

To organize items that are created in a variety of forms (email, CDs, DVDs) and which are stored in a variety of locations (employee computers, central file storage, and so on).

To provide a uniform infrastructure for retrieving and sharing the content across the organization.:

The information may be required for the day-to-day operations of the organization and must be kept for historical, tracking, or audit purposes (for example, receipts, order histories, completed forms, personnel files, corporate announcements).

The information may be necessary to the success or survival of the organization (for example, software source code, contracts, financial data).

There may be internal policies or external regulations requiring the information to be retained (for example, transaction documents, financial statements, lease agreements).

To ensure that content items are retained over the period they are useful to the business.

Oracle WebCenter Content: Records manages all content, regardless of source, in a single, consistent, manageable infrastructure.

2.1.2 Lifecycle for Retained Content

The lifecycle of retained content goes through several stages.

Figure 2-1 Life Cycle of Retained Content

The filing date is the date a content item is marked as an item being tracked. This often coincides with the checkin date. However, it is possible for an active content item already checked in to be tracked.

The information may need to be for different periods of time, depending on the type of content, its use within the organization, and the need to comply with external laws or regulations.

The cutoff of a content item is the moment the status of the item changes and the item goes into disposition. An item may be cut off after a specific period, at a specific event, or after an event.

Items are disposed of by authorized people according to the requirements of the organization. Disposition actions can include destruction, storage, transfer, or an item can be deemed so important it will never be destroyed (for example, due to historical significance). "Disposal" in this instance indicates a status changes from active use.:

2.1.3 Types of Retained Content

Retained content can be divided into categories depending on the perspective:

Section 2.1.3.1, "Internal and External Retained Content"

Section 2.1.3.2, "Classified, Unclassified, Declassified Content"

Section 2.1.3.3, "Non-Permanent, Transfer or Accession, and Reviewed Content"

2.1.3.1 Internal and External Retained Content

An internal retained content item is an electronic item stored within Oracle WebCenter Content and managed by the product.

External content can also be managed. An external retained content item is a source file not stored in Oracle WebCenter Content. It can be in a variety of formats, both physical or electronic. The software can manage the disposition schedule, search metadata associated with the external file, and manage an electronic rendition of an external file. An electronic rendition can either be checked in as a primary file of an external item, or be filed as a separate file, and then linked to the external file metadata.

2.1.3.2 Classified, Unclassified, Declassified Content

Content can be classified, unclassified, or declassified.

Classified content is that which requires protection against unauthorized disclosure (for example, because it contains information sensitive to the national security of the United States or because it is essential for a corporation's operation).

Unclassified content is not and has never been classified.

Declassified content was formerly classified, but that classified status has been lifted.

A classification specifies the security level of a classified content item. A classification guide provides default classification values for checkin pages.

Options can be chosen during the initial setup to insure that the system complies with the DoD 5015.2 standard (including Chapter 4). The software has been certified by the Joint Interoperability Test Command (JITC) to comply with that standard. A copy of the standard is available on the official web site of the Department of Defense, Washington Headquarters Services, Directives and Records Division at http://www.dtic.mil/whs/directives/.

Important:

Executive Order 12958: Classified National Security Information describes in detail the system for classifying, safeguarding, and declassifying national security information. This guide assumes you are familiar with proper classification protocols.

2.1.3.3 Non-Permanent, Transfer or Accession, and Reviewed Content

For disposition purposes, content is categorized into non-permanent, transfer or accession to NARA, and subject to review. Most items fall into the non-permanent category.

Non-permanent items are usually destroyed after a retention period. Permanent items are deemed important for continued preservation and are retained indefinitely (for example, because of their historical significance).

Items can be scheduled for periodic reviews by authorized people. This complies with the DoD Vital Record Review criteria.

2.2 Basic Retention Management Concepts

Oracle WebCenter Content: Records is used to manage content, regardless of source or format, in a single, consistent, manageable infrastructure. Managed items are assigned retention schedules and disposition rules that allow users to schedule life cycles for content to eliminate outdated or superseded information, manage storage resources, or comply with legal audit holds.

Content and its associated metadata are stored in retention schedules, which are hierarchies with categories that define disposition instructions. Access to the items is controlled by rights assigned to users by a Records Administrator. The items can be accessed, reviewed, retained, or destroyed in an easy and efficient manner by authorized people according to the requirements of an organization.

Disposition schedules of content in the repository can also be managed, enabling the scheduling of life cycles for content to eliminate outdated or superseded information, manage storage resources, or comply with legal audit holds.

The following concepts are important to understand in the context of retention management:

Record administrator: individuals in the organization who are responsible for setting up and maintaining the retention schedule and other aspects of the management system.

Record user: individuals who use the software to check content in and out of the system, to search for records, and to perform other non-administrative tasks.

Record officer: individuals who have limited administrative responsibility in addition to the responsibilities of a record user.

Administrator: individuals who may maintain the computer system, network, or software at the site where the management system is in place.

The retention schedule is an organized hierarchy of series, categories, and record folders, which allows users to cluster retained content into similar groups, each with its own retention and disposition characteristics.

A series is an organizational construct in the retention schedule that assists in organizing categories into functional groups. Series are normally static and are used at a high level in an organization hierarchy. They can be especially useful if a large amount of categories are used. A series can be nested, which means a series may contain other series.

A retention category is a set of security settings and disposition instructions in the retention schedule hierarchy, below a series. It is not an organization construct but rather a way to group items with the same dispositions. A category helps organize record folders and content into groups with the same retention and disposition characteristics. A retention category may contain one or more record folders or content items, which then typically follow the security settings and disposition rules associated with that retention category. Retention categories cannot be nested, which means a retention category cannot contain other retention categories.

A record folder is a collection of similar content items in the retention schedule. Folders enable content to be organized into groups. A folder typically follows the security settings and disposition rules associated with its assigned retention category. Folders can be nested, which means a folder may contain other folders.

Disposition is the collective set of actions taken on items. Disposition actions include wait times and activities such as transfer to external storage facilities, the destruction of temporary content, deletion of previous revisions, and deletion of all revisions.

A disposition instruction is created within a retention category, and typically consists of one or more disposition rules, which define how content is handled and what actions should be taken (for example, when and how content should be disposed of).

A period is the segment of time that must pass before a review or disposition action can be performed. Several built-in periods are provided (for example, "one year"), but custom periods can be created to meet unique business needs.

A trigger is an event that must occur before a disposition instruction is processed. Triggers are associated with disposition rules for retention categories. Examples of triggering events include changes in status, the completed processing of a preceding disposition action, or a retention period cutoff.

A link is a defined relationship between items. This may be useful when items are related and need to be processed together. Links are available for items stored both in and out of the retention schedule.

A classification specifies the security level of a classified item. It is used in the process of identifying and safeguarding content containing sensitive information. Typical classification levels are "Top Secret," "Secret," and "Confidential," and "Unclassified."

A classification guide is a mechanism used to define default values for several classification-related metadata fields on the content checkin pages for content. A guide enables convenient implementation of multiple classification schemes.

Freezing inhibits disposition processing for an item. Frozen content cannot be altered in any way nor can it be deleted or destroyed. This may be necessary to comply with legal or audit requirements (for example, because of litigation). Freezing is available for items stored both in and out of the retention schedule.

External items are those that are not searched and processed in the same fashion as retained content. External content usually refers to content managed by Physical Content Management or managed by an adapter (an add-on product).

Federation, Federated Search, Federated Freeze are functionality used to manage the process of legal discovery. Using Federated Search or Freeze, a legal officer can search content across all repositories to gather information needed for legal proceedings.

2.3 Physical Content Management

While Oracle WebCenter Content: Records enables organizations to manage the retention and disposition of content, PCM provides the capability of managing physical content that is not stored in the repository in electronic form.

All items, internal and external regardless of their source or format, are managed in a single, consistent, manageable infrastructure using one central application and a single user interface. The same retention schedules are used for both electronic (internal) and physical (external) content.

PCM tracks the storage locations and retention schedules of the physical content. The functionality provides the following main features:

Space management, including definition of warehouse layout, searching for empty space, reserving space, and tracking occupied and available space.

Circulation services, including handling reservation requests for items, checking out items, and maintaining a due date for checked-out items.

Chargeback services, including invoicing, for the use of storage facilities and/or actions performed on physical items.

Barcode file processing, including uploading barcode information directly into the system, or processing barcode files manually.

Label creation and printing, including labels for users, storage locations, or individual physical items.

Retention management, including periodic reviews, freezes and litigation holds, and e-mail notifications for pending events.

2.4 Interaction with Oracle WebCenter Content

The following layouts and search templates are supported. Users can change layouts and templates by setting them in their user profile:

Supported layouts:

Trays

Top Menus

Supported search templates:

Headline View

Thumbnail View

My Headline View

The Classic layout or the Classic View search template are not supported. This guide assumes you are using the Trays layout.

2.5 Basic Retention Processes

The following steps outline the basic workflow of retained content:

The retention schedule and any required components, such as triggers, periods, classifications, and custom security or metadata fields are created.

Items are filed into the retention schedule by users. The filed items assume the disposition schedules of their assigned category.

Disposition rules are processed in accordance with the defined disposition schedules, which usually have a retention period. The processing is activated by either a system-derived trigger or custom trigger. The trigger could affect one or more items simultaneously.

Whenever a disposition event is due for action (as activated by a trigger), an e-mail notification is sent to the person responsible for processing the events. The same is true for review. The pending events and reviews are displayed in the pages accessed from the Retention Assignments links within the user interface.

The Records Administrator or privileged user performs the review process. This is a manual process.

The Records Administrator processes the disposition actions on the pending dispositions approval page. This is a manual process.

A batch process is run to process an approval.

Many disposition schedules are time-based according to a predictable schedule. For example, content is often filed then destroyed after a certain number of years. The system tracks when the affected content is due for action. A notification e-mail is sent to reviewers with links to the pages where reviewers can review and approve content and folders that are due for dispositions.

In contrast, time-event and event-based dispositions must be triggered with a non-system-derived trigger (a trigger that was defined for a particular scenario). For example, when a pending legal case starts litigation, the Records Administrator must enable the custom trigger and set its activation date because the start date information is external. Custom triggers can define event and time-event based disposition actions based on the occurrence of a particular event.

3 Interface Overview

This chapter describes the key elements of the product interface. It covers the following topics:

Section 3.1, "Interface Overview"

Section 3.2, "Individual Page and Actions Menu"

Section 3.3, "Menus"

For a glossary of terminology used in this documentation, see the Oracle WebCenter Content Setup Guide for Records.

Also see the Oracle WebCenter Content User's Guide for Records for details about profiles, the task panel, the My Favorites functionality, and other interface elements used by both users and administrators.

3.1 Interface Overview

After installation, new links appear in the Top menu, used to configure and manage the software. If enabled, a link also appears to manage Physical Content Management.

3.1.1 Configuring The System

Administrative users will see all options from the menus. Other users (for example, those assigned privileged roles) may see a much smaller subset of the administrator menu, depending on their assigned rights. The exact menu options any user sees depend on the rights assigned to the user. For details about rights assigned to different roles, see the Oracle WebCenter Content Setup Guide for Records.

The following is an overview of the options on the Records menu:

Rights: Used to view assigned rights and roles. See the Oracle WebCenter Content User's Guide for Records for information about viewing rights and roles.

Favorites: Opens the Favorites interface, showing items added to your Favorites list. See the Oracle WebCenter Content User's Guide for Records for details about using Favorites.

Dashboard: Used to configure a dashboard that is a shortcut to frequently used pages. See the Oracle WebCenter Content User's Guide for Records for information about configuring dashboards.

Approvals: Opens a menu to access items awaiting review, approval or completion.

Scheduled: Accesses scheduled actions, reports, and freezes.

Reports: Used to access reports created by users as well as system reports.

Import/Export: Accesses menus allowing import and export of archives and XSD data.

Audit: Used to view checked-in audit entries or search the audit trail. Also used to configure performance monitoring tools and to screen disposition rules and failed dispositions.

Configure: Used to configure many aspects of the system, such as freezes, triggers, security, audit trail information and reports.

Global Updates: Used to update categories, folders, or content.

Batch Services: Used to process notifications, run all pending batch actions, or to process actions and reviews.

Sources: Used to display information about other content sources, either physical or external (such as adapters) where content is retained or tracked.

3.1.2 Configuring Reports

Use the Configure Report Settings Page to determine the output format for reports about freezes, screening, and labels. Default reports provided with the software can be used or new report templates can be created. The data used in the reports is limited depending on the security permissions of the person creating the report. In this way, the reports, while available to most users, can still be kept secure.

To access this page, choose Records then Configure from the Top menu. Choose Reports then Settings. For details, see Chapter 11, "Generating Reports."

See the Oracle WebCenter Content Setup Guide for Records for details about creating custom reports using BI Publisher.

3.1.3 Configuring PCM

Use the Physical menu in the Top menu to access most aspects of Physical Content Management. The exact menu options any user sees depend on the rights assigned to that user.

Administrative users will see all options. Other users (for example, those assigned privileged roles) may see a much smaller subset, depending on their assigned rights.

The following is an overview of the options on the Physical menu:

Reservations: Opens a list of all current reservations. See the Oracle WebCenter Content User's Guide for Records for details about reservations.

Storage: Opens the Exploring Storage page where storage locations can be defined and edited.

Invoices: Displays current invoices and allows creation of new invoices.

Requests: Displays pending requests, checked-out requests, and overdue requests for physical items.

Process Barcode File: Accesses a page to upload barcode data.

Configure: Used to configure many aspects of the physical management system, including general settings, chargeback types, and customers.

If Batch Services and Offsite Storage have been enabled, those options also appear. Batch Services are used to immediately process reservation requests, storage count updates, and other actions. Offsite Storage allows a site to interface with an offsite storage provider.

3.2 Individual Page and Actions Menu

When using this product, individual Actions menus are available for items on a page and in many cases for individual items. The options on the Actions menu vary depending on the page used and the type of item used (content, physical, retention category, and so on).

The following list summarizes the most commonly seen menu options:

Information: Opens a submenu used to access information pages for folders, the life cycle of the item, recent reviews, metadata history, and retention schedule reports.

Edit: Provides quick links to edit pages for folders or reviews, and options to alter an item's status by moving, closing, freezing, or unfreezing an item.

Set Dates: Provides quick links to actions associated with dates, such as marking items for review, canceling, rescinding, and expiring items.

Delete: Provides options to delete the item or perform a recursive delete (delete an entire tree if multiple items are checked).

Create: Provides options to create items appropriate to the location in the hierarchy. For example, if this is the Actions menu for a retention category, Create suboptions include Series and Retention Category.

Clicking the Info icon (a lower-case i in a circle) opens the Information Page for the item.

In addition, several pages have a page-level Actions menu that appears next to the Page title. The options on that menu apply to actions that can be performed at that level in the retention hierarchy.

3.3 Menus

After installation, the Search and Checkin menus are changed to include default profile pages. These profiles provide a filtered view of checkin and search pages, allowing you to customize what users will see. Additional options may appear depending on profiles created at your site and the choices made during configuration.

These menu options can be used to help quickly narrow searches and choose the type of checkin to perform. The Screening option on the Search menu is dependent on security rights assigned to the user.

When viewing search results, a query menu is added to the search results page.

4 Screening and Updating Content

Screening is an enhanced search capability that uses specific search criteria to filter search results. Screening can be performed by both administrative users and end users. Details are discussed in the Oracle WebCenter Content User's Guide for Records.

When using Oracle Text Search the system does not index external items, including physical items. Therefore those items and other items stored externally (for example, on an adapter system) are not available for searching.

This chapter provides overview information about screening, which can be performed by end users and by administrative users. Detailed information about performing global updates is included here because updates cannot be performed by end users.

For details about Federated Search, used during the legal discovery process, see Chapter 15, "Using Federated Search and Freeze."

Section 4.1, "Screening Functionality"

Section 4.2, "Updating Information"

4.1 Screening Functionality

In addition to search-like functionality, screening enables users to isolate retention categories, record folders, and content by their attributes. Screening lets a user see what has happened or what could happen within a retention schedule. Screening can be done at increasingly finer granularity within the retention schedule object levels. Within all levels, screening can be done by disposition information. It returns items in a retention schedule with a life cycle or items that are frozen.

Screening reports can be created immediately or they can be scheduled to be generated at a later time. This is especially useful for screening reports affecting large sets of content. Creating the screening report immediately might put a heavy load on the system, which could diminish its responsiveness and/or result in browser time-outs for end-users. To avoid overloading, schedule screening reports to be performed at midnight, an off-peak time in most environments.

Reports can also be scheduled to run at recurring intervals. Many screening functions can be performed from the Search menu. After installing and configuring the software, an additional Screening option is available on the Search menu. The same screening activities described in this chapter can be performed using that functionality.

While users can perform screening activities, the results returned are dependent on that user's roles and permissions. Only information that the user is privy to will be returned. Other information is filtered and not displayed.

4.1.1 Enabling or Disabling User-Friendly Captions

User-friendly captions are captions that do not use official retention language. User-friendly captioning can be enabled and disabled at any time. This setting also affects the captions in disposition instructions.

Permissions:

The Admin.RecordManager right is required to perform this action. This right is assigned by default to the Records Administrator role.

Choose Records then Configure from the Top menu. Choose Retention then Settings.

The Configure Retention Settings Page opens.

Select User-friendly disposition.

Click Submit Update. A message is displayed saying the configuration was successful.

Click OK.

To disable user-friendly captions, deselect User-friendly disposition.

4.2 Updating Information

Permissions:

The admin.noRmaSecurity right and the Admin role are required to perform updates. The noRmaSecurity right is not assigned by default to any role and must be assigned, with the Admin role, for the Update options to appear on the Configure Retention Settings Page.

The Update functionality quickly finds and changes large amounts of information. The information can be changed immediately or at a later time by using a scheduled update option. For example, you can change any items in a category matching a certain disposition to a different review type or to a new reviewer.

Note that a maximum of 2048 records can be searched for and updated using Oracle Text Search and Database Full Text Searching.

To access this functionality, choose Records then Global Updates from the Top menu. Select the type of update to perform.

The Define Query Page opens. The options on this page are similar to those on the Screen for Topic page, discussed in the User Guide. The options in the Query section depend on the type of query being performed (category, record folder, or internal content).

Follow these steps to define a query:

Choose a field for use from the menu.

Select a substring from the list.

Select a query value from the list.

Select a field to be updated for all items matching the first query.

Select a substring for the value from the list.

Select a new value for the field.

To preview the results of the update, click Preview Results in the upper right corner of the page.

The Update Preview Page opens. This page shows those items that will be changed by the update. To return to the Define Query Page, choose Continue Defining Search on the Page menu.

Continue adding update criteria if needed. To schedule the update for a later time, click Schedule. For more details, see Section 4.2.1, "Scheduling Updates." Click Run Now to run the change immediately. A message is displayed, indicating the selected items were updated. Click OK to return to the Define Query Page.

4.2.1 Scheduling Updates

To run the update at a later time, click Schedule to open the Query Schedule Section of the Define Query Page.

Choose a time and date for the update to run and click Submit. Enter a name for the update event and click OK. The Scheduled Update Page opens.

Use this page to change the scheduled event. To edit an event, select Edit Scheduled Event. To delete the event, select Delete Scheduled Event. And to run the event immediately, select Run Now.

5 Managing Content

This chapter discusses the tasks associated with the general administrative maintenance and processing of content. It covers the following topics:

Section 5.1, "Managing Content"

Section 5.2, "Managing Classified Content"

For information about creating and finding information, see the Oracle WebCenter Content User's Guide for Records. Page depictions and complete interface details are also in that guide.

5.1 Managing Content

Maintaining and processing content involves tasks such as moving them, initiating a freeze, or handling events such as canceling, expiring. Items can also be rescinded items or marked as obsolete.

Options for maintaining and processing content are accessible from the Page menu on the Content Information page of an item. The available actions vary depending on what type of content is being used.

The following tasks are involved in managing content:

Section 5.1.1, "Viewing Content Item Information"

Section 5.1.2, "Freezing, Rescinding, and Other Content Actions"

Section 5.1.3, "Reviewing Items"

Section 5.1.4, "Deleting, Moving, and Changing Content Items"

For details about creating content, searching for content, and using the Content Basket, see the Oracle WebCenter Content User's Guide for Records.

5.1.1 Viewing Content Item Information

Permissions:

The Record.Read right is required to perform these actions. All predefined management roles (Records Administrator, Records Officer, and Records User) have this right.

Viewing information can be done in several ways depending on the location in the product hierarchy. First locate the item by browsing, searching, or screening. Then perform one of the following actions:

On the search or screening results page, choose the option (Life Cycle, Recent Reviews, and so on) from the item's Actions menu.

On the search or screening results page, click the Info icon of the item.

The Content Information Page opens. On the Page menu, choose Information then the option needed (Life Cycle, Metadata History, and so on).

5.1.1.1 Viewing Content Life Cycles

Use the previously described procedure to access the Information menu or page for a content item. When Life Cycle is chosen, the Life Cycle Page opens.

The page shows the complete life cycle of the item according to its scheduled disposition, including the calculated dates of each disposition action. If a separate notification reviewer has been assigned for the item, the person's user name is displayed. In addition, the retention category identifier from which the record folder inherits the instruction is given for each disposition action because content can be filed into multiple folders.

5.1.1.2 Viewing Content Review History

Use the previously described procedure to access the Information menu or page for a content item.

Choose Information then Recent Reviews from the Page menu. The Review History for Item Page opens. The page shows a list of the last three reviews of the item. For details see Section 5.1.3, "Reviewing Items.". It also shows the date and time of review.

On the Recent Review Page, choose View Complete History from the Page menu to see the entire review history of an item

5.1.1.3 Viewing Content Item Metadata History

Use the previously described procedure to access the Information menu or page for an item. When Metadata History is selected, the Metadata History Page opens.

The page shows an overview of all changes made to the editable properties of the item and the affected metadata field name, the modification date and time, and the old and new values.

Important:

You can view the metadata history for content items checked into the Retention Schedule. You cannot view metadata history for content not checked into the Retention Schedule.

5.1.1.4 Viewing Classified Metadata History

Use the previously described procedure to access the Information menu or page for an item. When Classified Metadata History is selected, the Classified Metadata History Page opens. This page shows a list of all changes made to the security classification of the item.

5.1.1.5 Viewing an Item's Freeze Details

Use the previously described procedure to access the Information menu or page for a content item. If the item is frozen, the Is Frozen field value is 'Yes' and a Details hyperlink is displayed next to the field value. Click the Details hyperlink. The Freeze Details Page opens.

This page shows all freezes currently applied to the item. If the item inherited its freeze status from its parent record folder, the folder's name is shown in the Inherited From column for the inherited freeze. Click the Info icon for a freeze in the list to open the Content Information page of the item.

To save the information on this page to a file (in the report format specified on the Configure Retention Settings Page, choose the Save Freeze Details option from the Page Create menu.

5.1.2 Freezing, Rescinding, and Other Content Actions

Managing content information can be done in several ways depending on the location in the product hierarchy. First locate the item by browsing, searching, or screening. Then perform one of the following actions:

On the search or screening results page, select a Table menu then the option.

On the search or screening results page, click the Info icon of the item.

The Content Information Page opens. On the Page menu, choose Edit, Delete, or Set Dates then the needed option.

Actions can be performed on multiple items by clicking the selection box next to the item and choosing an option from the Table menu.

5.1.2.1 Deleting Metadata History of Content Items

Permissions:

The Record.DeleteHistoryFile right is required to perform this action. This right is assigned by default to the Records Administrator role.

Use the previously described procedure to find an item and delete its metadata history. When Delete Metadata History is chosen from a menu, a message prompts for confirmation. Click OK to confirm the action or Cancel to cancel it.

5.1.2.2 Freezing or Unfreezing an Item

Freezing inhibits disposition processing for an item. Content in a frozen folder inherits the freeze status from the parent folder, but it can also be frozen independently of the folder (usually with a different freeze).

In addition to content filed within a retention schedule, content not in a retention schedule can be frozen and therefore associated with a retention schedule.

More than one freeze can be applied to an item. View the Freeze Details Page for the item to see a list of all freezes currently applied to it.

Unfreezing an item releases the item again for disposition processing. When a content item is frozen, all revisions of that content item are frozen. The revision is frozen directly and the other revisions inherit the freeze.

Permissions:

The Record.Freeze/Unfreeze right to perform these actions. This right is assigned by default to the Records Administrator role.

Use the previously described procedure to find an item to freeze.

Choose Freeze or Unfreeze on the appropriate menu. A dialog is displayed.

In the Freeze Name list, select the freeze to be applied or canceled if unfreezing. If freezes were added to a My Favorites list, this freeze list contains those freeze names. Otherwise the list contains all defined freezes.

Enter a reason for the action (optional).

Click OK to confirm the action. Click Cancel to abort the entire action.

If the action is confirmed, the Retention Schedule Information area of the Content Information page shows Is Frozen: Yes and a Details hyperlink, which links to the detail page for the item. If the item was unfrozen, Is Frozen: No is displayed.

Important:

After a content item is frozen, you cannot edit its freeze reason. If the freeze is no longer correct, you should unfreeze the item and freeze it with a new reason.

5.1.2.3 Canceling, Rescinding or Expiring Content

When an item is canceled, rescinded, or expired, its status becomes obsolete.

Content can be expired as part of a disposition action or as needed. When an item expires, its status becomes obsolete.

Permissions:

The Record.Edit right is required to perform these actions. This right is assigned by default to the Records Officer and Records Administrator roles.

Use the previously described procedure to find an item to use. Choose Cancel, Rescind, or Expire from the Set Dates menu.

A prompt appears for a reason for the action. Enter a reason and click OK to confirm or leave the text box empty. Click Cancel to abort the entire action.

If confirmed, the Retention Schedule Information area of the Content Information page shows the date the item was canceled, rescinded, or expired, and also a corresponding obsolete date.

This action can be undone by choosing Clear Dates in the Actions list of the item's Content Information page. This clears a cancel, rescind, expire, or obsolete action.

5.1.2.4 Marking an Item as Obsolete or Removing Obsolete Designation

Content items can be made obsolete as part of a disposition action or through an ad hoc action.

This procedure makes an item obsolete for any reason other than expiration, cancellation, or rescinding.

Permissions:

The Record.Edit right is required to perform these actions. This right is assigned by default to the Records Officer and Records Administrator roles.

Use the previously described procedure to find an item to use. Choose Obsolete to mark the item as obsolete or Clear Dates from the Set Dates menu to undo an obsolete action.

A prompt appears for a reason for the action. Enter a reason or leave the text box empty. Click OK when done. Click Cancel to abort the entire action.

If confirmed, the Retention Schedule Information area of the Content Information page shows the date the item was made obsolete.

5.1.3 Reviewing Items

Use this procedure to mark an item as reviewed, either after receiving a review notification (as part of a disposition instruction) or as an ad hoc review.

Permissions:

The Record.Edit right and the RecordEditReview review are required to perform this action. The Record.Edit right is assigned by default to the Records Officer and Records Administrator role. The Record.EditReview right is assigned by default to all defined roles.

Use the previously described procedure to search for content items. Choose Mark Reviewed from the Set Dates menu. A prompt appears to enter a reason for the action. Enter a reason and click OK to confirm. Click Cancel to abort the entire action. If confirmed, the Retention Schedule Information area of the Content Information page shows the date the item was reviewed.

To find items awaiting review choose Records then Approvals from the Top menu. Choose Pending Reviews.

If you have administrative permissions, you can choose List All on the Table menu on the page. This shows all items awaiting review and the person assigned to do those reviews. Choose List Mine to show only those items awaiting the logged-in user's approval.

5.1.4 Deleting, Moving, and Changing Content Items

Actions involving individual content items are usually done on the Content Information Page using the Content Actions Page menu. Choose Update from that menu to access the menu choices discussed here. A frozen content item cannot be moved, deleted, or changed.

5.1.4.1 Moving an Item to Another Category or Record Folder

Permissions:

The Record.Edit right is required to perform this action. This right is assigned by default to the Records Officer and Records Administrator roles.

Select Content Actions then Update on the item's Content Information Page.

The Info Update form opens.

Click Browse following the Category or Folders field.

The Select Category or Folders page opens.

Click Clear to remove the current location.

Click the plus sign (+) or the icon to expand the retention schedule. Navigate to the retention category or record folder where the item will be moved. Click the category or folder to select it. The locator links show the hierarchical path of the category or folder in the retention schedule.

Click OK. The Select Category or Folders page closes.

On the Content Information page, click Submit Update.

The Content Information page shows the folder or category ID of the new location.

5.1.4.2 Deleting an Item

Use this procedure to delete content immediately outside of its disposition schedule. Metadata is not preserved. A frozen item cannot be deleted.

Permissions:

The Record.Delete right is required to perform this action. This right is assigned by default to the Records Administrator role. Delete permission (D) for the item's security group is also required (unless Folders is installed).

Open the item's Content Information Page.

In the Revision History area, click Delete. A prompt appears to confirm the permanent delete action.

A message is displayed stating the item was deleted successfully.

5.1.4.3 Assigning Disposition Schedules to Content Items

Use this procedure to assign a disposition schedule to an existing content item.

Select Content Actions then Update on the item's Content Information Page.

The Info Update form opens.

Select the desired object. In the Life Cycle list, select the retention category whose disposition instructions should be assigned to the item.

Click Submit Update.

The content item is now processed in accordance with the disposition instructions associated with the selected retention category.

5.2 Managing Classified Content

Managing classified information is done by using the Page menu at the top of the Content Information Page for the specific item. You must have the appropriate clearance to assign a security classification to an item. See the Oracle WebCenter Content Setup Guide for Records for more details. Use either of these methods to access the Information Page:

On the search or screening results page, choose Content Information from the item's Actions menu.

On the search or screening results page, click the Info icon of the item.

The Content Information Page opens. On the Page menu, choose Information then the option needed.

The following tasks are often performed when managing classified content:

Section 5.2.1, "Reviewing Classifications"

Section 5.2.2, "Upgrading or Downgrading Classification"

Section 5.2.3, "Declassifying Content"

Section 5.2.4, "Undoing a Cutoff"

5.2.1 Reviewing Classifications

If category authors must review the classification of an item with a higher security classification level than they have, they cannot perform that action. A records manager or system administrator with the appropriate classification level must to do it for them.

Permissions:

The Record.Edit right is required to perform this action. This right is assigned by default to the Records Officer and Records Administrator roles.

Use the previously described procedure to find an item to use. Choose Information then Review Classification from the Page menu. The Review Classification Page opens. Review the information and provide the following information in the marked fields:

The date and time of the classification review

The person (or other entity) who performed the classification review

When done, click Submit Update.

5.2.2 Upgrading or Downgrading Classification

Upgrading the classification of an item is rare. It is typically an ad-hoc action and not part of a retention instruction.

Note the following considerations:

You cannot downgrade content that had the Restricted Data or Formerly Restricted Data supplemental markings assigned. The Downgrade On field is disabled for content with a restricted supplemental marking history.

If category authors must upgrade or downgrade the classification of an item with a higher security classification level than they have, they cannot perform that action. A records manager or system administrator with the appropriate classification level must do it for them.

If a date was specified for the Downgrade on date metadata field for a classified item (upon checkin or later), a notification is sent on the due date with a reminder to downgrade the item.

Permissions:

The Record.Upgrade/Downgrade right is required to perform this action. None of the predefined roles have this right by default. You must assign that right to a user first.

Use the previously described procedure to find an item to use. Choose Edit then Upgrade Classification or Downgrade from the Page menu.

The Upgrade or Downgrade Classification Page opens. This page is similar to the Review Classification Page with the addition of fields where the classification can be changed.

Provide the following required information in the marked fields:

The date and time of the classification change

The person (or other entity) who changed the classification

The new classification level

The reason for the classification change

When done, click Submit Update.

5.2.3 Declassifying Content

Important:

You cannot declassify content that had the Restricted Data or Formerly Restricted Data supplemental markings assigned. The Downgrade On field is disabled for content with a restricted supplemental marking history.

Use this procedure to completely declassify an item, either after receiving a review notification (as part of a disposition instruction) or ad hoc. If an item is exempt from declassification, an exemption reason must be entered.

After content has been declassified, access to the content is unrestricted and in the absence of any other security restrictions, any user can view it.

If category authors must declassify content with a higher security classification level than they have, they cannot perform that action. A records manager or system administrator with the appropriate classification level must do it for them.

Permissions:

The Record.Edit right is required to perform this action. This right is assigned by default to the Records Officer and Records Administrator roles.

Use the previously described procedure to find an item to use. Choose Edit then Declassify from the Page menu.

The Declassify Page opens. It is similar to the Review Classification Page with the addition of fields to specify the declassification.

Provide the following required information in the marked fields:

The date and time of the declassification

The person (or other entity) who declassified the item

The reason for the declassification

When done, click Submit Update.

5.2.4 Undoing a Cutoff

After undoing a cutoff, the item is no longer cut off. Open the Content Information Page for the item. Choose Set Dates then Undo Cutoff from the Page menu.

Permissions:

The Record.UndoCutoff right is required to perform this action. This right is assigned by default to the predefined Records Administrator role.

6 Managing Physical Content

This section discusses the creation and management of physical items with Physical Content Management. It covers the following topics:

Section 6.1, "Managing Physical Items"

Section 6.2, "Importing Physical Content Manually"

Section 6.3, "Processing Physical Content"

6.1 Managing Physical Items

As opposed to internal electronic content managed by content management products, no copy of external, physical content is stored in the repository. Only its metadata (including storage information and retention schedule, if any) is stored when the information is checked in to the system.

When a user checks in an external, physical content item, the user must provide its basic metadata information and specify where the item is stored by selecting a location in the defined storage space hierarchy. If the user has the appropriate privileges, a retention schedule can also be assigned to the item, which determines its life cycle.

Physical items can be created within other physical items. This may be useful in situations where a "container" physical item is needed (for example, of object type Box add "content" physical items within it (for example, of object type Folder).

This section discusses the tasks involved in managing physical items. Some tasks are allowed for administrators and for end users while others are restricted only to people with administrative privileges.

The following user tasks are discussed in the Oracle WebCenter Content User's Guide for Records:

Creating a physical item

Creating a physical item within another item

Editing a physical item

Moving a physical item

Adding physical items to a content basket

Marking physical items as reviewed

Viewing reservations for physical items

The following tasks can be performed by administrators and are discussed in the following subsections:

Section 6.1.1, "Deleting a Physical Item"

Section 6.1.2, "Freezing and Unfreezing a Physical Item"

Section 6.1.3, "Printing a Label for a Physical Item"

6.1.1 Deleting a Physical Item

Permissions:

The PCM.Physical.Delete right is required to perform this task. This right is assigned by default to the PCM Administrator role.

Use this procedure to delete a physical item. When deleting a physical item, its metadata, storage, and retention information are removed from the repository. Therefore, the item can no longer be tracked and managed.

A physical item cannot be deleted if it has other physical items contained within it.

Search for the physical item to delete.

On the search results page, choose the Delete External Item option in the item's Actions menu.

You can also choose the Delete External Item option on the Physical Item Information Page.

The physical item is deleted immediately, without any further prompts. If no errors occur, a message is displayed stating the physical item was deleted successfully.

6.1.2 Freezing and Unfreezing a Physical Item

Permissions:

The Record.Freeze/Unfreeze right is required to perform this task. This right is assigned by default to the Records Administrator role. This right is not assigned by default to any PCM roles.

Use this procedure to freeze or unfreeze a physical item.

Freezing a physical item inhibits disposition processing for that item. For example, it will not be flagged for destruction, even if the action is due, until the item is unfrozen (when its frozen status is revoked). This may be necessary to comply with legal or audit requirements (for example, because of litigation).

More than one freeze can be applied to an item. View the freeze details for the item to see a list of all freezes currently applied to the item.

If a physical item containing other physical items is frozen, all of those items are also frozen.

After a physical item is frozen, its metadata cannot be edited.

To freeze a physical item, complete the following steps:

Search for the physical item to freeze.

On the search results page, choose Edit then Freeze in the item's Actions menu.

You can also choose Edit then Freeze on the Physical Item Information Page.

To freeze all items on the search results page, choose the Freeze Results option in the Page menu.

In the Freeze Name list, select the freeze to be applied to the item. The list contains all defined freezes. A reason can be given for the freeze or leave the text box empty.

Click OK to confirm the freeze. Click Cancel to abort the entire action.

If confirmed, the information page of the affected item displays Is Frozen: Yes and a Details link, which links to a detailed page for the item.

After an item is frozen, the freeze reason cannot be edited. If the freeze is no longer correct, unfreeze the item and freeze it with a new reason.

To unfreeze a physical item (cancel its frozen status), complete the following steps:

Search for the physical item to unfreeze.

On the search results page, choose Edit then Unfreeze in the item's Actions menu.

You can also choose Edit, then Unfreeze on the Physical Item Information Page.

The Unfreeze dialog opens.

In the Freeze Name list, select the freeze to be canceled for the item. The list contains all freezes currently applied to the item (at the item level). If needed, provide a reason for the unfreeze action or leave the text box empty.

Click OK to confirm. Click Cancel to abort the entire action.

If confirmed, the Retention Schedule Information area of the Content Information page displays Is Frozen: No and no Details link is displayed.

Important:

Multiple freeze may be applied to an item. Therefore, after an item is unfrozen, the Actions menu for the item may continue to include an Unfreeze option if other freezes are still applied to the item.

6.1.3 Printing a Label for a Physical Item

Permissions:

The PCM.Admin.PrintLabel right is required to perform this task. This right is assigned by default to the PCM Administrator role.

Use this procedure to print a label for a physical item. By default, the label contains a barcode for the item, and its name, title, security group, and account (if applicable).

Search for the physical item for which to print a label.

On the search results page, click Create Report then the type of label.

You can also choose the Print Label option on the Physical Item Information Page.

6.2 Importing Physical Content Manually

If an import file already exists for physical content, that data can be imported into the system for tracking by PCM. This section describes the format for the file needed for correct importing.

6.2.1 Required File Format

The import file to be used must be an .hda file with three result sets:

Section 6.2.1.1, "LocalDataProperties"

Section 6.2.1.2, "ImportExportManifest"

Section 6.2.1.3, "ExternalItemsExtItems"

In the following sections with examples, blank lines must be included where shown.

6.2.1.1 LocalDataProperties

This result set is used for the local data used by the Import service when importing the data. Set aIncludeERM_Physical=1 for physical data to be imported.

@Properties LocalData
aIncludeERM_Physical=1
blFieldTypes= dCreateDate date,dLastModifiedDate date
blDateFormat='{ts' ''yyyy-MM-dd HH:mm:ss{.SSS}[Z]'''}'!tAmerica/Chicago
@end

If importing dates, the data must be in the format {ts 'yyyy-mm-dd hh:mm:ss.mmm'} if using the blDateFormat property set as shown in the Local Data result set. That format can be modified but imported dates must then be in the same format.

6.2.1.2 ImportExportManifest

This result set provides the import function with the necessary data to import physical items. This result set can be copied into an .hda file as is.

@ResultSet ImportExportManifest
28
Name
Order
Caption
ResultSetName
ExportScript
ExportConditions
ExportClass
ExportAction
ExportParameters
ExportActionCopy
ImportScript
ImportConditions
ImportClass
ImportAction
ImportParameters
ImportPassName
UpdateClass
UpdateAction
UpdateParameters
UpdatePassName
UpdateForced
DeleteClass
DeleteAction
DeleteParameters
DeletePassName
Group
dSource
idcComponentName
aIncludeERM_Physical
300
csaIncludeExternal
ExternalItemsExtItems
<$hasCustomRights("ecm.pcm.physical.read")$>

Service
EXPORT_EXTERNAL_ITEMS
dSource,Physical

 <$hasCustomRights("ecm.pcm.physical.create")$>

Service
CREATE_EXTERNAL_ITEM

Service
EDIT_EXTERNAL_ITEM

content
Physical

@end

6.2.1.3 ExternalItemsExtItems

This result set contains the physical data being imported.

@Result Set ExternalItemsExtItems
11
dID 3 19
dDocName 6 100
dDocTitle 6 200
dDocAuthor 6 30
dDocType 6 30
dSecurityGroup 6 30
dPermLocation_Barcode 3 19
dActualLocation_Barcode 3 19
dExtObjectType 6 30
dMediaType 6 32
dSource 6 8
@end

Important:

Set only one location value for each current and permanent location. The following list shows multiple options for setting these values.

The following fields are required:

dID: The document identifier. This field can be left blank, but the field has to be in the definition. The system assigns a value if this is left blank.

dDocName: The document name.

dDocTitle: The document title.

dDocAuthor: The assigned author/creator.

dDocType: The assigned document type.

dSecurityGroup: The assigned security group.

dExtObjectType: The object type for the item being imported (for example, a box or a document). The object type must exist in the system prior to importing.

dSource: The source identifier. This must be set to Physical.

dPermLocation_Barcode: The permanent location value. Set this value if the location value is the barcode value of the storage or container item where the object is being assigned.

dActualLocation_Barcode: The current location value. Set this value if the location value is the barcode value of the storage or container item where the object is being assigned.

dPermLocation: The permanent location value. Set this value if the location value is the dObjectID value of the storage item where the object is being assigned.

dActualLocation: The current location value. this value if the location value is the dObjectID value of the storage item where the object is being assigned.

dPermContainer: The permanent container location value. Set this value if the location value is the dID of the contain item where the object is being assigned.

dActualContainer: Set this value if the location value is the dID of the contain item where the object is being assigned.

The following fields are optional:

dMediaType: Used to assign a media type to an item.

dBarcode: Used to provide a specific barcode for an item. Leave this blank and the system assigns the dDocName as the barcode.

Include any custom fields or other fields required for import.

6.2.2 Sample File

The following sample file demonstrates all result sets in an .hda file.

<?hda version="10.1.3.5.1 (090717)" jcharset=UTF8 encoding=utf-8?>
@Properties LocalData
aIncludeERM_Physical=1
blFieldTypes=xRecordFilingDate date,xArchiveDate date,xRecordCutoffDate
date,xRecordExpirationDate date,xRecordObsoleteDate date,xNewRevisionDate
date,xPublicationDate date,xRecordActivationDate date,xRecordSupersededDate
date,xRecordCancelledDate date,xRecordDestroyDate date,xDateClosed
date,xRecordRescindedDate date,xNoLatestRevisionDate date,xDeleteApproveDate
date,xRecordReviewDate date,xSuperSupersededDate date,dCreateDate
date,dLastModifiedDate date
aIncludeChargeTransactions=0
dLastModifiedDate={ts '2009-06-01 17:00:00.000'}
aExportDate=6/01/09 5:00 PM
blDateFormat='{ts' ''yyyy-MM-dd HH:mm:ss{.SSS}[Z]'''}'!tAmerica/Chicago
@end
@ResultSet ImportExportManifest
28
Name
Order
Caption
ResultSetName
ExportScript
ExportConditions
ExportClass
ExportAction
ExportParameters
ExportActionCopy
ImportScript
ImportConditions
ImportClass
ImportAction
ImportParameters
ImportPassName
UpdateClass
UpdateAction
UpdateParameters
UpdatePassName
UpdateForced
DeleteClass
DeleteAction
DeleteParameters
DeletePassName
Group
dSource
idcComponentName 6 30
aIncludeERM_Physical
300
csaIncludeExternal
ExternalItemsExtItems
 <$hasCustomRights("ecm.pcm.physical.read")$>

Service
EXPORT_EXTERNAL_ITEMS
dSource,Physical

 <$hasCustomRights("ecm.pcm.physical.create")$>

Service
CREATE_EXTERNAL_ITEM

Service
EDIT_EXTERNAL_ITEM

content
Physical

@end
@ResultSet ExternalItemsExtItems
11
dID 3 19
dDocName 6 100
dDocTitle 6 200
dDocAuthor 6 30
dDocType 6 30
dSecurityGroup 6 30
dPermLocation_Barcode 3 19
dActualLocation_Barcode 3 19
dExtObjectType 6 30
dMediaType 6 32
dCreateDate 5 20
dSource 6 8

B0000003050
ImportTestBox
sysadmin
ADACCT
Public
TSTIMPORT
TSTIMPORT
Box

{ts '2009-06-04 11:50:50.497'}
Physical

F0000003050
ImportTestFolder
sysadmin
ADACCT
Public
B0000003050
B0000003050
Folder

{ts '2009-06-04 11:50:50.497'}
Physical
@end

6.3 Processing Physical Content

This section explains how to process physical items used by PCM. It discusses the following topics:

Section 6.3.1, "Retention Schedules for Physical Items"

Section 6.3.2, "Disposition Events for Physical Items"

Section 6.3.3, "Pending Options for Physical Items"

Section 6.3.4, "Audit Log Files for Processed Events"

6.3.1 Retention Schedules for Physical Items

Physical items can be assigned retention schedules that define their life cycle. This links the physical item to a set of retention and disposition rules, which specify how long an item should be stored and when and how it should be disposed.

The same retention schedules and disposition rules may be used for physical items as for electronic items, but disposition rules can be defined specifically for physical items.

6.3.2 Disposition Events for Physical Items

A disposition event is any action needing to be performed on an item as part of its retention schedule (for example, after the retention period of the item has ended). Disposition events for physical items consist of three steps:

Approving the event.

Performing the action(s) associated with the event such as physical destruction of the affected item(s).

Marking the event as completed.

Note:

The Destroy disposition event requires two steps for physical items, but not for electronic items. This is because the software can destroy electronic items for you, but it cannot destroy physical items. Destruction of physical items requires human intervention.

Physical items can be assigned the same disposition actions as electronic items. For an in-depth discussion of the available disposition actions, see the Oracle WebCenter Content Setup Guide for Records.

Due to the nature of physical items, some of the available disposition actions are less relevant than for electronic items:

Disposition actions related to revisions because physical items cannot be revisioned:

Deleting old revisions

Checking in new revisions

Deleting previous revisions

Deleting revisions

Deleting all revision

Disposition actions involving digital data:

Scrubbing data. This includes overwriting it multiple times to prevent recovery as part of the destruction process.

If any of these disposition actions are assigned to physical items and they are due for completion, nothing specific needs to be done and they can be marked completed immediately.

6.3.3 Pending Options for Physical Items

Any pending events for physical items are included on the My Approval List page. To access this page, choose Records then Approvals from the Top menu. Choose the type of approval to perform:

Reviews

Dispositions

To complete an action such as approval, review or a disposition, choose the appropriate completion action from an item's Actions menu. Some dispositions require approval before disposition processing.

Note:

If the event action does not move to the completion list, then all affected items are frozen and cannot be processed. If the event action does move but also remains in the approval list, some affected items are frozen. The frozen items will not be processed until they are unfrozen.

6.3.4 Audit Log Files for Processed Events

When a disposition event for physical items is completed, an audit log file is created automatically and, if possible, is checked into the repository using the default metadata for audit logs. These checked-in log files can be used for audit trail purposes or as a verification tool.

Use the Search Audit Trail Page to search for disposition event that were processed for physical items by setting the Source field to 'Physical'.

The Admin.Audit right is required to search the audit trail.

Note:

All completed disposition actions are included in the audit trail.

7 Managing Reservations and Barcodes

Physical Content Management offers circulation services for physical content items, in much the same way as a library circulates content. Users can receive items, keep them for a specific period then return them so they can be stored at their designated location again for someone else to check out. Users can also put a hold on unavailable items. If more than one person makes a reservation request for an item they are placed on a waiting list, which specifies the order in which people made a reservation for the item. Barcode functionality is used in conjunction with reservations to easily track items that are either checked out or requested.

This chapter covers the following topics:

Section 7.1, "Reservation Details"

Section 7.2, "The Reservation Process"

Section 7.3, "About Barcodes"

Section 7.4, "Managing Barcodes"

The following tasks are typically performed when using reservations. These tasks can be performed by users depending on how the system has been set up. Therefore, these tasks are all discussed in the Oracle WebCenter Content User's Guide for Records:

Creating a reservation request

Editing a reservation request

Deleting a reservation request

Searching for reservations

Saving reservation search results

Viewing reservations for physical items

Viewing your own reservation requests

Editing a request item

Canceling a request item

Deleting a request item

Changing the status of a request item

7.1 Reservation Details

Reservations in Physical Content Management are handled using a special criteria workflow called ReservationProcess, which is used for approval and notification purposes. This workflow must be configured and enabled. See the Oracle WebCenter Content Setup Guide for Records for details about setting up that work.

The reservation workflow is not used if the Check in internal content item for reservation workflow setting on the Configure Physical Content Management Page is disabled. Users can still make reservations but e-mail notifications are not received (not even by the system administrator). If this is done, a different procedure to process reservations should be in place.

Users with the predefined PCM Requestor role can make reservations for physical items. Users with the predefined 'pcmadmin' role can also edit and process reservation request.

By default, if a user submits a reservation request for one or more items, a new content item is checked into the repository in the Reservation security group. If the workflow is enabled, this content item automatically enters the ReservationProcess workflow and the administrator receives a workflow review notification about the request.

Default metadata values can be set to be assigned to the reservation workflow item checked into the repository. See the Oracle WebCenter Content Setup Guide for Records for details.

The person in the administrator role receives e-mail notifications about pending reservations and the requesting user is not notified. Change this behavior by changing the ReservationGroup alias in the User Admin utility. For example, you could set up the workflow to also send e-mail notifications to the user who made the reservation request.

Clicking the Review workflow item link in the notification e-mail opens the Workflow Review for Request page, where the administrator can acknowledge the reservation request. As soon as the administrator clicks Approve on this page, the reservation request exits the workflow.

The administrator can then proceed and fulfill the reservation request in accordance with the applicable procedures within the organization.

The reservation process can be modified to suit an organization's need by changing the ReservationProcess workflow. For more information about workflows, see the Oracle WebCenter Content Application Administrator's Guide for Content Server.

By default, each user can place only one reservation request for the same item. If users make reservation requests on behalf of multiple people (for example, manager assistants), it may be useful to override this behavior. To do so, add the following variable to the physicalcontentmanager_environment.cfg configuration file:

AllowMultipleRequests=true

7.1.1 Reservations History

All completed reservation requests are automatically logged in the reservations history. A reservation request is considered completed if none of its request items are still pending (in process), on a waiting list, or checked out.

By default, completed reservation requests are stored in the history log until it is deleted. A log is kept in the audit history table until it is archived.

Limit the maximum number of days a completed request is included in the history by modifying settings on the Configure Physical Content Management Page.

An administrator can view the current reservations history by searching for reservations with the Completed field set to 'Yes'.

7.2 The Reservation Process

The following is a typical fulfillment process of a reservation request:

A user creates a reservation request for one or more physical items.

As soon as the user submits the reservation request, the status of each requested item is automatically set to In Process. If it was already In Process or Checked Out, it is set to Waiting List. For information about data used in reservation requests, see Section 7.2.1.1, "Request Status," Section 7.2.1.2, "Transfer Method," and Section 7.2.1.3, "Priority."

A reservation workflow is initiated and the administrator receives an e-mail notification to review the reservation request.

The administrator acknowledges the reservation request. If any items in the reservation request are not available or should be denied, the administrator can change their status accordingly.

All available requested items (not already checked out) are gathered from their storage location, in accordance with the organization's procedures. During this process, an appropriate transaction barcode is scanned to indicate it is checked out, the requestor's barcode is scanned, and the barcode for the desired item is scanned.

The status of each available requested item is changed to Checked Out automatically after the barcode file is uploaded to PCM and the data is synchronized.

When the item's status changes to Checked Out, its current location (as shown on the Physical Item Information Page) is automatically set to the deliver-to location specified when the reservation request was created. If no deliver-to location was specified, the current location is set to OTHER. The current location comment on the Physical Item Information Page is set to the location comment specified for the associated reservation request. If no comment was provided, it is set to the login name of the user who made the reservation.

The requesting user can be notified and the reservation fulfilled in accordance with the applicable procedures within the organization. This is not handled by PCM but by the organization.

The user keeps the items for a specific number of days. If a bar code system is in place, after the item is returned, the item's barcode is once again scanned, the barcode for the location of the item's placement is scanned, and a transaction barcode is scanned to indicate the item is checked in and its location.

The status is changed to Returned and its current location set to its assigned storage location automatically after the barcode file is uploaded to PCM.

If a waiting list exists for the item, the status for the next requestor on the list should be changed from Waiting List to In Process, so the item can be processed for the user. This can be done manually on any of the reservation pages, but if a barcode scanner is used to scan the item for checkin, it can be done automatically, depending on how the system is configured.

The status of the item continues to be Returned until the reservation is deleted. This can be done manually or automatically (after a certain number of days).

Depending on the procedures in place at the site, a charge may be levied for reservations and processing. Chargebacks and billing are discussed in the Oracle WebCenter Content User's Guide for Records.

7.2.1 Reservation Request Properties

Each reservation request has several properties, including the following:

Section 7.2.1.1, "Request Status"

Section 7.2.1.2, "Transfer Method"

Section 7.2.1.3, "Priority"

7.2.1.1 Request Status

The request status specifies the current status for a reserved physical item, which can be any of the following:

Waiting List: The request item is currently already checked out to someone else. It will become available to the next requestor upon its return (unless the system administrator chooses to override the waiting list order).

In Process (initial default): The reserved item is available and is being prepared for delivery. Only one request item for a reservation can have the In Process status.

Not Found: The request item could not be located in its designated location.

Unavailable: The request item cannot currently be processed for delivery.

Denied: The reservation request has been rejected by the administrator and cannot be fulfilled.

Cancelled: The reservation request was called off before it could be fulfilled.

Checked Out: The reserved item is currently in the possession of someone as part of a reservation request. If a physical item is checked out, its current location (as shown on the Physical Item Information page) is automatically set to the value of the Deliver To Location field for the associated reservation request. If no value was entered in this field, the current location is set to OTHER. Also, the current location comment as shown on the Physical Item Information page) is set to the location comment specified for the associated reservation request. If no comment was provided, it is set to the login name of the user who made the reservation.

Overdue: The reserved item is currently checked out to someone who has failed to return the item within the configured checkout time. As a result, the reservation request cannot currently be fulfilled.

By default, an e-mail notification is sent out to the user who has an overdue item. This e-mail notification can be disabled.

Returned: The checked-out item was returned to the storage repository, so it is available for other users to reserve and check out.

A reservation request is considered completed if none of its request items are still pending (in process), on a waiting list, or checked out (including overdue).

The PCM.Reservation.Process right is required to change the status of a reservation request item. By default, this right is assigned to the predefined 'pcmadmin' role.

7.2.1.2 Transfer Method

The transfer method specifies how the person who made the request (the requestor) will receive the reserved item. Users specify the transfer method when a reservation request is created. The following transfer methods are supported:

Copy: The physical content item will be duplicated and the copy will be provided to the intended recipient. The copy can be physical (for example, a copied DVD) or electronic (for example, an ISO image of a CD).

Fax: The physical content item will be faxed to its intended recipient.

Mail: The original physical content item will be mailed to its intended recipient.

Pickup: The intended recipient will pick up the physical content item in person.

E-mail: The content item will be e-mailed to its intended recipient.

The default transfer method is set on the Configure Physical Content Management Page.

7.2.1.3 Priority

The priority of a reservation request specifies the urgency with which it needs to be fulfilled. User specify the priority when they create a reservation request. The following priorities are supported:

No Priority: Delivery of the requested item does not have any particular priority (there is no rush). The item can be delivered in accordance with the applicable fulfillment procedures.

ASAP Rush: The requested item should be delivered to its intended recipient as soon as possible after the reservation was made.

This Morning: The requested item should be delivered to its intended recipient the same morning the reservation was made.

Today: The requested item should be delivered to its intended recipient the same day the reservation was made.

This Week: The requested item should be delivered to its intended recipient the same week the reservation was made.

The default priority is set on the Configure Physical Content Management Page.

7.2.1.4 Request Item Actions

If you are an administrator, you can perform actions on a request item to change its status as part of the reservation fulfillment process. These actions are accessible through the Actions menu for a request item on the Reservation Search Results Page or the Items for Request page. You can also perform the actions on multiple items simultaneously using the Actions menu on the Items for Request page.

Not all actions may be available for a particular request item, depending on the item's current status. For example, if the item is currently checked out, it can only be deleted or returned.

The following actions are supported:

Delete: Deletes an item from a reservation request. If deleted, the request for that item is not included in the reservation log. The item is no longer in the item list for the reservation request. This option is available only if the system has been set up to allow users to delete items from a reservation request. In addition, requested items can be deleted only by a user with the PCM.Reservation.Delete right (assigned to the predefined PCM Administrator role by default).

Deny: Rejects the reservation request for an item. The item will remain to be part of the reservation request, but it will not provided to the requestor.

Not Found: Changes the status of an item because it could not be located in its designated location. The item will remain to be part of the reservation request, but it cannot currently be provided to the requestor.

Unavailable: Changes the status of an item because it cannot currently be processed for delivery. The item will remain to be part of the reservation request, but it cannot currently be provided to the requestor.

Cancel: Cancels the reservation request for an item before it is fulfilled. If a request item is cancelled, the request for that item is still included in the reservation log (the item is still on the item list for the reservation, with its status set to cancelled). Request items can be cancelled only users with the PCM.Reservation.Edit right (assigned to the predefined 'pcmadmin' role by default). Only request item with the In Process status can be cancelled.

Check Out: Changes the status of an item because it was handed off to its intended recipient, who can now keep the item for the configured checkout period. After checking out a request item, its current location (as shown on the Physical Item Information Page) is automatically set to the value of the Deliver To Location field for the associated reservation request. If no value was entered in this field, the current location is set to OTHER. Also, the current location comment shown on the Physical Item Information Page is set to the location comment specified for the associated reservation request. If no comment was provided, it is set to the login name of the user who made the reservation.

Returned: Changes the status of a checked-out item because it was returned handed off to its intended recipient, who can now keep the item for an agreed period.

7.3 About Barcodes

Barcode files are generated by barcode devices that scan storage information contained in barcodes located on physical content items or storage containers. A barcode is a machine-readable symbol used to store bits of data. In the context of physical content management, they can be used for purposes of identification, inventory, tracking, and reservation fulfillment.

Figure 7-1 Example of Barcode

Barcodes can be printed on labels attached to physical content items or storage containers holding such items (for example, a box). This helps track their location and status. User labels can also be created to help process reservation requests by users.

Important:

View barcode reports using HTML but print reports using PDF in order to ensure proper formatting.

The following technical information applies to barcodes in PCM:

Physical Content Management uses the Code 3 of 9 barcode standard (also called Code 39). This is a widely used standard for alphanumeric barcodes that can store upper-case characters, decimal numbers, and some punctuation characters (dash, period, dollar sign, slash, percent sign, and plus symbol).

All lower-case letters are automatically converted to upper case. For example, if a user login is 'jsmith' then its barcode value is 'JSMITH'.

Any accented letters and double-byte characters (such as Japanese and Korean) are encoded in their hexadecimal values. For example, if a user login is 'kmüller', then its barcode value is 'KMC39CLLER' (Ü = hex C39C). Therefore the barcode length increases as multiple hexadecimal characters are used to represent each accented letter or double-byte character.

Barcode values for users default to their login names. This behavior can be changed for a user by setting a specific, unique barcode value for the user in the User Admin utility.

After scanning barcode information using a barcode reader, load the information into Physical Content Management. This can save time and money, and is especially useful to process large numbers of items (for example, during the initial Physical Content Management implementation).

There are two ways to load barcode information into Physical Content Management:

Directly using the PCM Barcode Utility software.

Manually by processing generated barcode file. For details, see Section 7.4.5, "Processing a Barcode File."

7.3.1 Barcode Files

Barcode files are generated by barcode scanners that read storage information from barcode labels and write this information to a file. Use the optional PCM Barcode Utility to directly load barcode information into the system or the barcode file can be processed manually.

Barcode files are plain-text files that are viewable using any text editor, such as the following example.

H 20050721130204 00 0000000000
20050721130145 00 2000
20050721130151 00 +W1R1R1B1S1P3
20050721130152 00 B3

Important:

Barcode files are created by barcode scanners and processed by Physical Content Management, and there is normally no reason to view or modify barcode files.

7.3.1.1 Barcode File Actions

When a barcode file is processed (automatically or manually), one of three actions is performed (specified for each item in the barcode file):

Section 7.3.1.1.1, "Check In"

Section 7.3.1.1.2, "Check Out"

Section 7.3.1.1.3, "Set Home & Actual"

7.3.1.1.1 Check In

The Check In barcode action assigns an item to the location specified in the barcode file for the item. It is only the current location that is set, not the permanent location. Both the location and the item must already exist in Physical Content Management. If neither exists, an error is reported.

[The location must already exist in the defined storage space hierarchy in Physical Content Management. If an item to be checked in does not yet exist in Physical Content Management, it is created and assigned to the specified location. If the item already exists, its current location is updated to match the value in the barcode file.]

7.3.1.1.2 Check Out

The Check Out barcode action checks an item out to the user specified in the barcode file for the item (typically obtained by scanning a user label). The status for the item is set to Checked Out and its checkout user to the specified user (both values are shown on the Physical Item Information page). The item's current location is automatically set to the value of the Deliver To Location field for the associated reservation request (if there is one). If no value was entered in that field or if no reservation request exists, the current location is set to OTHER, and the Location Comment field will show the name of the checkout user.

7.3.1.1.3 Set Home & Actual

The Set Location barcode action assigns an item to the current and permanent locations specified in the barcode file for that item, allowing it to be moved to a different location. Both the locations and the item must already exist in Physical Content Management. If any of them do not exist, an error is reported.

The locations and items must already exist in the defined storage space hierarchy in Physical Content Management. The item's current and permanent locations are updated to match the values in the barcode file.

7.3.2 The Barcode Utility Software

The Barcode Utility software is a Windows application providing an interface to the Videx LaserLite barcode scanner used with Physical Content Management. With this functionality, information can be read into the barcode scanner and uploaded into PCM. The barcode information can also be read and written to a file for manual processing at a later time. In addition, the Barcode Utility enables the reprogramming of the barcode scanner, should that be necessary.

The Barcode Utility software for Videx is provided but not automatically installed with the PCM software. To use, install the software after enabling PCM. The installer for the Barcode Utility is included on the PCM software distribution media.

Microsoft .NET Framework Version 1.1 Redistributable Package is needed to run the Barcode Utility. If not already on the computer, it can be downloaded from the Microsoft website at www.microsoft.com

The Barcode Utility can be installed on any computer that has a web connection to the server.

Important:

If you upgrade the Barcode Utility from an earlier version, you must de-install the existing instance before installing the new release. If you do not, an error message is reported during the installation and you will not be able to proceed.

To install the Barcode Utility, complete the following steps:

Locate the executable installer file, named BarcodeUtility.exe on the Physical Content Management distribution media. This is typically stored in the ucm\Distribution\urm\language directory (different files are included for the different languages that are supported).

Double-click the setup.exe file to continue the installation.

Follow the instructions on screen to install the software.

From Start, select Programs, then select Oracle, then select Barcode Utility, then select Barcode Utility. You can also double-click the utility icon on the Windows desktop.

An interface is also provided to a Wedge Reader type of scanner that plugs in directly to the computer. If that type of scanner is enabled, data is automatically uploaded to a location on the screen where the cursor rests after three scans have taken place.

7.4 Managing Barcodes

This section discusses the following common barcode tasks:

Section 7.4.1, "Programming the Barcode Scanner"

Section 7.4.2, "Uploading Barcode Data Directly to PCM"

Section 7.4.3, "Saving Barcode Data to a File"

Section 7.4.4, "Uploading Previously Saved Barcode Data to PCM"

Section 7.4.5, "Processing a Barcode File"

For details about enabling a mobile bar code scanner, see the Oracle WebCenter Content Setup Guide for Records.

7.4.1 Programming the Barcode Scanner

The Videx Wand scanner may be pre-programmed for use at installation. Use the following procedure, if needed, to program the barcode scanner:

Start the Barcode Utility application.

The Main Barcode Utility Screen opens.

Choose Options then Program Videx Wand.

The Program Videx Barcode Wand Screen opens.

Choose the type of scanner to be programmed from the Communication Device list.

Choose the communication port where the device is connected.

Click Program.

A message appears, indicating that the application is communicating with the scanner. The dialog closes when the programming finishes.

Click Done on the Main Barcode Utility Screen.

Push the Scan button on the scanner.

7.4.2 Uploading Barcode Data Directly to PCM

After gathering data with the scanner, the data can be directly uploaded to the server running the PCM software. The data can also be saved to a file and uploaded later.

Complete the following steps to upload the scanned barcode data directly to PCM:

Connect the scanner to the computer where the Barcode Utility is installed, either by placing the scanner in its base station or by using the connection cable.

Start the Barcode Utility application.

The Main Barcode Utility Screen opens.

Select the scanner type.

Select the communication port where the barcode scanner is installed. Normally this is COM1, a commonly used serial port.

Make sure that Download To File Only and Allow File Selection are both deselected.

Click Process.

A prompt appears to begin the upload process.

Select Yes to continue.

Select the host name of the instance where data files will be uploaded. The software must be installed on this computer.

To configure the list of available hosts, complete the following steps:

Click Advanced.

The Configure Host List Screen opens.

Enter the name of the instance where the repository is stored and the CGI URL for the instance.

Click Update to add multiple names.

Click Done when finished.

Enter the user name and password for a person who is allowed to upload data. To upload data, the user must have the predefined PCM Administrator role. Click OK after selecting the user name.

The data is now transferred from the scanner to the PCM system. After all data has been transferred, a message is displayed, indicating the operation is complete.

Click OK to continue.

Important:

If you select No when asked to confirm the upload, the data is erased from the barcode scanner and nothing is uploaded. The data is still available in a file called DATA.TXT (located in the installation directory of the Barcode Utility), but this file is overwritten the next time data is uploaded or saved to a file.

7.4.3 Saving Barcode Data to a File

Complete the following steps to save the scanned barcode data to a file:

Connect the scanner to the computer where the Barcode Utility is installed, either by placing the scanner in its base station or by using the connection cable.

Start the Barcode Utility application.

The Main Barcode Utility Screen opens.

Select the scanner type.

Select the communication port where the barcode scanner is installed. Normally this is COM1, a commonly used serial port.

Make sure Download To File Only is selected.

Click Process.

The data is stored in a file called DATA.TXT, which is located in the installation directory of the Barcode Utility. For details about uploading this data file at a later time see Section 7.4.4, "Uploading Previously Saved Barcode Data to PCM."

Note:

Data is always stored in a file named DATA.TXT. If not renamed, the file is overwritten the next time data is downloaded and stored as a file.

7.4.4 Uploading Previously Saved Barcode Data to PCM

If barcode data was saved to a file for later processing, use the Barcode Utility application to move the data to the PCM software for use.

Complete the following steps to upload a previously saved barcode data file:

Start the Barcode Utility application.

The Main Barcode Utility Screen opens.

Make sure Allow File Selection is selected and click Process.

A file selection dialog is displayed, showing the contents of the Barcode Utility installation directory (which is the default location of saved barcode data files).

Select the file to be uploaded, or navigate to the directory where the data files were stored and select a file from that location. Click Open.

The Barcode Upload Screen opens.

Select the host name of the instance where the data file will be uploaded. The software must be installed on this computer.

If you need to configure the list of available hosts, complete the following steps:

Click Advanced.

The Configure Host List Screen opens.

Enter the name of the instance where the repository is stored and the CGI URL for the instance.

Click Update to add multiple names.

Click Done when finished.

Enter the user name and password for a person who is allowed to upload data. To upload data, the user must have the predefined PCM Administrator role.

Click Submit.

The barcode data file is processed and uploaded to the selected instance.

After the file upload has completed, a message is displayed. Click OK.

The Barcode Upload Results Screen opens, allowing a review of the results of the upload.

Click Done when finished.

7.4.5 Processing a Barcode File

Permissions:

The PCM.Barcode.Process right is required to perform this action. This right is assigned by default to the PCM Administrator role.

Use this procedure to process a barcode file containing information obtained using a barcode scanner.

Choose Physical then Process Barcode File from the Top menu.

The Barcode Processing Page opens.

Click Browse to select a barcode file to be processed.

A file selection dialog is opened.

Navigate to the barcode file to be processed, select it, and close the file selection dialog.

Click Process File.

The barcode file is processed, and the Barcode File Processed Page opens. If any errors occurred, these are reported in the Message column. Click the Info icon to see more specific information about the error message.

When finished viewing the results of the barcode processing, click OK to return to the Barcode Processing Page.

8 Setting Up PCM Offsite Storage

This section explains how to set up and manage offsite storage in Physical Content Management. Offsite storage is an optional feature that enables users to set up requests for storage and to track storage processing.

If offsite storage functionality is enabled on the system, the total size allowed for the content ID for a physical item is 11 characters. When setting up offsite storage, verify if automatic assignment of IDs is enabled and if so, make sure the content prefix is set to 5 characters or less.

This chapter covers the following topics:

Section 8.1, "Using Offsite Storage"

Section 8.2, "Managing Offsite Storage"

8.1 Using Offsite Storage

Customers can integrate storage with Iron Mountain SafeKeeper PLUS and other offsite storage facilities.

Important:

Iron Mountain configurations will vary from customer to customer. Be sure to test the integration in a development instance before using for production data.

The Offsite Storage link is an automated interface process for daily inventory and activity management between the Records system and offsite storage. This interface provides the following features:

The automated creation of requests, both reference and permanent, for boxes and files from offsite storage.

The automated creation of pickup requests for new and re-filed boxes and files for storage and return to the offsite location.

Transfer of transmittal and individual list data for new boxes and files, and transmittal and list maintenance for existing boxes and files.

The creation of a nightly log file listing inventory transaction history for a given day. This serves as a confirmation and data synchronization between the two systems.

To use this functionality, first map default values for different types of storage file formats to districts where the content is stored. Types of file formats include legal storage, insurance, loans, medical, and other storage types. Default districts are provided and default values for the fields used for storage.

After setting up the mapping, specify the storage parameters on the checkin page for physical content. After the content is checked in, a criteria workflow can be started to handle the approval of items pending transfer. This workflow must be created and enabled before the Offsite functionality can work. See the Oracle WebCenter Content Setup Guide for Records for details about setting up this workflow. While not required, it is recommended that this workflow be used.

Iron Mountain is currently the primary offsite provider. After the appropriate configurations are in place, the files are first stored on the computer before being sent to and from Iron Mountain using File Transfer Protocol (FTP). After the files are compiled, they are uploaded to the /toplus directory in the software directory structure.

A confirmation file is sent from Iron Mountain and stored in the /fromplus directory in the Iron Mountain directory structure. A nightly history download log is also stored in the /fromplus directory after each night's district job is processed. Verify beforehand that the chosen FTP location has these directories already created.

Pickup lists are automatically created for items that must be transferred. Manual pickup lists can also be created as needed.

8.2 Managing Offsite Storage

The following aspects are required to use offsite storage:

Section 8.2.1, "Setting Up Default Customer Information"

Section 8.2.2, "Mapping New Districts"

Section 8.2.3, "Creating Manual Pickup Requests"

Section 8.2.4, "Browsing Uploaded Files"

Section 8.2.5, "Browsing Processed Files"

Section 8.2.6, "Transferring Files to Offsite Storage"

8.2.1 Setting Up Default Customer Information

First set up default customer information about the account to be used by the offsite provider. These defaults identify your company to the provider and are used to monitor and process offsite requests.

Follow these steps to configure defaults for offsite storage.

Choose Physical then Settings from the Top menu.

The Configure Physical Content Management Page opens.

Select Enable Offsite Storage Functionality then click Submit Update. The Configure Physical Content Management Page opens.

Refresh the browser window. Choose Physical then Offsite Storage then General Setup.

The Offsite Storage General Setup Page opens.

Fill in the necessary fields:

Customer ID: The customer ID used with this offsite storage facility.

Default District: The district to use. Select from a predefined list. If the district has not previously been defined, the definition must be mapped beforehand. For details, see Section 8.2.2, "Mapping New Districts."

FTP Address: Enter the address associated with the FTP site.

FTP User: Enter the user associated with the FTP site.

FTP Password: Enter the password associated with the FTP site.

Transfer checkboxes: Choose options associated with the transfer:

Automatically transfer new items: Enable automatic transfer of new items.

Automatically return checked-in items: Enable automatic returns of items that have been checked in.

Enable workflow: Start a workflow for this transfer action. The workflow must be created before this step. See the Oracle WebCenter Content Setup Guide for Records for details about creating the workflow.

Use general requestor for Offsite Requests: Choose a user from the list to use as the requestor. There is a limit of five characters for this value.

Box Identifier: Choose what identifier will be associated with the box. Options include Name or Title.

When done click Submit Update.

A message is displayed indicating the offsite storage data has been configured.

8.2.2 Mapping New Districts

Several default districts are provided with Physical Content Management to use for offsite storage. Reconfigure any of these districts as necessary for your particular offsite solution.

The district mapping uses a wizard that steps through each stage of the process. When one stage is finished, the wizard opens the next page in the process. For details about each page and the fields displayed, see Section A.6.2, "District Mapping Pages."

The values used to populate the option lists for each field are based on data provided by Iron Mountain. For details about the field values, consult Iron Mountain documentation.

Follow this procedure to map district data:

Choose Physical then Offsite Storage then Map District Metadata from the Top menu.

The Choose District Mapping Page opens.

Select a district to configure from the list by scrolling through the list and highlighting a selection. Click Configure to select the district.

The next page in the wizard appears. The process for mapping information is the same on each page. Scroll through the values provided for the different fields and highlight a selection.

Click Save to proceed to the next page in the process. Click Exit the Wizard to exit the process without saving selections. Click Reset to clear the selections on the current page. To move forward or back in the process and skip pages, select a different page from the Page menu.

Eight pages are available for configuration:

Map box metadata

Map standard file metadata

Map account file metadata

Map insurance (1) metadata

Map insurance (2) metadata

Map law metadata

Map loan file metadata

Map medical file metadata

When finished configuring districts, click Save. A message is displayed indicating a successful exit from the wizard.

8.2.3 Creating Manual Pickup Requests

This function can be used to create requests to the offsite storage provider for pick up of materials.

Use this procedure to set up pickup requests:

Choose Physical then Offsite Storage then Create Manual Pickup Request from the Top menu.

The Create Manual Pickup Page opens.

Select a district ID from the list of IDs.

Enter a pickup location or select a location by clicking Browse to look at stored locations.

Enter the remainder of the information on the page.

To discard entries, click Reset. When done, click Submit Update.

8.2.4 Browsing Uploaded Files

You can browse all of the uploaded files and view the status of the files. If a file has failed to upload, the upload request can be resent from this page.

Use this procedure to view files:

Choose Physical then Offsite Storage then Uploaded Files List from the Top menu.

The Browse Uploaded Files Page opens.

To work with a file, select the box next to the file name. To delete a file, choose Delete from the Table menu or the item's Actions menu. To resend a file for processing, choose Resend.

8.2.5 Browsing Processed Files

You can browse all of the processed files and view the status of the files. If a file has errors, you can then use this page to correct the errors.

Use this procedure to view files:

Choose Physical then Offsite Storage then Processed History Files List from the Top menu.

The Browse Processed History Page opens.

To delete a file, check the box next to the file name then choose Delete from the Table menu or the item's Actions menu.

8.2.6 Transferring Files to Offsite Storage

Transferring files for offsite storage occurs in two stages: files must first be generated then transferred.

To generate files for files for transferring, choose Physical then Offsite Storage then Generate Offsite Transfer Files from the Top menu.

To upload, download, or process the files, choose Physical then Offsite Storage then Upload, Download, Process Offsite Files from the Top menu. The files will be automatically transferred with other scheduled batch processes during the nightly services that are processed.

9 Scheduled Tasks

It is possible to set up a schedule to perform retention-related tasks at times that are more convenient for your environment. This chapter discusses scheduling tasks that can be performed at a later time. It covers the following topics:

Section 9.1, "Using Scheduled Tasks"

Section 9.2, "Managing Scheduling"

Important:

If jobs were scheduled in previous versions of this product, those jobs must be rescheduled. Schedule times and frequency are not automatically assigned when the product is updated.

9.1 Using Scheduled Tasks

Some of the tasks performed may involve large sets of content. Tasks such as processing retention assignments, performing archives, or customizing metadata may interfere with normal daily operations or put a heavy load on the system, which is undesirable during regular business hours.

With the scheduling feature tasks can be set to be performed at a later time, during off-peak times on the system. Freezes can also be scheduled to be performed at specific times. For details about creating a freeze, see the Oracle WebCenter Content Setup Guide for Records.

For details about viewing scheduled updates and searches, see Section 4.2, "Updating Information."

9.1.1 Changes in Scheduling From Previous Product Versions

The following changes have been made to scheduling from previous versions of this product:

Dispositions can no longer be scheduled and will be removed from any schedule after upgrading. See the Oracle WebCenter Content Setup Guide for Records for details about dispositions.

Scheduled freezes are migrated but they are not functional if the search engine type was changed (for example, from database to Oracle Text Search).

Scheduled screening reports are migrated but they must be modified to use the correct query and the correct report template. If a template is not chosen a default template is used.

Scheduled freeze notifications are not rescheduled after upgrading. The notifications should be resubmitted.

9.2 Managing Scheduling

This section discusses the following scheduling tasks:

Section 9.2.1, "Scheduling Screening Reports"

Section 9.2.2, "Editing Recurring Screening Reports"

Section 9.2.3, "Viewing Recurring Screening Report History"

Section 9.2.4, "Scheduling and Unscheduling Freezes"

Section 9.2.5, "Viewing Scheduled Job Information"

9.2.1 Scheduling Screening Reports

The scheduling functionality is discussed in detail in the Oracle WebCenter Content User's Guide for Records. This section provides an abbreviated overview of the process.

To schedule a screening report, first screen for information using the screening function. Select the source then choose the scheduling criteria such as name for the report, start date, indication if it will recur, and the recurrence frequency for the report. You can also subscribe to the report and be notified when the report is generated.

The screening report is then put in the queue of actions to be performed. All scheduled screening reports are generated daily at midnight by default.

9.2.2 Editing Recurring Screening Reports

To edit a recurring scheduled screening report, complete the following steps:

Choose Records then Scheduled then Screening Reports from the Top menu.

The Scheduled Screening Reports Page opens.

Choose an Edit option in the Actions menu of the screening report to modify:

Edit schedule: Change the scheduling criteria for the job. After clicking, the Edit Recurring Report Schedule Page opens. Change any schedule details and click Submit Update when done.

Edit criteria: Used to change the criteria used for screening. After clicking, the Screen for Topic Page opens. Choose the new criteria for screening and click Submit Update.

Edit subscription: If the user is subscribed to the report, that subscription can be changed to include other users or a group of users. Choose the new users and click OK when done.

9.2.3 Viewing Recurring Screening Report History

To view the history of recurring scheduled screening reports, complete the following steps:

Choose Records then Scheduled then Scheduled Screening Reports from the Top menu.

The Scheduled Screening Reports Page opens.

Choose Report History in the Actions menu of the recurring screening report whose history will be viewed.

The View History Page opens.

To view a report, click its link in the Name column.

9.2.4 Scheduling and Unscheduling Freezes

Use this procedure to schedule a recurring freeze of selected items. This optional feature will freeze any new items that match the search criteria specified from the search page.

To unschedule a freeze, select Records then Scheduled then Freezes. Select Unschedule from the Action menu of the scheduled freeze.

Search for the items to include in the scheduled recurring freeze.

On the Search Results page, choose Edit then Freeze All Search Results from the Table menu.

A dialog is displayed. Select the freeze reason from the list.

Enter a freeze reason (optional).

Select Schedule Recurring Freeze Inclusion then click OK.

The Scheduled Freezes Page opens.

9.2.5 Viewing Scheduled Job Information

Follow this procedure to view a list of all scheduled jobs (reports, freezes, and any other Oracle WebCenter Content scheduled jobs).

Choose Administration then Scheduled Jobs Administration from the Main menu. Choose Active Scheduled Jobs.

The Scheduled Jobs Listing Page opens, showing all scheduled jobs.

To view details about a particular job, click the Info icon for that job. To edit details about the scheduled job, select Edit from the Actions menu for a particular item.

The Job Information Page/Edit Job Information Page opens. This page can be used to edit job details such as priority, the type of job, and so forth. See the Oracle WebCenter Content System Administrator's Guide for Content Server for more details.

10 Processing Retention Assignments

Retention assignments are the items and events (disposition actions) that users are responsible for reviewing or processing. A user can quickly access retention assignments by choosing Records then Approvals from the Top menu. They can also be accessed by choosing My Content Server then My Records Assignments from the Main menu.

This chapter discusses processing retention assignments, which include reviewing items subject to review and processing disposition actions. It covers the following topics:

Section 10.1, "Retention Assignment Overview"

Section 10.2, "Managing Disposition Tasks"

Section 10.3, "Processing Dispositions"

10.1 Retention Assignment Overview

The Approvals menu options provide a link to items needing to be reviewed and all pending events needing to be processed.

A disposition is an action taken on content after a triggering event has occurred. For complete details about setting up dispositions, see the Oracle WebCenter Content Setup Guide for Records.

This chapter describes how dispositions are processed and what approvals may be needed in order for some specific types of disposition actions to proceed.

This section discusses the following topics:

Section 10.1.1, "Items Subject to Review"

Section 10.1.2, "Approval and Completion"

Section 10.1.3, "Frozen Items and Event Processing"

Section 10.1.4, "Searching Retention Steps and Actions"

Section 10.1.5, "Using Batch Processing"

Section 10.1.6, "Specifying an Alternate Reviewer"

10.1.1 Items Subject to Review

Content can be subjected to periodic review whether it is managed in a disposition or not. From a DoD perspective, contents subject to review are vital. According to NARA, the National Archives and Records Administration in the United States, vital records are essential government agency content needed to meet operational responsibilities under emergency or disaster conditions, or are required to protect legal and financial rights of the Government. and update for any purpose so designated.

Organizations that are not government agencies may have content that is vital to their type of business and therefore subject to review.

Items that are subject to review typically comprise about five percent of content deemed critical to a business. Some examples of content of this type include:

Software source code

Patents and copyrights

Legal documents such as trusts, estates, and wills

Regulatory compliance data

Cycling vital content that is subject to review refers to the periodic replacement of obsolete copies of content with copies of current content. Initial reviews are based on the content release date content and the filing date for record folders. The next review date is based on the reviewer's last review date.

To find items awaiting review choose Records then Approvals from the Top menu. Choose Pending Reviews.

If you are a member of the RmaReviewers alias, choose List All on the Table menu on the page. This shows all items awaiting review and the person assigned to do those reviews. Choose List Mine to show only those items awaiting the logged-in user's approval.

10.1.2 Approval and Completion

Some pending triggering events require only approval by the person specified as the Notification Reviewer when the disposition was first set for the category. After the action has been approved, it is marked as such and is processed when dispositions are run, usually overnight. The disposition actions are logged in the audit log and are subsequently removed from the approval list.

Some events require two steps, depending on the event type and the item to be processed. First, they must be approved and after an action has been carried out manually, they must be marked as completed after the required event action has been executed (for example, physical transfer to a different location). For details, see Section 10.3.1, "Multi-Step Disposition Processing."

To view items awaiting disposition choose Records then Approvals from the Top menu. Choose Pending Dispositions. To also access pending dispositions choose My Content Server then My Records Assignments from the Main menu.

10.1.3 Frozen Items and Event Processing

After an event has been processed (approved and marked as completed if required) it should automatically be removed from the pending event pages (approval list and/or completion list). If an event remains on these pages there is probably a frozen item or folder preventing its removal.

For example, if a total of ten items are affected by a Destroy event and one of them is frozen, then the event for that one item will remain in the approval list, and the event will move to the completion list for the other nine items. These nine items can then be destroyed and the event marked as completed, but the frozen item cannot be processed until it is unfrozen.

For information about how to find those dispositions that did not succeed, see Section 10.2.2, "Viewing Failed Dispositions."

10.1.4 Searching Retention Steps and Actions

Use the Retention Step Search Page to screen for disposition steps. For example, a user can screen to discover what actions have been approved, who approved them, and what actions are done. From the screening results, a report can be created that can then be used as a destruction certificate, if needed. To access this page, choose Records then Audit then Retention Steps from the Top menu.

Information can also be displayed about any disposition actions that did not process correctly. The Failed Dispositions Page shows those dispositions actions that did occur as specified. To access this page, choose Records then Audit then Fail Dispositions from the Top menu. For details, see Section 10.2.2, "Viewing Failed Dispositions."

10.1.5 Using Batch Processing

Pending events and review cycles are processed by the system every night on a 24-hour cycle. Notifications are sent daily at midnight.

Use the Batch Services options on the Records menu to process certain actions immediately rather than wait for the scheduled processing time. Options on the Batch menu include:

Run All: Processes all events pertaining to reviews or dispositions

Process Dispositions: Processes all disposition-related pending events

Process Reviews: Processes pending reviews regardless of whether items are in a disposition or not.

Send Notifications: Sends any pending notifications relating to dispositions

Run Other: Processes other batch services unrelated to disposition processing such as notification of monitoring alerts, scheduled key rotation, and so on.

10.1.6 Specifying an Alternate Reviewer

It may be useful to select another user than yourself to perform review actions and process disposition events, for example when you are out of the office for some time. Alternate reviewers can be specified in your user profile. They will then receive e-mail notifications of any pending actions assigned to you and can act on them.

Permissions:

The Admin.PerformActions or Admin.PerformPendingReviews right is required to perform this action. The Admin.PerformActions right is assigned by default to the Records Administrator role. The Admin.PerformPendingReviews right is assigned by default to all roles. A user can also ask your Records Administrator to specify an alternate reviewer.

Log in and open your user profile. Select an alternate reviewer from the list. The list includes all users who have been specified as default notification recipients as discussed in the Oracle WebCenter Content Setup Guide for Records. The selected person will now receive e-mail notifications of pending actions and events assigned to you.

By default, only the alternate reviewer will receive notifications and not the users. The system can be configured so both the users and the alternate reviewer are notified. To accomplish this, make sure the config.fg configuration file contains the following line:

RmaNotifyReviewerAndAlternateReviewer=true

Restart Content Server for this setting to take effect.

10.2 Managing Disposition Tasks

The following tasks are performed when processing disposition actions:

Section 10.2.1, "Screening for Retention Steps"

Section 10.2.2, "Viewing Failed Dispositions"

Section 10.2.3, "Viewing Pending Reviews and Dispositions"

Section 10.2.4, "Marking Content Items as Reviewed"

Section 10.2.5, "Editing Review Information"

Section 10.2.6, "About Disposition Processing"

10.2.1 Screening for Retention Steps

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

To screen for disposition actions and events, complete the following steps:

Choose Records then Audit then Retention Steps from the Top menu.

The Retention Step Search Page opens.

Select the criteria for the search from the provided lists. The options on the lists will vary depending on customizations in place at the site. This list provides some examples of the type of criteria available:

Sources: Choose the repository source for the search. Click Select to display a list of sources that can be used.

Disposition Criteria: Includes criteria specific to dispositions such as a derived triggering event or location type.

Category Criteria: Includes criteria specific to retention categories such as restrictions (edits, revisions, deletions) and review information (review periods and reviewers).

Records Folder Criteria: Includes criteria specific to folders such as cutoff date, profile trigger, and freeze name for freezes applied to the folder.

Content Criteria: Includes criteria used for content such as author and content type.

Retention Steps Criteria: Includes options for retention actions such as freezing dispositions and action state.

Select sorting preferences in the Results Options area.

Use the defaults or select another option from the Sort By list.

Sort by default descending order or select ascending order.

To view the results of the screening immediately, click Search. Any results matching the screening criteria display in a result page.

To schedule the retention report to run later, select the criteria for the screening and click Schedule.

The Schedule Retention Step Audit Report Page opens.

Provide a name for the screening report.

Provide the start date of the screening report. This is the date the scheduled screening report will be generated. If the screening report is recurring, the first screening report will be generated for the first time on this date, and all subsequent reports at the end of each recurring period after this date.

To create a screening report periodically rather than just once, select Is Recurring. Specify the interval at which the recurring screening report will be created (for example, every 2 weeks).

Click OK when done.

10.2.2 Viewing Failed Dispositions

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

Follow this procedure to find disposition actions that have not succeeded and replay those actions as needed.

Note that if content is managed on an adapter system, no warning is given if the disposition will fail. If the disposition does fail, the action appears on the Failed Dispositions Page. Check that page to verify the status of an adapter disposition.

Choose Records then Audit then Failed Dispositions from the Top menu.

The Failed Dispositions Page opens.

Use this page to view information about failed disposition actions. The following actions can also be performed:

To restart the disposition, select the checkbox for the item and choose Retry from the Table menu.

To create a report of failed dispositions, select the items to include in the report then choose Create Reports from the Table menu.

To mark the disposition as complete regardless of whether the action succeeded or not, select the checkbox for the item and choose Skip from the Table menu. Use this option with caution because it may have unforeseen consequences when a disposition is skipped.

10.2.3 Viewing Pending Reviews and Dispositions

Permissions:

The Folder.Read right and Record.Read right are required to perform this action. All predefined management roles have this right. The Admin.PerformActions right is required to view your own or pending events of others. This right is assigned by default to the Records Administrator role.

Follow this procedure to view pending actions to be taken:

Choose Records then Approval from the Top menu. Choose the type of pending approval to view: Reviews or Dispositions.

The Pending Dispositions Page or Pending Reviews Page opens.

These pages list actions awaiting approval. It lists actions assigned to the logged-in user as well as actions assigned to other users if the logged-in user has permission to see those actions.

10.2.4 Marking Content Items as Reviewed

Follow this procedure to perform reviews. Use this procedure to review items that have been marked as Subject to Review, or items in a category that has a disposition that is Subject to Review.

Permissions:

The Admin.PerformPendingReviews right is required to perform this action. This right is assigned by default to the Records Officer and Records Administrator role. When performing reviews of items assigned to others, you must also be designated as the main notification recipient.

Follow the link in the e-mail sent by the system to notify the reviewer or choose Records then Approvals then Pending Reviews.

The Pending Reviews Page opens.

Select the checkbox of the item to be reviewed then choose Set Dates and Mark Reviewed from the Table menu. If this is a folder to review, the option Mark Reviewed Recursive can be used to mark all items in the folder as reviewed.

In addition, you can choose Set Dates then Mark reviewed from the Actions menu for individual items.

To perform a different action involving dates (mark the item as expired, cancelled, or obsolete, for example), choose Set Dates from the item's Actions menu and choose the appropriate menu option.

Enter a comment for the action (review, expiration, and so on) or leave that field blank if a comment is not needed.

The current date is inserted to indicate the date when the action happened. This date can be changed by typing a new date or selecting one from the calendar icon.

After inserting the information, click OK. The item is then removed from the list of pending reviews.

10.2.5 Editing Review Information

Permissions:

The Category.EditReview right or Folder.EditReview right is required to perform these actions. This right is assigned by default to the Records Administrator role.

Follow this procedure to edit retention category or record folder review information:

Find the Retention category or folder to use.

Choose Edit then Edit Review from the page Actions menu (if editing a category review) or the item's Actions menu (if editing a folder review).

The Edit Review Information for Retention Category/Folder Page opens.

To change a review category to non-review category, deselect Subject to Review. The remaining fields become gray and unavailable. To change a non-review category to a review category, select Subject to Review.

Tech Tip:

Remember the review setting is inherited. If items or record folders should stay as subject to review, make sure to set the review information for the child record folders that no longer inherit review status from their retention category. Any content filed directly into retention categories are directly affected by review status changes.

To select, remove, or change a reviewer, select the reviewer from the Reviewer list. Select the topmost blank to remove the reviewer and allow the system default to designate the reviewer.

To edit or enter the review period, enter an integer and select a review period in the Review Period box and list.

Click Submit Update. An update message is displayed, and the Retention Category Information Page displays the review information that was entered.

When editing folder review information, keep the following points in mind:

The Folder.EditReview right is required to perform the action. This right is assigned by default to the Records Administrator role.

Follow the same procedure to change folder review information as that used to change an item's review information. Remember the review setting is inherited, and if any child folders should stay as subject to review, make sure to set the review information for record folders that no longer inherit it from a parent folder or category.

The selected reviewer must have the Records Administrator or Records Officer role because users assigned the Records User role cannot mark a record folder as reviewed.

10.2.6 About Disposition Processing

This section contains procedures for processing pending events.

Section 10.2.6.1, "Accessing the Pending Approval Interface"

Section 10.2.6.2, "Event Processing"

Section 10.2.6.3, "Pending Approvals"

Section 10.2.6.4, "Pending Review"

10.2.6.1 Accessing the Pending Approval Interface

In the following event descriptions, all events are accessed by choosing Records then Approvals and choosing Pending Review or Pending Disposition or by clicking the link in the e-mail notifying a user of dispositions or reviews to be performed.

Events for yourself are listed. To view assignments to other users, you must be added to the RmaReviewers alias. Then choose List All on the Table menu on the Pending Dispositions Page or Pending Reviews Page.

Note that Access Control List settings can limit what dispositions are accessible. If a user is not in the ACL for the category, then the pending disposition is not seen.

10.2.6.2 Event Processing

The following list describes common functionality regardless of the type of action being processed:

The Admin.PerformActions right is required to perform these actions. This right is assigned by default to the Records Administrator role.

For most events, when the disposition event is processed, an audit log file is created automatically. A screening can be done for that audit log and it can be checked in as a content item if needed. An audit log is not created for a Move event or a No Action event.

Most actions are run automatically with the batch services that are run nightly or when a Batch Services option is selected by choosing Records then Batch Services.

10.2.6.3 Pending Approvals

The following persons may receive notifications of events triggered by disposition rules, depending on the system configuration:

the author or filer of a retention category

members of the RmaReviewers alias group

the additional notification reviewer, if specified when the disposition rule was set up for the category

The pending events appear in both the other notification recipient's approval list and the filer's own approval list. If the main recipient processes the event, the event is removed from the author's approval list and vice versa. Some events only require approval. After approval of these events, their associated disposition actions are executed when the dispositions are run, usually nightly, unless otherwise processed by selecting an option from the Batch Services menu. The processed events are subsequently removed from the approval list.

Some events require multiple steps, depending on the event type and the item to be processed. First, they must be approved and after approval they must be marked as completed. Items marked as completed often must be physically moved to complete the action (for example, transferring an item to different location).

When an event must be marked as complete, it still appears on the Pending Dispositions Page and the name of the event is changed to indicate it must be marked complete (for example, Mark Transfer Complete). To mark the item as complete, select the box for the item then choose Approve from the Table menu.

10.2.6.4 Pending Review

To mark multiple items as reviewed, select the checkbox for the item and choose Mark Reviewed from the Set Dates menu on the Pending Reviews Page. A prompt appears to enter any review comments.

The current date is inserted as the review date. This date can be changed by typing a new date or selecting one from the calendar icon.

After inserting the review information, click OK. The item is then removed from the list of pending reviews.

10.3 Processing Dispositions

Disposition actions can be divided into two types: those requiring one step for completion and those requiring multiple steps. This section describes each type of disposition processing.

Dispositions are grouped and held in batches. They are automatically scheduled and executed at the same time as other batch processes, normally at midnight or later.

To execute dispositions immediately, choose Records then Batch Services from the Top menu. Select the type of action to process (dispositions, review, notifications, and so on). For information about the options on the Batch Services menu, see Section 10.1.5, "Using Batch Processing."

If a processed event does not become available to mark as complete, then affected items (for example, content in a folder) are frozen and cannot be processed. Use the List Disposition Folders and Content option from the item's Actions menu to view the contents of the folder. The frozen items will not be processed until they are unfrozen. It is also possible the disposition failed. For information about checking on a disposition status, see Section 10.2.2, "Viewing Failed Dispositions."

This section describes the following types of dispositions:

Section 10.3.1, "Multi-Step Disposition Processing"

Section 10.3.2, "Single Step Disposition Processing"

10.3.1 Multi-Step Disposition Processing

The follow disposition events require multiple steps for processing. For complete details about disposition events, see the Oracle WebCenter Content Setup Guide for Records:

Accession: An accession is one of the last actions in a disposition sequence. Files for accession are stored in a directory (typically in the weblayout_dir/groups/secure/rm/RmaAccessionApp directory) and a user can then choose how to hand off the files to the final archive institution.

The option also is available to destroy the items while retaining their metadata or to destroy items without retaining metadata. This option is selected when the category's disposition is created. An accession event consists of two steps: it must be approved first and then, after the action has been carried out, it must be marked as completed.

Archive: The Archive action creates a zip file of the content and folder. Within each zip archive, there is a copy of each item and its metadata. The meta files contain the item metadata in the format specified by the Archive Meta Data Format setting on the Configure Retention Settings Page (hda, xml, or csv). An archive event consists of two steps: it must be approved first and then, after the action has been carried out, it must be marked as completed. The .zip file is stored in a location on the computer. To see the location, choose Archive Location from the Actions menu of an Archive action on the Pending Dispositions Page.

Move: A move action does not leave a copy of internal (electronic) items on the system. This action should not be confused with moving retention items within the retention management system, which is accomplished with the Move command within the retention schedule (Browse Content menu). A move event consists of two steps: it must be approved first and then, after the action has been carried out, it must be marked as completed.

Transfer: A transfer action leaves a copy of internal (electronic) items on the retention management system. A transfer event can be considered complete when an organization sends the items to another organization. A transfer event consists of two steps: it must be approved first and then, after the action has been carried out, it must be marked as completed. A terminal transfer action is when the transfer disposition action is the last action for a disposition schedule. If the Transfer action is the last step (rule) in a disposition action, the items must be destroyed before the step can be marked as completed.

One aspect of these events is the ability to destroy items in conjunction with the processing. For example, you can choose to transfer items and destroy the metadata after the transfer, or you can retain the metadata. Another example is to move content and either destroy or keep the metadata. These actions are chosen when the disposition for the category is set up initially. See the Oracle WebCenter Content Setup Guide for Records for details.

The number of disk scrubbing passes that accomplish the destruction can be configured by setting the following parameter in the config.cfg environment file:

RecordsManagementNumberOverwriteOnDelete

Restart Content Server after setting this variable. By default, the number of scrubbing passes on the hard disk is set to 2.

The destroy process can consist of one or two steps. For electronic (internal) items, multiple actions are carried out automatically by the system. If metadata was to be destroyed with the items, that is done as well.

For physical (external) items, which are managed using Physical Content Management, two steps are required: the event must be approved first and then, after the external items have been destroyed manually, it must be marked as completed.

10.3.1.1 Approval Step

The name listed in the ID column is the name of the category involved in the disposition followed by a step number. Note that numbering begins with step 0.

Choose Records then Approvals from the Top menu. Choose Pending Dispositions or click the link in the notification e-mail.

The Pending Dispositions Page opens.

To view information about the disposition action, click the action name. The Disposition Information Page opens. To view what items are included in this action, choose List Disposition Folders and Content from the Actions menu of a disposition action. An individual disposition can also be approved from this menu.

Select the checkboxes of the actions to approve and choose Approve from the Table menu.

The Disposition Parameter Dialog opens.

Enter a reason for the action and click OK. To abort the entire action, click Cancel.

The action is approved. After processing (either during the scheduled processing time or after a batch service is run) the event appears on the Pending Dispositions Page and is available to mark as completed if needed.

10.3.1.2 Completion

After an item has been marked as approved and is processed, it remains on the Pending Dispositions Page but the name of the action is changed to Mark action Complete (for example, Mark Accession Complete).

Internal items are completed as needed automatically. This action is transparent to users but the system approval steps are listed in the disposition.

Follow these instructions to mark an action as completed:

Choose Records then Approvals from the Top menu. Choose Pending Dispositions or click the link in the notification e-mail.

The Pending Dispositions Page opens. Note that all disposition actions awaiting approval are displayed, not just those actions awaiting completion.

To view information about the disposition action, click the action name. The Disposition Information Page opens. To view what items are included in this action, choose List Disposition Folders and Content from the Actions menu of a disposition action. An individual disposition can also be approved from this menu.

Select the checkboxes of the actions to approve (mark complete) and choose Approve from the Table menu.

The Disposition Parameter Dialog opens. Enter a reason for the disposition action and click OK. Click Cancel to abort the entire action.

If the action requires a decision involving destruction (that is, to destroy or keep metadata associated with the action), choose a destruction method from the menu in the Disposition Parameter Dialog. Disposition actions that involve such a choice are Accession, Archive, Move, and Transfer.

The action is removed from the Pending Dispositions Page. If further approvals are needed (that is, if another action must be taken to complete the disposition) that action will appear on the Pending Dispositions Page after processing (either during the scheduled processing time or after a batch service is run.

10.3.2 Single Step Disposition Processing

The following dispositions require single step processing:

Classified Records Actions

Review Classification: This action indicates it is time to review the security classification status of an item.

Upgrade Classification: This action indicates it is time to increase the security classification of an item. Classifications can be increased as high as the classification of the user applying the classification.

Declassify: This action indicates it is time to declassify content.

Downgrade Classification: This action indicates it is time to lower the security classification of an item.

Dispose Actions

Delete Previous Revision: This action indicates it is time to delete the revision before the content item revision that triggered the disposition action. The revision that activated the trigger may be the latest revision of a content item, but does not need to be.

If a content item has 5 revisions and this disposition action is activated for revision 5 (the latest revision), then only revision 4 is marked for deletion.

If a content item has 5 revisions and this disposition action is activated for revision 3, then only revision 2 is marked for deletion.

Delete Revision: This action indicates it is time to delete the content item revision that triggered the disposition action. This revision may be the latest revision of a content item, but does not need to be.

If a content item has 5 revisions and this disposition action is activated for revision 5 (the latest revision), then only revision 5 is marked for deletion.

If a content item has 5 revisions and this disposition action is activated for revision 3, then only revision 3 is marked for deletion.

Approve Deletion: This action indicates it is time to approve record folders or content for deletion.

Delete All Revisions: This action indicates it is time to delete the content item revision that triggered the disposition action and all earlier revisions. The revision that activated the trigger may be the latest revision of a content item, but does not need to be.

If a content item has 5 revisions and this disposition action is activated for revision 5 (the latest revision), then revisions 1 through 5 are marked for deletion (effectively removing the content item altogether).

If a content item has 5 revisions and this disposition action is activated for revision 3, then revisions 1 through 3 are marked for deletion.

If the DoD Config module is enabled, all revisions can be deleted and the metadata destroyed or kept, or only old revisions destroyed. Metadata cannot be retained unless the DoD Config module is enabled.

Delete Old Revisions: This action indicates it is time to delete all revisions before the content item revision that triggered the disposition action. The revision that activated the trigger may be the latest revision of a content item, but does not need to be.

If a content item has 5 revisions and this disposition action is activated for revision 3, then revisions 1 and 2 are marked for deletion.

If a content item has 5 revisions and this disposition action is activated for revision 5 (the latest revision), then revisions 1 through 4 are marked for deletion.

Delete Working Copy: This action deletes the working copy of a cloned content item. It first deletes the direct working copy of the clone. Then all previous revisions of the working copy are deleted until a revision of the fixed clone itself is found. The deletions stop at that point.

Delete Previous Clones: This action deletes the previous clone of a content item.

Other

Check in New Revision: This action indicates it is time to take the latest revision of the affected content items and check in a copy of this revision as a new revision. This may be useful to process a content item revision based on changed historical information, refresh an expired document, or enter a content item into a criteria workflow for disposition processing.

Activate: This action indicates it is time to activate record folders or content.

Close: This action indicates it is time to close record folders.

Cutoff: This action indicates it is time to cut off content or record folders from further processing. Cutoff refers to changing the status of items to prohibit further processing.

Cutoff and Create Volume: This creates a volume folder, content is placed inside, and the volume is cut off.

Expire: This action indicates it is time to expire record folders or content.

Obsolete: This action indicates it is time to mark content as obsolete.

Mark Related Content: This action marks any content linked to the current content.

No Action: This action indicates there is no action to take currently. This action is usually found mid-disposition. A No Action action acknowledges a disposition milestone has passed, and the next step in the disposition begins processing.

Notify Authors: This action indicates it is time to notify the author of the affected category that disposition actions are due for the category.

Supersede: This action indicates that new content will be checked into the category or folder, superseding the original content item. The superseded item is indicated by a strikethrough on its name.

10.3.2.1 Approving Events

Choose Records then Approvals from the Top menu. Choose Pending Dispositions or click the link in the notification e-mail.

The Pending Dispositions Page opens.

To view information about the disposition action, click the action name. The Disposition Information Page opens. To view what items are included in this action, choose List Disposition Folders and Content from the Actions menu of a disposition action. Individual items affected by the current action can also be approved using this menu.

Select the checkboxes of the actions to approve and choose Approve from the Table menu.

The Disposition Parameter Dialog opens.

Enter a reason for the action and click OK. To abort the entire action, click Cancel.

The action is approved and is removed from the Pending Dispositions Page.

11 Generating Reports

Several types of reports are provided with the software. These reports can be used to track user and group usage of the system and provide summary information for content and items involved with physical content such as invoices, chargebacks, and storage.

In addition, reports can be created as needed about the data that appears on the page as a search result, content information, and so on. If these kinds of reports are available, an option appears on the Page menu, indicating the default reports available for that data.

Customized reports can also be created that are based on existing reports. Creating a customized report requires in-depth knowledge of service calls and queries. That type of report creation is discussed in the Oracle WebCenter Content Setup Guide for Records. This chapter discusses how to set default report options and how to produce the default reports provided with the software.

The following topics are discussed in this chapter:

Section 11.1, "Configuring Report Options"

Section 11.2, "User and Group Reports"

Section 11.3, "Content and Physical Item Reports"

11.1 Configuring Report Options

Reports are initially configured through menu options on the Configure Report Settings Page. During configuration a profile can be specified to be used when creating or updating a report template, and a profile to be used when creating or updating a report. A report format can also be chosen and if the report or template should be included when performing searches.

Note:

If barcode labels will be printed, specify PDF for the report format. Labels will display in HTML output but they can only be printed correctly using the PDF option.

Follow this procedure to configure default options to be used with all reports:

Choose Records then Configure from the Top menu. Choose Reports then Settings.

The Configure Report Settings Page opens.

Choose the report template profile from the option list or use the default profile provided.

Choose the profile to use when creating or updating a report.

Choose the report format to use. Options include HTML, PDF, RTF, or XLS. Note that if barcode labels are to be printed, this must be set to PDF.

Check the box to exclude all report templates during search operations.

Check the box to exclude all checked-in reports during search operations.

When finished, click Submit Update.

11.2 User and Group Reports

After creating users and alias groups, and assigning management roles and rights to users, reports can be generated to view at a glance which users and alias groups have access to the system. The following reports are available:

Section 11.2.1, "User Report"

Section 11.2.2, "User Barcode Reports"

Section 11.2.3, "User Roles Report"

Section 11.2.4, "Group Report"

Section 11.2.5, "Group-User Report"

For details about the audit report, see Chapter 12, "Monitoring, Customizations and Audit Tools."

Reports are generated in the format specified by the setting on the user's profile page. To see the user format that is specified, click the user name in the top right corner of the screen and the User Profile page opens. If the system format is used, that usage is specified on the Configure Report Settings Page.

If the generated report file is in PDF format, Adobe Acrobat version 6.0 or later is required to view it.

To generate reports, choose Records then Reports then the report type from the Top menu.

Permissions:

The Admin.Reports right is required to produce any reports. This right is assigned by default to the Records Administrator role. The Admin role is also required.

11.2.1 User Report

A list can be generated of all users who have access to the system as well as a barcode list for the users. A report can also be created that can be used to produce barcode labels. The users and the bar codes assigned to them are defined in User Admin utility.

This report lists overview information for each user.

Column | Description
User Name | The name of the user as entered in the User Admin utility.
Full Name | The full name of the user as entered in the User Admin utility.
E-mail Address | The e-mail address of the user.
Creation Date | The date and time the user was created in the User Admin utility.
Change Date | The date and time the user information was last modified.
Supplemental | Any supplemental markings assigned to a user.
Security Classification | The classification assigned to the user.
Alternate Reviewer | The alternate reviewer for this user.
Barcode | The barcode designation for the user.

11.2.2 User Barcode Reports

A report can be generated that lists barcode information and another type that can be used to produce barcode labels. The users are defined in the User Admin utility then assigned rights and roles.

View barcode reports using HTML but print reports using PDF in order to ensure proper formatting.

This report lists the barcode information for each user.

The following report produces a barcode list that is suitable for label printing.

11.2.3 User Roles Report

Use this report to view a list of all users and their assigned roles. The output of the report may not show all data for all roles. The output is dependent on the user who is generating the report and the permissions given to that user.

Column | Description
User | The user name of the user as entered in the User Admin utility.
Roles | The roles assigned to the user.

11.2.4 Group Report

Use the All Groups report to view a list of all aliases defined for the system.

Column | Description
Group Name | Lists all alias groups defined in the User Admin utility.
Description | A short description of each alias group.

11.2.5 Group-User Report

Use this report to view a list of all users and groups (aliases) currently defined for access. The users and groups (aliases) are assigned in the User Admin utility.

Column | Description
Group | Lists all alias groups defined in the User Admin utility.
User | Lists every user assigned to an alias group.

11.3 Content and Physical Item Reports

Several default reports and templates are provided with the product. These reports are available in a variety of locations within the software such as search result page, Content Information pages, and so on. The type of reports depend on the configuration of the system and what components have been enabled.

This section describes how to generate content reports using the default templates provided. For details about generating user and group reports, see Section 11.2, "User and Group Reports." For information about creating custom reports, see the Oracle WebCenter Content Setup Guide for Records.

This section discusses the following topics:

Section 11.3.1, "Creating a Report"

Section 11.3.2, "Internal Item Detail Report"

Section 11.3.3, "Search Results Report"

Section 11.3.4, "Records Destruction Certificate Report"

11.3.1 Creating a Report

The creation of new reports is composed of two steps: finding the information for the report then choosing the appropriate report option.

Use searching or screening to find the information.

Use one of the following methods to create a report for an individual item:

Click the Info icon for the item. On the item's Content Information Page, choose Create Reports then the type of report.

On the Search Results Page, select the checkbox for an item. Choose Create Reports then Selected Items then the type of report.

To create a report for multiple items, select the checkboxes of the items then choose Create Reports then Selected Items then the type of report.

To create a report for all items on the page (such as all search results), choose Create Reports then Full Results then the type of report.

This section provides several examples of reports.

11.3.2 Internal Item Detail Report

The following is an example of an Internal Item Detail Report. This report shows details about one item or about a group of items if several items are selected for use for the report.

An external detail report is similar to this report, but it includes the bar code for the item as well as other information that pertains only to external items.

11.3.3 Search Results Report

The following is an example of a Search Results report. This report shows basic information about items.

11.3.4 Records Destruction Certificate Report

The following is an example of a Records Destruction Certificate report. This report shows those items that are scheduled for destruction and which should be removed from the warehouse.

12 Monitoring, Customizations and Audit Tools

Several optional tools are available to help administrators customize and track system performance and usage:

Performance monitoring can be used to check the length of time needed to process service requests, to monitor batch requests and to check for items that have failed to process.

Custom scripts can be written and applied to content for access control and to add notifications. This complies with DoD Chapter 4 certification requirements.

Audit trails capture and record all user activity configured to be included. An audit trail is critical for tracking user actions within a record management system.

This chapter discusses using monitoring, custom scripts, and audit trails. It covers the following topics:

Section 12.1, "Using Performance Monitoring"

Section 12.2, "Using Custom Scripts"

Section 12.3, "Using the Audit Trail"

12.1 Using Performance Monitoring

Performance monitoring can be enabled to check the status of batch processing, service calls, and other system information.

Several default numbers have been set as a starting point for monitoring. Actual performance variations will depend on the hardware used at the site and other variables such as total amount of content and software in use.

The frequency with which you need to update statistics depends on how quickly the data is changing. Typically, statistics should be updated when the number of new items since the last update is greater than ten percent of the number of items when the statistics were last updated.

If a large amount of disposition processing is being done (for example, at the end of the calendar year for organizations that synchronize dispositions on the calendar), you should update statistics at the end of the week rather than wait for a particular percentage of data updates.

Performance monitoring statistics are written to a database table and can be accessed later.

12.1.1 Enabling Performance Monitoring

Follow this procedure to use performance monitoring:

Choose Records then Audit from the Top menu. Choose Configure then Performance Monitoring.

The Configure Performance Monitoring Page opens.

Select the items to monitor and the time intervals for reports and alerts.

Click Submit Update when done.

12.1.2 Checking Performance Results

After enabling performance monitoring, current performance information can be checked using this procedure:

Choose Records then Audit then Performance Monitoring from the Top menu.

The Performance Processing Results Page opens.

Choose the type of information to view by clicking the tab at the top of the body section of the page:

Performance Processing: This page contains a summary of requests processed, total items processed, total number of queries run, total time to run queries, total time to validate data, total service request parse time and total service request time per each source. Averages for these are also included.

Report by Batch: This page contains a summary of batches/items pending, processed, and failed with a total for each source. If an item has failed, a batch file is created that can be re-run. Click on any value in a column to open a page showing details about that item and to access the option to re-run the batch.

Report by Item: This page contains the details per batch for a particular source, status or batch type as well as totals. The detail page for the item contains the batch type, start time, completed time, elapsed time, and number of items processed for each batch.

12.1.3 Viewing Performance Alerts and Details

If any performance activities exceed the limits set on the Configure Performance Monitoring Page, a message is displayed automatically when you log in to the system.

Click any link on the message to see details about the specific alert. For example, a detail screen opens when the first alert message is clicked. Click any link to show details about the specific items that caused the alert.

12.2 Using Custom Scripts

Custom scripts can be created using Idoc Script, a proprietary scripting language. This functionality is enabled by default when the DoD Configuration component is enabled. See the Oracle WebCenter Content Setup Guide for Records for details about different options.

Custom scripting can be disabled by deselecting Enable Custom Script in the DoD Config section of the Configure Retention Settings Page. To access that page choose Records then Configure then Settings from the Top menu.

When enabled, new content fields are available that allow you to define which scripts will apply to a folder or category.

Caution:

You must have a thorough understanding of Idoc Script to use this feature. The software does not validate the script. You are responsible for creating usable scripts. See the Oracle WebCenter Content Idoc Script Reference Guide for details about Idoc Script and its use.

Two types of scripts can be created using the Custom Script functionality:

Security scripts, which allow users with the Records Administrator role to define and manage access control to content.

Custom Notification scripts, which notify users of events. One custom script is provided, which notifies a list of reviewers when items are due for destruction after being superseded. Notification is sent in one consolidated e-mail when batches are run. Additional scripts can be created.

Scripts can be applied at a category or folder level but content in the category or folder does not automatically inherit the script. Consider the following scenario:

A custom script is created to prevent user A from viewing content.

A folder is created and the custom script is applied to it.

An item is checked in by user B to the folder.

User A browses through the folder and sees the title of the item checked in by user B. However, if user A tries to view the actual item, an error is returned.

To prevent user A from even seeing the title of the item, the security script must be set so items included in the object (category or folder) explicitly inherit the attributes of the script. For example, to set inheritance in a category, the following variable would be set in the config.cfg file:

RecordsMetaInheritFromCategory=dSecurityScripts:xSecurityScripts

To set inheritance for a folder, use the RecordsMetaInheritFromFolder variable.

Note:

Custom scripts comply with the DoD 5015.2 specification, chapter 4.19 and chapter 4.20.

12.2.1 Creating or Editing Scripts

Note:

Any custom Idoc script that is entered is NOT verified for accuracy. You should have knowledge about Idoc script and its uses before creating scripts.

Follow this procedure to set up a custom script. Use the same procedure for both types of scripts.

Choose Records then Configure from the Top menu. Choose Security then Custom Scripts.

The Configure Custom Script Page opens.

Select the type of script to use (Notification or Security) by clicking the tab for the script type. To edit an existing script, choose Edit from the script's Actions menu. To add a script, choose Add or Edit on the Custom Script Information Page.

The Create or Edit Custom Script Page opens.

Add or edit the name for the script.

Add or edit the description for the script (optional).

Add or edit the Idoc code for the script. Note that the code is not verified for accuracy.

When finished adding a new script, click Create. When editing a script, click Submit Update. To reset the page without saving, click Reset.

12.2.2 Deleting a Custom Script

Follow this procedure to delete a custom script. Use the same procedure for both types of scripts.

Choose Records then Configure from the Top menu. Choose Security then Custom Scripts.

The Configure Custom Script Page opens. Select the type of script for deletion by clicking the tab for either a Notification or a Security script.

To delete the script, select the box next to the script name and choose Delete or Delete Script from the script's Actions menu. You can also choose Delete on the Custom Script Information Page.

12.2.3 Viewing Script Information

Follow this procedure to view a script's information:

Choose Records then Configure from the Top menu. Choose Security then Custom Scripts.

The Configure Custom Script Page opens. Select the script for viewing by clicking the tab for either a Notification or a Security script.

To view the script information, click the script name or choose Script Information from the script's Actions menu.

The Custom Script Information Page opens.

12.3 Using the Audit Trail

The audit trail is generated in the format specified by the Report Format setting on the Configure Report Settings Page.

Permissions:

The Admin.Audit right is required to work with audit trails. This right is assigned by default to the Records Administrator role. Administrative privileges are required to check in the audit trail.

At certain points, the current audit trail can be cut off and archived and checked into the repository. This action can also be scheduled to occur on a regular basis. The audit trail must be cycled for growth reasons the same as other items. Be sure to check in the audit trail log on a regular basis to keep the file size smaller and the report generation time faster. Each current audit trail is generated from the time the system was installed or archived until the request to generate an audit trail.

An audit trail can be generated at any time. The columns within the audit trail correspond directly with the fields you can use to search within the Search Audit Trail Page.

If the generated file is in PDF format, Adobe Acrobat version 6.0 or later is required to view it.

Several tasks are involved in managing Audit Trails:

Section 12.3.1, "Configuring the Audit Trail"

Section 12.3.2, "Specifying Metadata Fields to Audit"

Section 12.3.3, "Searching within the Audit Trail"

Section 12.3.4, "Setting Default Metadata for Checking In Audit Trails"

Section 12.3.5, "Checking In and Archiving the Audit Trail"

Section 12.3.6, "Searching an Archived Audit Trail"

Section 12.3.7, "Viewing an Archived Audit Trail"

12.3.1 Configuring the Audit Trail

The configuration on the Configure Audit Page determines the administrator and user actions recorded for an audit trail.

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

To configure an audit trail, complete the following steps:

Choose Records then Audit from the Top menu. Choose Configure then Audit Trail.

The Configure Audit Page opens.

Select the boxes for the actions to audit for each entity.

Click Submit Update. A message indicates configuring the audit was successful. The next time the audit trail is generated, the trail reflects the chosen selections.

Click OK. The Configure Audit Page opens again with the updated settings.

Caution:

If actions are deselected for objects, the actions are not captured by the audit trail. It is recommended you leave all settings selected and use the Search Audit Trail Page to narrow down searches of the audit trail. If transactions are heavy and the audit log grows too large too fast, you might want to consider turning off capturing browsing actions to manage the audit trail size.

12.3.2 Specifying Metadata Fields to Audit

Use this procedure to specify which metadata fields should be included in the audit trail.

Permissions:

The Admin.SelectMeta right is required to perform this action. This right is assigned to the Records Administrator role by default.

Choose Records then Audit from the Top menu. Choose Configure then Audit Fields.

The Audit Fields Page opens.

Select the boxes for the metadata field to include in the audit trail.

Click Submit Update when done.

Any changes take effect immediately without restarting the system.

12.3.3 Searching within the Audit Trail

Use this procedure to further refine a search within the current audit trail. For example, you can search for all delete actions, or all delete actions by a particular user, or all actions by a particular user, and so on. To search within archived audit trails, see Section 12.3.6, "Searching an Archived Audit Trail."

When sorting the audit trail using Oracle DB, the output depends on the type of sort being performed. When sorting with Fulltext Search, sorting is case-sensitive, meaning that upper case items (capitalized items) will appear first in a list. When sorting with Oracle Text Search, a case-insensitive search is performed.

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

Choose Records then Audit from the Top menu. Choose Search Audit Trail.

The Search Audit Trail Page opens.

Make the selections to narrow the search. As much or as little detail can be included. To adjust the scope (narrow or widen) of the search, use the Boolean operators before each field.

Click Search. The search results are displayed in the format specified by the Report Format setting on the Configure Report Settings Page.

12.3.4 Setting Default Metadata for Checking In Audit Trails

Setting the default metadata is useful for setting similar checkin attributes. You must set the default metadata before checking in an audit trail for the first time. This is a required step during the setup of the software.

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

To set the default metadata for checking in and archiving a portion of the audit trail, complete the following steps:

Choose Records then Audit from the Top menu. Choose Checked-in Audit Entries.

The Checked-in Audit Entries Page opens.

Click the Default Metadata for Checked-In Audit Entries link.

The Default Metadata for Checked-In Audit Entries Page opens.

Make selections reflecting the metadata most commonly used when checking in an archived audit trail. When finished, click Submit Update. A message is displayed saying the default metadata has been updated successfully.

Click OK.

12.3.5 Checking In and Archiving the Audit Trail

A user must have performed at least one action while logged into the system to generate an audit trail entry. If an empty audit trail is submitted for check-in, a message is displayed indicating there are no entries in the audit trail. Before checking in an audit trail for the first time, set the default metadata for the checkin. For details, see Section 12.3.4, "Setting Default Metadata for Checking In Audit Trails."

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

Choose Records then Audit from the Top menu. Choose Checked-in Audit Entries.

The Checked-in Audit Entries Page opens.

In the Check In Audit Entries area, specify the date and time to cut off the audit trail in the Date box, and click Archive.

The checkin confirmation page opens. The content ID of the checked-in audit trail is AUDITLOGARCHIVE. Every time it is checked in, a new revision is generated.

Click Content Info to view the information about the archived audit log. The Content Information Page opens. To view the audit log just checked in, click the Web Location or the Native File in the Links area of the Content Information page.

12.3.6 Searching an Archived Audit Trail

Use this procedure to search for all checked in and archived audit trails.

Prerequisites

Section 12.3.5, "Checking In and Archiving the Audit Trail"

Permissions:

The Admin.Audit right is required to perform this action. This right is assigned by default to the Records Administrator role.

Choose Records then Audit from the Top menu. Choose Checked-in Audit Entries.

The Checked-in Audit Entries Page opens.

Click Search Audit Entries. The results of the search are displayed in the search results page. From the search results page, click options in the Query Actions list to search within the results and save the search.

12.3.7 Viewing an Archived Audit Trail

Use this procedure to view an archived audit trail.

Prerequisites

Section 12.3.6, "Searching an Archived Audit Trail"

To view an archived audit log from the search results page, do one of the following:

Click the ID (quickest method)

Click the Info icon then click the PDF links on the Content Information page.

12.3.8 Creating an Audit Trail Report

An audit trail report is automatically generated in the format specified by the Report Format setting on the Configure Report Settings Page. If the generated file is in PDF format, Adobe Acrobat version 6.0 or later is required to view it.

The following is a sample audit trail report.

13 Archiving and Transferring Information

If an environment is set up on one computer (including a retention schedule, security scheme, and so on), you may want to copy this configuration information to another computer, for example, from a development system to a production system or a mirrored site. This can be done using built-in archive import and export features.

You can also import and export records, folders, and metadata in XML format by creating a XML Standard Definition (XSD). XSD is a an XML schema language used to define the structure of an XML document. The XSD file is created to make the file usable in the Records system. This allows the content from the system to be imported into a third-party system using a different archive file format or to export data from another system and import it into the system.

This functionality is compliant with the DoD 5015.2 specification that requires the ability to create different XSD schemas.

This chapter discusses exporting archives and importing them into other instances to duplicate the retention schedule and a variety of other configuration settings. It also discusses importing and exporting XSD schema to transfer content.

Important:

When using the import/export process, make sure the instance to which you are importing has the same metadata fields, security groups, and accounts as the instance where the export is originating from. Errors can result if there are mismatches.

This chapter covers the following topics:

Section 13.1, "The Archive Process"

Section 13.2, "Managing Imports and Exports"

Section 13.3, "XSD Data Transfer"

13.1 The Archive Process

The archive process is used to back up or restore a retention schedule and other configuration settings. It is not used to archive copies of content. For details about archiving content, see the Oracle WebCenter Content System Administrator's Guide for Content Server.

Note that if you import an archive from a 10g version of the software to the 11g version that includes a Related Content table, the import must be done in two steps. First import the content items in an archive. Then import the Related Content table.

The export feature copies a variety of configuration settings to a separate .hda file that can be imported into another instance or stored in a safe location for backup purposes. The .hda file is a plain text, serialized data file that can be opened in any text editor.

Retention Schedule objects should be imported before importing other content. Content Server content should be imported before importing the content-related objects.

Permissions:

For details, see Section 13.1.3, "Archive Import/Export Rights and Permissions."

The archive export and import features enable exporting and importing of the following items:

Supplemental markings

Security classifications, also known as Classified Markings

Custom categories metadata and custom folder metadata

Custom security fields, also known as Custom Supplemental Markings

Periods

Triggers

Retention schedules

Dispositions history: a log of all actions that have been performed

Custom disposition actions

Freezes

Recurring scheduled tasks

Classification guides and classification topics. These are only available if the ClassifiedEnhancements component is enabled.

PCM location types

PCM storage space definitions

Custom PCM metadata

Reservations

Note the following considerations when using imports and exports:

When using PCM, the export feature copies the space management definitions (the setup and hierarchy of warehouses, rooms, and so on) but none of the metadata of the items stored at those locations is archived.

When importing an archive, existing items can be overwritten or can be left unchanged.

Set the default archive metadata format by choosing Records then Configure then Settings from the Top menu. The Configure Retention Settings Page opens. Expand the General section and select the metadata format from the list.

When custom category metadata fields or custom folder metadata fields are imported, the order of the fields is not updated. Restart Content Server after importing custom fields.

The disposition history is not updated. Only new dispositions are imported.

The export feature copies the retention schedule definition (that is, the defined hierarchy) and disposition instructions, not the items within the retention schedule.

If an add-on is enabled, there may be additional items available for export.

Important:

If your organization uses additional security (ACLs) on your retention schedule, the import and export only includes items that can be accessed by the user performing the import or export. For example, if the person does not have ACL access to a particular category, that category is not imported or exported. A message is displayed during the import or export process if any objects are not processed due to ACL access. Make sure you have ACL access to all items to export and import.

13.1.1 Exporting Auxiliary Metadata Sets

Permissions:

You must have administrative privileges to add tables to the list of schema tables used.

When exporting an auxiliary metadata set, add the AuxiliaryMetadataSets and AuxiliaryMetadataSetDefs table to the list of schema tables used. Follow this procedure to add those tables:

Choose Administration then Admin Applets from the Main menu.

Click Configuration Manager. The Configuration Manager applet opens.

Click the Tables tab. A Table List opens. Click Add Table.

Highlight AuxiliaryMetadataSets and click OK. The Table list opens again.

Highlight AuxiliaryMetadataSetDefs and click OK. The Table list opens again.

Close the Configuration Manager.

After adding the MetadataSet tables to the list of tables, they become available in the list of tables that can be added from the Archiver.

13.1.2 The Export/Import Process

The process of importing and exporting content consists of three distinct parts.

First import or export a retention schedule and any of the objects in that schedule. This corresponds to the Include Retention Schedules Plan portion of the Export and Import pages.

Then import or export the content using the Oracle WebCenter Content Archiver. See the Oracle WebCenter Content Application Administrator's Guide for Content Server for details about using the Archiver.

After content has been imported or exported using the Archiver, import or export the Disposition History of related objects. This corresponds to the Include Dispositions History portion of the Export and Import pages.

13.1.3 Archive Import/Export Rights and Permissions

The following export rights are needed for specific objects. These rights are included by default with the Records Administrator role:

Admin.RetentionSchedulesArchive right: to export a Retention Schedule.

Admin.Triggers right: to export triggers.

Admin.PerformActions right: to export Disposition Histories.

Admin.RecordManager right: to export objects other than those mentioned previously.

The following import rights are needed for specific objects:

Category.Edit, Folder.Edit, and Record.Edit rights: to import a Retention Schedule (because these objects are part of a Retention Schedule).

Admin.Triggers right: to import triggers.

Admin.PerformActions right: to import Disposition Histories.

Admin.CustomDispositionActions right: to import Disposition Actions.

Admin.RecordManager right: to import objects other than those mentioned previously.

If ACL security is enabled, make sure you have access to all retention schedule components and objects to import.

13.2 Managing Imports and Exports

The following tasks are performed when importing or exporting archives:

Section 13.2.1, "Exporting an Archive"

Section 13.2.2, "Importing an Archive"

Section 13.2.3, "Importing a Batch-Created Storage Hierarchy"

13.2.1 Exporting an Archive

Use this procedure to export an archive that can be imported into another instance (located on the same or a separate system) or for backup purposes. Choose which items should be exported.

Permissions:

For details, see Section 13.1.3, "Archive Import/Export Rights and Permissions."

Choose Records then Import/Export then Archives from the Top menu.

The Import/Export Archive Page opens.

Select all items to be included in the export.

Click Export. A download dialog is displayed.

To save the archive, click Save. Navigate to the location to save the file, and enter a filename.

Click Save.

The file is saved to the specified location, and the Import/Export Archive Page opens.

13.2.2 Importing an Archive

Important:

When using the import/export process, make sure the instance to which you are importing has the same metadata fields, security groups, and accounts as the instance where the export is originating from. Errors can result if there are mismatches.

Use this procedure to import an archive that was exported on another instance (located on the same or a separate system). Choose which items in the archive should be imported. The items to import must have been included in the export of the archive.

Permissions:

For details, see Section 13.1.3, "Archive Import/Export Rights and Permissions."

Choose Records then Import/Export then Archives from the Top menu.

The Import/Export Archive Page opens.

Select all items to be included in the import. Click Attempt Update to specify whether to update existing items or leave them untouched. If you do not have update checked and the imported item(s) already exist, an error may occur. Read the error message to determine the best course of action to pursue.

Click Browse next to Archive File to select the archive file (.hda) to import.

After selecting the file, click Import. The import adds all new items and updates any existing ones, if applicable. The results of the imported archive are tracked in the audit trail for the enabled actions.

If an error occurs, the error message indicates the number of items that failed, not necessarily the number of individual errors for all retention schedule components. If classified markings are imported, they should be reordered after importation.

13.2.3 Importing a Batch-Created Storage Hierarchy

Permissions:

For details, see Section 13.1.3, "Archive Import/Export Rights and Permissions."

Use this procedure to import a storage hierarchy definition file (StorageImport.hda) that was created using the batch storage creation feature.

Choose Records then Import/Export then Archives from the Top menu.

The Import/Export Archive Page opens.

Make sure the Include Storage checkbox is selected. You do not have to unselect all the other items. They are ignored if none of them are included in the StorageImport.hda file.

Click Browse next to Archive File to select the StorageImport.hda archive file that was created when you batch-created the storage hierarchy.

After selecting the file, click Import. The import adds the storage hierarchy contained in the StorageImport.hda file to the existing storage space at the location specified in the hda file.

13.3 XSD Data Transfer

XSD schemas can be used to manage records, folders, and content to comply with the DoD 5015.2 specification. Exporting and importing data using a format defined as XSD format (XML Schema Definition) conforms with standard transfer schema defaults.

The information must be mapped before proceeding with exporting or importing. After the correct mapping is in place, data can be imported and used. It can then later be transferred as needed to NARA or another system using the XSD schema for that site.

13.3.1 Important Considerations Before Exporting

Two considerations should be evaluated before beginning the import and export process:

Section 13.3.1.1, "Special Handling of <choice> Elements"

Section 13.3.1.2, "Required Fields on Import"

Section 13.3.1.3, "Target Namespace and Qualified Locals"

13.3.1.1 Special Handling of <choice> Elements

The <choice> element type allows only one of the elements contained in the selected group to be present within a containing element. This differs from an option list where one field can have multiple possible values.

A document whose data is being exported can only contain a value in one of the fields contained in the <xs:choice> group. This restriction determines which field to use when the XML file is generated for output. If more than one of the fields in the choice group contain a value, an error occurs and the export cannot finish because of ambiguity as to which field should be used.

The following example shows this type of <choice> list. In this example, an employee can be only one of the three types of employees (full-time, part-time, or contractor). So only one of the three corresponding fields can be contained in the <choice> element.

<xs:complexType name="employee">
  <xs:choice>
     <xs:element ref="full-time" />
     <xs:element ref="part-time" />
     <xs:element ref="contractor" />
  </xs:choice>
</xs:complexType>

13.3.1.2 Required Fields on Import

If your server has required fields, all of those fields must have a value set in order to perform an import. Mapping the required fields to an XML node provides the value. However, if any of the required fields are not mapped, a profile must be created that sets these values on import. If this is not done, the import fails.

13.3.1.3 Target Namespace and Qualified Locals

Explicitly declare a target namespace in the .xsd file and also specify that locally defined elements and locally defined attributes are qualified. The target namespace is specified by the targetNamespace attribute.

Local elements and attributes can be qualified globally by using the elementFormDefault and attributeFormDefault attributes on the schema element. They can be specified separately for each local declaration using the form attribute. Attribute values can be set to unqualified or qualified, to indicate if locally declared elements and attributes must be unqualified.

13.3.2 Configuring XSD for Importing and Exporting

Use this procedure to configure the schema definition for the export.

Choose Records then Import/Export from the Top menu. Choose Configure then Import/Export Schema.

The Configure Import/Export Schema Page opens. Click Add to create a schema definition to use for the export. The Create Import/Export Schema Page opens.

Enter the necessary information and click Browse to find an archive file for use. When done, click Create. The Upload Confirmation Page opens. Choose Configure Top Level Nodes from the Page menu.

The Configure Top Level Schema Nodes Page opens. Top level nodes are those that represent an entire object, such as a record or a folder. Highlight the nodes to include in the list, using the left or right arrows to move or remove the node. Choose mapping options in the mapping section, choosing the appropriate type from the menu lists. Click Save when done.

Choose Map Fields from the Page menu to map folder and content fields. The Configure Mappings Page opens. Use this page to map XSD fields to the Records system metadata fields for both records and folders. These mappings will be used for both exporting and importing. The custom mapping at the bottom of the page is used to resolve ambiguity when two different objects that are defined in the same XSD reference a common sub-object that must be mapped to different fields. To add fields, click Add at the bottom of the page and enter the new custom field. To delete custom fields, click the delete icon (a red X). Click Save when done.

13.3.3 Exporting and Importing XSD Data

After configuring the data to be exported, you can proceed with the import or export process.

Choose Records then Import/Export from the Top menu. Choose Export with Schema.

The Export with Schema Page opens.

Choose a schema name from the list and assign an archive batch name by expanding the existing archive batch names and selecting one.

Click Export.

Follow a similar procedure to import an archive using XSD mapping by choosing Import with Schema from the menu.

Choose Records then Import/Export from the Top menu. Choose Import with Schema.

The Import with Schema Page opens.

Choose a schema name from the list. Select an archive file by clicking Browse and navigating to the location where archives are located.

Click Import.

14 FOIA and Privacy Act Tracking

Important:

The FOIA/PA component is an example of usage and should not be used as is. It shows the types of decision points, workflow branches, and forms used in a typical FOIA/PA process. The process in use at your site may vary significantly from that shown here.

Oracle WebCenter Content: Records contains the functionality needed to comply with the Freedom of Information Act (FOIA) and the Privacy Act (PA) to track requests for information. The process is similar for both types of information requests. The main difference lies in the type of forms used in the information processing.

This functionality is available only if the FOIA/PA component is enabled during configuration. See the Oracle WebCenter Content Setup Guide for Records for details about choosing options.

When enabled, new links appear on the Setup Checklist page. Make sure to select Install Data Resource Files (Schema, etc.) to enable the necessary services to use this component. In addition, import the necessary archive by selecting Import FOIA Privacy Act Archive. This imports the workflow and other items needed for the component. Note that the workflow must be modified before enabling it for use.

When the FOIA/PA component is enabled, default users are added to populate different default alias groups. Because of the complexity of the FOIA/Privacy Act specification, the users are left in place to make it easier to match the FOIA configuration with the specification.

A FOIA profile is also installed making the necessary metadata fields available. If the FOIA component is later disabled, the FOIA profile and metadata fields remain. They should be removed if the component is disabled. See the Oracle WebCenter Content User's Guide for Records for information about profiles. See the Oracle WebCenter Content Application Administrator's Guide for Content Server for information about managing metadata fields.

This chapter provides an overview of the process of tracking, fulfilling, or denying information requests. This type of information processing is accomplished by using workflows. This chapter provides an overview of workflow usage but does not discuss the details of setting up or maintaining workflow. For complete details about using workflows including how to customize a workflow, see the Oracle WebCenter Content Application Administrator's Guide for Content Server.

The forms used with the functionality can be edited as needed. The forms are checked in as content items. To alter the forms, search for the form name then check out the form and edit the .hcsw or .hcsf files using an ASCII editor.

This chapter covers the following topics:

Section 14.1, "FOIA and DB2 Databases"

Section 14.2, "About Workflows"

Section 14.3, "The FOIA/Privacy Act Workflow"

14.1 FOIA and DB2 Databases

The FOIA/PA functionality contains an archive that is imported. This archive contains a table, FOIAPAMETA, that is used to store auxiliary metadata. This table contains 99 fields, 21 of which are memo fields. Memo fields are normally 2000 characters in length.

However, DB2 has a smaller row size limit than Oracle or SQL Server. With 21 memo fields, the FOIAPAMETA table would fail to import on a DB2 database because of this limit. Normally, when a memo field is created on a DB2 system, Configuration Manager uses a special DB2 data type called long varchar. But that doesn't apply when Archiver is importing a table.

To accommodate this, the memo fields in the FOIAPAMETA table have been manually changed so the size is set to 1000. This may not match the memo field size on the server where this component is installed if DB2 is used. There are two solutions for this problem:

Change the memo field size setting for the instance to 1000 to match what was imported with this table.

Change the length of the 21 fields in the FOIAPAMETA table to match what is expected on the server where the instance resides.

The second method is the recommended method for implementation.

14.2 About Workflows

Workflows are used to route content for review, approval, and eventual release. In this case, the content that is routed are the forms required for the FOIA/PA process.

Effective workflow design is an iterative process, continually refined as the process is implemented. Three types of workflows can be created:

Criteria workflows are used for content that enters the workflow process automatically based on content metadata that matches predefined criteria. Criteria workflows are used for FOIA and PA approvals.

Basic workflows are used for specific content items (for example, a particular document to be reviewed) and must be initiated manually.

Sub-workflows can also be used to split complex workflows into manageable parts and can be used with either a criteria or a basic workflow.

Workflows are composed of steps in which content is reviewed, approved or denied. Multiple reviewers can be assigned to approve or reject the content at each step. A set of users and the step type must be defined for each step in the workflow. Users assigned to a step can only perform the tasks allowed for that step type.

Workflows can be customized in several ways. Tokens can be used to designate unknown users. Aliases can be used to include a group of people in a workflow step. Jumps enable the creation of conditional statements to branch content through different paths in the same workflow or to route content to a different workflow. Exit conditions can prevent content from moving to the next step unless essential conditions are met. Custom metadata fields can be created and used to trigger different workflows.

For details about these customization tips and for examples of workflows, see the Oracle WebCenter Content Application Administrator's Guide for Content Server.

14.3 The FOIA/Privacy Act Workflow

The FOIA/PA workflow should be considered a starting point for the process to be used. It must be customized with users added as reviewers, specific rules added to reflect the process in place at different organizations, and additional steps added as needed. In addition, this version of the workflow reflects draft requirements specified by the Joint Interoperability Task Force (JITC). It should be expected that these requirements will change in the future and the procedures outlined here may then be outdated.

Only those request forms requiring approval go through a workflow process. Other necessary supporting forms must be filled out and filed in the requestor's folder. Those forms are linked to the main request using the Related Content functionality.

There is no set time frame for filing of those forms, but they must be completed before the workflow is completed when the request is either denied or serviced. Those forms are not discussed in this chapter.

This section discusses the current default workflows provided with the software. It is divided into task groupings, most of which are based on the decision points in the workflow. The finished, customized workflow at your site may have different decision points and tasks than those discussed here.

Section 14.3.1, "Processing Details"

Section 14.3.2, "Initial Required Setup"

Section 14.3.3, "Begin Request Processing"

Section 14.3.4, "First Decision Point: Expedited or Non-Expedited"

Section 14.3.5, "Second Decision Point: Service or Denial"

Section 14.3.6, "Third Decision Point: Denial Processing"

Section 14.3.7, "Fourth Decision Point: Appeal and Decision"

Section 14.3.8, "Final Actions"

14.3.1 Processing Details

When a workflow is started to process an information request, the stages of the workflow are automatic and may branch depending on the choices made during the process (for example, a denial of the information request, or the servicing of a request). It is important to know the stage where a request is currently in process because that will determine which workflow must be used for action.

The Active Workflows Page shows all types of workflows available with the system. When a user accesses a request being processed, the appropriate stage of the workflow must be chosen. The stage of the workflow is shown on the Workflow Content Page in the Step column.

Time limits are set according to the specification guidelines for each stage of processing. These limits are set within the workflow and can be changed if needed. See the Oracle WebCenter Content Application Administrator's Guide for Content Server for details about editing workflows.

To view current workflow assignments, choose My Content Server then My Workflow Assignments from the Main menu or click the My Workflow Assignments link on the Active Workflows Page.

14.3.2 Initial Required Setup

As mentioned earlier, the default workflow must be customized to add the appropriate users, steps, and decision points for your working environment. This must be done before using this functionality.

Forms are submitted from within a record folder, so make sure to set up the category structure beforehand. Categories should be created where FOIA and PA requests will be stored (for example, Open FOIA Requests and Open PA Requests). As information requests are received, a new folder must be created for each request within the appropriate category. This folder will house all of the paperwork associated with the request.Therefore, any people involved in the workflow process should be those users who have the necessary rights and roles to allow them to create and move folders. Depending on how the system is set up, users will receive notification e-mail with links to actions that can be performed depending on the user's rights and roles.

Categories must be created to store the finished requests. The naming and disposition rules for those categories is an organizational decision. Categories could be created based on final outcome (Granted in Full, Refused, and so on) or by date (for example, "December 2009 requests") or some other filing method.

In addition to creating folders, plan to track expenses associated with the request process. Information such as the fees collected, the staff allocated to the request, the time and money spent servicing the request, and the final result of the request should all be tracked independently in order for final reports to be produced. As noted previously, the workflow and reports documented here are based on the draft specification that may change in the future.

14.3.3 Begin Request Processing

The initial stage of the request process involves creating a folder for the request and filling out the appropriate form for the request.

14.3.3.1 Create a Request Folder

When a request for information is received, a new folder for the request must be created. All information associated with the request will be stored in that folder. For complete details about creating folders, see the Oracle WebCenter Content Setup Guide for Records.

Choose Browse Content then Retention Schedule from the Main menu. Click the category name for use.

The Exploring Category Page opens. Choose Create then Create Records Folder from the Page menu. The Create Record Folder Page opens.

Enter the appropriate metadata information and click Submit when finished.

14.3.3.2 Create a Request

After the folder is created, initiate a form for the request from within the folder.

Choose Create then the type of request from the Actions menu of the folder or select these options from the Page menu of the Folder Information Page. The same menus are available for FOIA Requests or Privacy Act Requests but different default data is filled in on the forms depending on the type of request. Request types include:

Access Request Form: Used to request access to records under the Freedom of Information Act or the Privacy Act (depending on which menu option is chosen).

Amendment Record Form: Used to request a change or amendment to a record.

Disclosure Record Form: Used to initiate the process to make records available for disclosure.

Other: Forms used to track information for the request. The form used will vary depending on the type of request and how it progresses through the workflow.

Access Record Form

Accounting Record Form

Appeal Request Form

Denial Record Form

Disclosure Record Form

Dispute Record Form

Exemption Record Form

Matching Program Records Form

Privacy Act File

System of Records Form

If adding supplementary information to a previously created file request, select one of the forms from the Other category. The appropriate form opens. Fill out the form and click Submit when done. The form is filed in the folder with other documentation for the request.

If beginning the request process, select one of the request types. The chosen form opens: the Access Request Form, the Amendment Record Form, or Disclosure Request Form.

Fill in the appropriate information for the request and click Submit when done.

A submission confirmation is displayed.

14.3.4 First Decision Point: Expedited or Non-Expedited

When a request is submitted for information, the first decision point revolves around if the request will be expedited or not. The request form contains a field that specifies if the requester wants expedited processing, but that is not what determines this decision. This decision should be made by the FOIA/PA processors.

An expedited request is immediately serviced without further information needed. A non-expedited request requires review and may be denied after review.

14.3.4.1 Review Request Form and Route

The first decision point in the workflow will be to route the request to the proper workflow by choosing the type of request.

Choose Content Management from the Main menu then Active Workflows. A list of current workflows is displayed.

Choose FOIA Requests. A Workflow Content Page opens, listing items in workflows and the steps where the workflow is currently processing. Click the Workflow Review icon for the item to review (the document icon next to the Actions menu icon).

The submitted request is displayed within a Workflow Review Page.

Select Expedited or Non-Expedited in the Review Workflow pane (on the left side of the page) to route the request. The Workflow Review Page opens, showing that appropriate sub-workflow is started in the Step column.

Click the Workflow Review icon to continue workflow processing.

14.3.4.2 Send Acknowledgements

An acknowledgement of the request must be sent regardless of the request type (expedited or non-expedited).

If the workflow process was exited, choose Content Management then Active Workflows to show all available workflows. Choose FOIA Requests to show all requests currently in the initial stage of processing (this is applicable for FOIA requests and Privacy Act Requests). The Workflow Review Page opens.

If still in the workflow process, click the Workflow Review icon for the request to process. The Workflow Review Page opens. Note that the action options in the Workflow Review Pane have changed to match the current workflow step.

Click Acknowledged. A search page opens. Use this page to search for items that were used to acknowledge the request.

Enter metadata for the search fields. Click Search when done.

A list of content items matching the criteria is displayed. Select the checkbox of the item to use and click OK. The Workflow Review Page opens again with the new workflow step indicated in the Step column.

14.3.5 Second Decision Point: Service or Denial

If this is an expedited request, the next step will be to service the request by providing the requested information. If a request is denied, fill out the appropriate forms to indicate why the request is denied and what steps the requestor can take to appeal the denial.

Figure 14-1 Expedited Sub workflow

If this is a non-expedited request, the request will be evaluated and perhaps serviced or denied.

Figure 14-2 Non-expedited sub workflow

14.3.5.1 Servicing a Request

The software is not used to fulfill the request but is used to track the process of fulfilling the request. Therefore, after the information has been released to the requestor, it must be indicated in the workflow that the request has been serviced.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Select Expedited Subs if this was an expedited request that will be immediately serviced.

The Workflow Content Page opens, showing all requests in that sub-workflow.

Click Workflow Review for the request to be serviced. If still in the workflow process, click the Workflow Review icon for the request to be serviced on the Workflow Content Page.

The Workflow Review Page opens. Note that the action options in the Review Workflow pane have changed to match the current workflow step.

Select Serviced on the Workflow Review Pane.

A search page opens.

Enter metadata to search for items that will fulfill the request. Click Search when done.

A search results page opens.

Select the checkbox for those items used to fulfill the request. Click OK when done.

The Final Result Dialog opens. Enter the information to be included on the final reports, including the final result, fees collected, number of people involved in servicing the request and total cost of servicing. Click OK when done.

14.3.5.2 Denying a Request

A request may be denied for a variety of reasons. If the request is denied, a Denial Request Form must be filled out before proceeding.

Note that at this stage of the workflow process, it is possible you are not creating a new denial but are reviewing a denial created outside of the workflow (a direct denial) to make a decision about its outcome. Choose the appropriate Denial Form depending on the type of denial in process.

If still in the workflow process, click the Workflow Review icon for the request.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Non-Expedited Sub (a request cannot be denied that was initially chosen as expedited). For details, see Section 14.3.4.1, "Review Request Form and Route."

Click the Workflow Review icon of the request to process.

The Workflow Review Page opens. Note that the action options in the Review Workflow Pane have changed to match the current workflow step.

Choose Recommend Denial - New or Recommend Denial - Existing from the Review Workflow pane.

The Denial Record Form opens.

If this is a new denial, enter the necessary data for the denial and click OK. If this is a previous denial, a search dialog opens. Select the submitted denial form. This links the two forms together. Click OK when done.

A submission confirmation page opens. Click OK.

The Workflow Content Page opens. The request is listed and the Step column is changed to DenialDecision.

The denial form is filed into the request folder and the workflow process moves to the next step. The denial is forwarded to the appropriate reviewers for a decision.

14.3.6 Third Decision Point: Denial Processing

A denial of request can have one of two different outcomes:

The denial can be disapproved. This means the denial will be returned to the reviewer who denied it and it must be serviced (for details, see Section 14.3.6.1, "Refusing a Denial" and Section 14.3.5.1, "Servicing a Request.")

The denial can be approved. If a denial of service is approved, the requestor is notified of the denial and can appeal that decision within a sixty day time frame. For more details about the appeal process, see Section 14.3.7, "Fourth Decision Point: Appeal and Decision."

If a request is denied and an appeal is not received within the sixty day time frame, the FOIA/PA workflow is concluded. For details about the final processing of the workflow, see Section 14.3.8, "Final Actions."

Figure 14-3 Denial processing sub workflow

14.3.6.1 Refusing a Denial

If still in the workflow process, click the Workflow Review icon for the request.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Denial Sub.

The Workflow Content Page opens, listing all items in this stage of processing. The Step column for a denied request is DenialDecision. Click the Workflow Review icon of the request to process.

The Workflow Review Page opens.

In the Review Workflow pane, choose Disapprove Denial to refuse the denial and have the request serviced.

The Workflow Content Page opens with the item listed. The Step column indicates the request has moved back to the Serviced stage.

Click the Workflow Review icon.

The Workflow Review Page opens. In the Review Workflow pane, choose Serviced to route the request for servicing.

14.3.6.2 Approve Denial

If still in the workflow process, click the Workflow Review icon for the request.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Denial Sub.

The Workflow Content Page opens listing all items in this stage of processing. The Step column for a denied request is DenialDecision.

Click the Workflow Review icon of the request to process.

The Workflow Review Page opens.

In the Review Workflow pane, choose Approve Denial to approve the denial and refuse to fill the request.

The Workflow Content Page opens with the item listed. The Step column indicates the request has moved to the AwaitAppeal stage.

14.3.7 Fourth Decision Point: Appeal and Decision

If a request has been denied, the requestor has sixty days to file an appeal of that denial. If an appeal is not filed, the workflow for that request concludes.

When notification is received that an appeal has been filed, access the folder housing the original request and file an Appeal Request form. An acknowledgement that the appeal was received and is being reviewed must also be sent. All paperwork for the appeal is filed using the same identification as the original denial and the original Access Request Form, thus linking the records together.

It may be possible that you are not creating a new appeal form but are reviewing an appeal created outside the workflow process to make a decision about its outcome. Choose the appropriate Appeal Form depending on the type of appeal being processed (a similar action can occur when processing denials).

Figure 14-4 Appeal process sub workflow

14.3.7.1 Initiating an Appeal

If still in the workflow process, click the Workflow Review icon for the request on the Workflow Content Page.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Denial Sub. A list of all requests in this stage is displayed.

Click Workflow Review for the request being processed.

The Workflow Review Page opens. Note that the action options in the Review Workflow Pane have changed to match the current workflow step. Choose Appeal Received - New Form or Appeal Received - Existing Record.

If this is a new appeal, a search page opens. Use this page to search for the original request item. That item will be linked to this denial form and the denial stored in the appropriate folder.

If this is an existing appeal, a search page opens. Use this page to search for the appeal already submitted.

The Workflow Content Page opens. The request is listed and the Step column is changed to Acknowledge.

14.3.7.2 Acknowledging an Appeal

If still in the workflow process, click the Review Workflow icon for the request on the Workflow Content Page.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Appeal Sub. A list of all requests in this stage is displayed.

Click Workflow Review for the request being processed.

The Workflow Review Page opens. Note that the action options in the Workflow Review Pane have changed to match the current workflow step.

Click Acknowledged. A search page opens. Use this page to search for items used to acknowledge the request.

Enter metadata for the search fields. Click Search when done.

A list of content items matching the criteria is displayed. Select the checkbox of the item to use and click OK. The Workflow Content Page opens again with the new workflow step (AppealDecision) listed in the Step column.

14.3.7.3 Reviewing the Appeal

If still in the workflow process, click the Review Workflow icon for the request on the Workflow Content Page.

If the workflow process was exited, choose Content Management then Active Workflows to display all available workflows. Choose FOIA Appeal Sub. A list of all requests in this stage is displayed.

Click Workflow Review for the request being processed.

The Workflow Review Page opens with the original access request. Note that the action options in the Workflow Review Pane have changed to match the current workflow step.

Choose Approve Appeal to approve the appeal and route the request for servicing. For details, see Section 14.3.5.1, "Servicing a Request."

Choose Disapprove Appeal to end the workflow process. The Final Result Dialog opens. Enter the information to be included on the final reports, including the final result, fees collected, number of people involved in servicing the request and total cost of servicing. Click OK when done.

14.3.8 Final Actions

When processing is finished for a request, move the folder to the appropriate category that was previously created.

Follow these instructions to move a folder to a new location:

Navigate to the folder to be moved. Choose Edit then Move from the Page menu.

The Select Category or Folder Page opens. If necessary, click the plus sign icon to expand the view of the items.

Click the category name where the folder should be moved then click OK.

The Exploring Retention Category Page opens, listing all folders in that category.

15 Using Federated Search and Freeze

Federation is a term used to describe the process of providing a single point of contact/entry for searching multiple disparate data sources. This is often used during the legal discovery process. For example, by using the Federated functionality with the Records system, a legal officer can search all repositories and catalogs for items pertaining to a legal matter. The search results then connect all the items together in one place in order to perform legal searches.

Federated search is most effective when used with the adapters that manage content on remote repositories.

This chapter describes how to use Federated Search to gather information needed for a discovery action and how to use Federated Freeze to freeze those items. It discusses the following topics:

Section 15.1, "Federated Searches"

Section 15.2, "Performing a Search"

Section 15.3, "Federated Freeze"

Important:

Federated Search functionality is not visible until the RmaNoSecurity right is added to a role. This right is not added by default to any role and must be enabled for the functionality to be accessible. This right should not be treated lightly or granted indiscriminately.

In addition, a system administrator role is needed to use this functionality.

15.1 Federated Searches

Federated Search is available when an external repository (an adapter) is installed.

As part of a discovery process, organizations might search for or freeze content across multiple repositories that are managed by adapters. Oracle WebCenter Content: Records uses external adapters to search metadata and full text of remote repository items. With this functionality, a user can:

Create searches by sending the search criteria to the adapter. External adapters check periodically to see if there are searches pending, perform the searches, and return the search results. The adapters may perform the search in a delayed timeline, requiring users to wait for the search results to complete.

Freeze the content returned from a completed scheduled search. While scheduled freezes are initiated immediately, the Records system performs the freeze in the background.

View detailed information about a scheduled search or freeze.

View search or freeze results.

Delete a scheduled search or freeze.

15.1.1 Federated Search Query Builder

To access the Federated Search Query Builder choose Search then Global Search in the Top menu. The following options are available:

Central Catalog Search is used for external content already registered with the system. This is a search of local metadata and is usually a faster search than Remote Repository items.

Note that it is up to the adapter configuration to make adapter content visible to the the Records system server. If the adapter has not made its content available, content will not be found in a search.

Remote Repositories Search is used to find items stored on external content systems whether they have been cataloged on the the Records system server or not. This is a search of all possible content using adapters to schedule the search. The adapters use the criteria entered for a Remote Repository Search as the criteria used for the search on that remote repository. Searching for content in Remote Repository is not in real time and is dependent on adapters to complete the search. This option provides the most accurate and up-to-date results but it may take a long time to complete.

Note:

Federated Search adds functionality to the Search Query Builder Form. See the Oracle WebCenter Content User's Guide for Content Server for additional help using the Search Query Builder.

SES Search is similar to a Remote Repository Search but the search is not scheduled and run by an adapter. Instead, a connection is made to an SES server which has done a scheduled crawl of content on the adapter(s). Oracle WebCenter Content: Records connects directly to the SES server, which has been configured ahead of time. If this option is selected and no servers have been configured, an error message is displayed.

The Federated Query Builder Page enables users to build and schedule queries across all repositories. Select the repositories to include in the search from the External Sources list. Multiple sources can be included in the search.

Select a field to use as sorting criteria and click Search when done. When performing a remote repository search, a search name must be entered. Users can only search using fields that are mapped to all of the selected external sources. Errors occur if a search is done against a source using a field that is not mapped.

After pressing Save enter a title for the action. The search is scheduled and the Federated Searches Page appears. The list of scheduled searches includes the number of external sources requested in the search, and number of external sources that have completed the search request.

The search is scheduled and waits for the external search adapters to return results.

To return to the Federated Searches Page, choose Records then Scheduled then Federated Searches from the Top menu.

15.2 Performing a Search

Follow this procedure to perform a search of a remote repository:

Choose Search then Global Search from the Top menu. Choose the type of repository search to perform.

The Federated Query Builder Page opens.

Select the external sources to use in the query from the pull-down list.

Select Include Content to retrieve copies of the content matching the search criteria. This option is only available when performing a remote repository search.

Do not select this box unless search results are certain. Returning a copy of the data takes long and uses space. Fine tune the query first and verify what items will be returned before actually retrieving the content. For more information about content retrieved during a search, see Section 15.2.1, "About Returned Content."

Choose the fields to use for searching. The Search Builder menu is used to select fields for use in the query. Only search using fields that are mapped to all of the selected external sources. Errors occur if a search is done against a source using a field that is not mapped.

After a field is selected for use, additional menus are available to further refine the criteria. Boolean operators can be used to combine fields. Click the insert symbol (a plus sign) to access a menu of Boolean operators. Click the remove symbol (a lowercase x) to clear previous selections. Additional wildcard search operators, such as Matches and Substring, enable further flexibility in query building.

Enter a search term for full-text searching. If a search is done across all sources, be aware that some adapters may not be able to perform a full text search. When choosing a search type, make sure to choose types that are valid for the adapters in use. For example, if a user chooses full-text search to use with an adapter that does not allow that option, an error is returned.

Enter a search name. A Federated search is performed on the adapter's schedule, so it may not occur immediately. A search name allows users to check the status of the scheduled Federated search. No uniqueness validation is performed on this field because the unique identifier is an assigned Federated Search ID.

Select the result output criteria by indicating a number of results per page and the sorting criteria used for the results.

Click Search when done. The query is routed to the chosen adapters and is completed according to the adapter configuration.

15.2.1 About Returned Content

Saved content is stored in a zip file and is checked into the Records system as internal content. These returned content items can be accessed and treated as standard local items. Users can set dispositions on the files, establish specific rules for their handling, and so on.

Some adapters may return the content in multiple files because the adapter may be configured to chunk data into manageable units. This behavior is controlled on the adapter side and cannot be modified

15.2.2 Checking Search Progress

Federated searches are performed according to adapter schedules which may vary according to the different configurations. To check the progress of the search, choose Records then Scheduled then Federated Searches from the Top menu. Or click the Federated Searches Link on the Federated Query Builder Page.

The Federated Searches List Page opens. This page shows the scheduled searches and their progress. The following options are available on the Actions menu for each search:

Show Search Results: Opens the Federated Search Results Page for the selected search. If multiple external sources were selected in the search, the Search Results Page organizes the results by external source. The search results for individual external sources can also be displayed.

Show Search Details: Opens the details for the selected search. Within the Federated Search Details Page, users can view the search results for individual external sources, freeze the search results, download the files returned for the search, and create a similar search.

Note:

Users can freeze items in the returned search results per external source. If multiple external sources have been defined in the search, but have not all returned results, users can schedule a freeze on the sources that returned results for the scheduled search.

Subscribe to Search: Subscribes the user to the search and opens the Content Information Page for the query. For more details, see Section 15.2.3, "Subscribing to a Search."

Create Similar Search: Opens the Federated Query Builder Page, pre-populated with search criteria used in the selected search. Users can modify or add criteria to schedule a new search.

Delete Search: Deletes the selected scheduled search. See Deleting a Search for details.

15.2.3 Subscribing to a Search

When a Federated search is created, a content item is checked into the local repository with details of the search. If a user chooses Subscribe to Search on the Actions menu for an item on the Federated Searches List Page, the user is subscribed to the content item for that query.

As results are returned for the saved search, the content item is updated. For example, if a query is set to use three repositories and results are returned from one, the content item is updated and a notification is triggered to those people who are subscribed to the content item.

15.2.4 Deleting a Search

A Federated search can be deleted at any time. Search results do not have to be returned to delete the search.

To delete a search, deselect the checkbox for the search on the Federated Searches List Page then choose Delete on the Table men. A message is displayed, indicating the search and all returned results will be deleted. Any pending search results will be ignored.

15.3 Federated Freeze

Federated Freeze is used in conjunction with Federated search, to freeze search results from a Federated query.

Note:

Federated Freeze adds functionality to content freezing used in the Records system. See the Oracle WebCenter Content Setup Guide for Records for additional information about freezes.

When freezing content on an external repository, first schedule a Federated Search, then run a Federated Freeze on the returned results. If the search result that is selected for freezing has not been registered with the Records system yet, an external record is created for it automatically using the metadata returned in the search results. This new external record is then frozen.

The Frozen Federated Search Content Page opens for review or further action. The list of frozen scheduled searches includes the external source of the frozen content, and the status (scheduled, completed or errors) of the freeze.

The following options are available from the Actions menu for a frozen item:

Show Freeze Errors: Displays the items with errors during the selected freeze. Freeze errors may occur if the checked-in items from the Federated Search do not have all required fields defined or if the items do not pass validation.

Refreeze Errors: Reschedules the freeze for the error items in the selected search task.

Delete Freeze: Deletes the selected freeze.

15.3.1 Freezing Search Results

Follow this procedure to freeze search results:

Choose Records then Scheduled from the Top menu. Choose Federated Searches.

The Federated Searches List Page opens.

Choose Show Search Results from the Actions menu of a search.

The Federated Search Results Page opens.

Select the checkbox of the items to freeze then choose Freeze from the Table menu.

A dialog box opens.

If freezes have been added to a My Favorites list, they appear on the list. Choose a freeze name from the list or select Show All Freezes to display all defined freezes.

Enter a reason for the freeze.

Click OK.

The search results are frozen.

15.3.2 Viewing Scheduled Freezes

Use this procedure to view which results are frozen:

Choose Records then Scheduled from the Top menu. Choose Federated Search Freezes.

The Frozen Federated Search Content Page opens, showing all items found during a federated search that are frozen.

A User Interface

This section contains information about the interface that is used with the product.

The following pages are shown in this chapter:

Section A.1, "Configure Retention Settings Page"

Section A.2, "Configure Physical Content Management Page"

Section A.3, "Update Interface"

Section A.4, "Classified Content Interface Pages"

Section A.5, "Barcode Interface"

Section A.6, "Offsite Storage Interface Pages"

Section A.7, "Subject to Review (Vital) Interface Pages"

Section A.8, "Scheduling Interface Pages"

Section A.9, "Retention Assignment Interface Pages"

Section A.10, "Configure Report Settings Page"

Section A.11, "Customization, Monitoring and Audit Pages"

Section A.12, "Import/Export Interface Pages"

Section A.13, "FOIA and PA Interface Pages"

Section A.14, "Federated Search and Freeze Pages"

Several buttons are common to many pages and are not discussed unless additional information is available:

Submit: Submits the changes made to the page.

Reset: Clears any entries and resets the page to its default.

Quick Help: Opens the help entry for the page.

Delete: Removes the item on the page.

Create: Submits the information provided and creates the item.

Info: Opens the Content Information page for the item.

Thumbnail View: Opens the page in thumbnail view.

Headline View: Opens the page in headline view.

A.1 Configure Retention Settings Page

This page is used to set most of the configuration options for the system. When initially opened, the options on this page are unexpanded. Click a link next to an option to expand it.

Permissions:

The Admin.RecordManager right is required to use this page. This right is assigned by default to the Records Administrator role.

To access this page, choose Records then Configure then Settings from the Top menu.

Most configuration tasks are discussed in the Oracle WebCenter Content Setup Guide for Records.

A.2 Configure Physical Content Management Page

This page is used to configure many aspects of PCM.

The Physical Item Information Page, also discussed in this section, contains information about individual physical items that are managed by PCM.

Permissions:

The PCM.Admin.Manager right is required to access this page. By default, this right is assigned to the predefined PCM Administrator role.

To access this page, choose Physical then Configure then Settings from the Top menu.

The Batch Services option is only displayed if the corresponding option on the Configure Physical Content Management Page is enabled.

The menu items available to users depend on the rights they have been assigned. A content administrator with all access rights (typically assigned the predefined PCM Administrator role) will see all administrator menus. Other users (for example, those assigned the default 'pcmrequestor' role) may see a much smaller subset of the administrator menus, depending on their assigned rights.

A.2.1 Physical Item Information Page

This page is used to view information about a physical item.

Permissions:

The PCM.Physical.View right is required to use this page. This right is assigned by default to the PCM Requestor and PCM Administrator roles.

To access this page, search for the item. On the search results page choose Information then External Item Information in the item's Actions menu.

This page shows the current properties of the physical item, including its basic metadata (name, title, filer, and security group), its freeze status, its object and media types, its storage location, and barcode label.

Note the following:

If the repository is set up to auto-generate content IDs (in the System Properties utility), the name of a physical item was generated automatically. It is typically a number, possibly preceded by a prefix (for example, ID_002319).

If the physical item was assigned a life cycle (retention schedule and disposition rules), the information page also includes a Retention Schedule Information section providing disposition processing and security information for the item.

If the physical item is currently checked out, its current location is set to the value of the deliver-to location as specified when the associated reservation request was created. If no location was provided, the current location is set to OTHER. If a location comment was specified for the associated reservation request, the Current Location Comments field shows this comment. Otherwise it contains the login name of the user who created the reservation request.

If the physical item is contained within another physical item, the current location and/or permanent location field includes a Container Details link, which opens the information page of the parent physical item (the "container").

A.3 Update Interface

The following pages are accessed when using the update functionality:

Section A.3.1, "Define Query Page"

Section A.3.2, "Query Schedule Section"

Section A.3.3, "Scheduled Update Page"

Section A.3.4, "Update Preview Page"

A.3.1 Define Query Page

This page is used to define what fields will be updated and what values will be used for updating.

To access this page, choose Records then Global Updates then the type of update from the Top menu.

Frozen content cannot be updated.

The options on this page are specific to the type of query being created. After an option is selected, additional menus open to help further refine the query. See the Oracle WebCenter Content User's Guide for Content Server for complete details about using queries.

A.3.2 Query Schedule Section

The Schedule portion of the Define Query Page is used to choose the times when updates will occur.

To access this portion, click Schedule on the Define Query Page. Select values from the lists for the update schedule and click Submit when finished.

A.3.3 Scheduled Update Page

This page shows the results of scheduling an update action.

This page opens after scheduling an update or search or by choosing Records then Scheduled then Search and Update Events from the Top menu.

Use the Actions menu for the individual event to change the options for the event.

Element
Description

Metadata Sets
The type of update that was selected.

Scheduled Search and Update Event Name
The event name entered when the update was created.

Date Event Created
The date when the scheduled event was created.

Actions
Menu with options for individual events:

Run Now: Runs the event without waiting for the scheduled time.

Edit Scheduled Event: Opens the Define Query Page where the event can be edited.

Delete Scheduled Event: Deletes the event.

A.3.4 Update Preview Page

This page shows those items that will be changed when an update is done.

To access this page, click Preview Results on the Define Query Page.

The Update icon (a capital W in a circle) indicates that the item is not locked and can be changed. Click the Info icon to view the Information Page for the item.

To return to the Define Query Page, choose Continue Defining Search on the Page menu.

A.4 Classified Content Interface Pages

The following pages are used when reviewing or altering the classification of items:

Section A.4.1, "Review Classification Page"

Section A.4.2, "Upgrade or Downgrade Classification Page"

Section A.4.3, "Declassify Page"

A.4.1 Review Classification Page

This page is used to review the classification of content.

To access this page, choose Information then Review Classification from the Page menu on a Content Information page.

A.4.2 Upgrade or Downgrade Classification Page

This page is used to change the classification of an item.

To access this page, choose Edit then Upgrade Classification or Downgrade Classification from the Page menu on a Content Information page.

A.4.3 Declassify Page

This page is used when declassifying content.

To access this page, choose Edit then Declassify from the Page menu on a Content Information page.

A.5 Barcode Interface

Barcode processing has the following user interface screens:

Section A.5.1, "Main Barcode Utility Screen"

Section A.5.2, "Barcode Upload Screen"

Section A.5.3, "Configure Host List Screen"

Section A.5.4, "Barcode Upload Results Screen"

Section A.5.5, "Program Videx Barcode Wand Screen"

Section A.5.6, "Barcode Processing Page"

Section A.5.7, "Barcode File Processed Page"

A.5.1 Main Barcode Utility Screen

This screen is used to upload information to the PCM software or write it to a file.

To access this screen, start the Barcode Utility application.

Element | Description
Options | Opens the Program Videx Barcode Wand Screen.
Scanner Type | Barcode scanner type. One type is currently supported.
Scanner Port | Communication port where the barcode scanner or its base station is connected. Normally this is COM1, a commonly used serial port.
Download to File Only | If selected, writes barcode scanner data to a file for later processing.
Allow File Selection | If selected, uses a previously stored file for processing.
Process | Starts the upload process. The barcode scanner data will either be directly uploaded to Physical Content Management or, if Allow File Selection was selected, a file selection dialog opens, where the file to be uploaded can be selected.
Done | Closes the Barcode Utility application.

A.5.2 Barcode Upload Screen

This screen is used to specify the instance where data will be uploaded.

To access this screen, select Allow File Selection on the Main Barcode Utility Screen. Click Process.

Element | Description
Host | Name of the instance where the barcode information should be uploaded. The instance should be running Physical Content Management.
User | Login name of the user who will connect to the instance to upload the barcode data.
Password | Login password of the user who will connect to the instance to upload the barcode data.
Advanced | Opens the Configure Host List Screen, which shows all instances where barcode data can be uploaded.

A.5.3 Configure Host List Screen

This screen is used to specify the instances where barcode data can be uploaded. The defined hosts are included in the Host list on the Barcode Upload Screen.

To access this screen, click Advanced on the Barcode Upload Screen.

Element | Description
Host Name | Name of an instance where barcode information can be uploaded. The instance should be running Physical Content Management.
CGI URL | URL of the idcplg directory of the instance. This information is required to establish a connection to the instance.

A.5.4 Barcode Upload Results Screen

This screen provides information about what barcodes were processed and also shows the upload results of each item processed (including any error messages).

This screen appears after uploading a stored barcode file.

Element | Description
Error | Indicates if an error occurred during processing of an item. The error message is displayed in the Message column.
Date | Date and time the information was scanned by the barcode scanner.
Type | Type of action performed for the item. Three actions are possible: Check In, Check Out, and Set Home & Actual.
Object Type | Object type of the data item (for example, Box or Folder).
Barcode ID | Barcode value of the item as read by the barcode scanner. For storage items, this is the item's name as specified when it was created in Physical Content Management.
Location Type | Location type of the item (for example, Box for items in a box, or User for items that are checked in or checked out).
Location | Barcode of the location where the item is assigned (stored).
Message | Message if an error occurred during the transfer.

A.5.5 Program Videx Barcode Wand Screen

This screen is used to program the barcode scanner.

To access this screen, choose Options then Program Videx Wand from the Main Barcode Utility Screen.

Element
Description

Communication Device
Selects the device used to connect the barcode scanner to the computer:

Jet Eye: An infrared receiver device connected to a COM port on the computer. Point the barcode scanner at the receiver to communicate with the computer.

Base Station: A holder for the barcode scanner linked directly to the computer using a cable.

Scanner Port
Selects the communication port where the barcode scanner or its base station is connected. Normally this is COM1, which is a commonly used serial port.

Program
Starts the programming cycle of the barcode scanner.

A.5.6 Barcode Processing Page

This page is used to select a barcode file to be processed.

Permissions:

The PCM.Barcode.Process right is required to use this page. This right is assigned by default to the predefined PCM Administrator role.

To access this page, choose Physical then Process Barcode File from the Top menu.

Element | Description
Select File to Process | A barcode file to be processed. Enter a name or use Browse to select a file.
Process File | Starts the analysis and processing of the selected barcode file.

A.5.7 Barcode File Processed Page

This page shows information about all the items in the barcode file, the actions performed on them and any status and error messages.

This page opens after a barcode file has been selected on the Barcode Processing Page and processed.

Element | Description
Date | Date and time the information was scanned by the barcode scanner.
Action | Action performed for the item.
Object Type | Object type of the data item (for example, Box or Folder).
Barcode ID | Barcode value of the item as read by the barcode scanner.
Location Type | Location type of the item (for example, Position.)
Location Barcode | Barcode of the location where the item is assigned (stored).
Message | Message if an error occurred during the transfer.

A.6 Offsite Storage Interface Pages

The following pages are used to set up and use the offsite storage functionality:

Section A.6.1, "Offsite Storage General Setup Page"

Section A.6.2, "District Mapping Pages"

Section A.6.3, "Create Manual Pickup Page"

Section A.6.4, "Browse Uploaded Files Page"

Section A.6.5, "Browse Processed History Page"

A.6.1 Offsite Storage General Setup Page

This page is used to begin setting up offsite storage.

To access this page, choose Physical then Offsite Storage then General Setup from the Top menu.

Element
Description

Customer ID
Customer ID for this storage session.

Default District
Default district to be used with this customer ID. Several districts are provided. New districts can be also be created.

FTP Address
FTP address associated with this storage location.

FTP User and Password
User associated with the FTP account and the user password.

Transfer options
Options associated with the transfer:

Automatically transfer new items: enables automatic transfer of any new items.

Automatically return checked in items: enables automatic returns of checked in items.

Enable workflow: starts a criteria workflow to handle the approval of items pending transfer. An internal file is checked in with a list of objects for approval. Objects can be removed from the list or approved for transfer.

Use general requestor for Offsite Requests: indicates a requestor should be used.

General Requestor
Requestor for storage setup. Use 5 characters or less.

Box Identifier
Method of identifying boxes used in transfer.

A.6.2 District Mapping Pages

Several similar pages are used to map metadata to districts used when configuring offsite storage. A sample page is depicted and described here.

Section A.6.2.1, "Choose District Mapping Page"

Section A.6.2.2, "Map Metadata Pages"

A.6.2.1 Choose District Mapping Page

This page is used to select the district for which to map data.

To access this page, choose Physical then Offsite Storage from the Top menu. Choose Map District Metadata.

Scroll up or down in the list and select a district by highlighting the name. Districts that are already mapped are in bold face type at the top of the list. After highlighting a district, click Configure.

A.6.2.2 Map Metadata Pages

After selecting a district to configure on the Choose District Mapping Page, the next page in the District Mapping process opens.

To access this page, choose a district to map on the Choose District Mapping Page and click Configure.

All pages in this process are similar. The fields and field values in the option lists on these pages are provided by Iron Mountain. For a description of the fields and their values, see the Iron Mountain documentation.

The following pages can be configured. Either configure all pages in sequence or skip to a specific page by selecting the page name from the menu list at the top of the page:

Box metadata

File metadata

Accounting metadata

Insurance1 and Insurance 2 metadata

Law metadata

Loan metadata

Medical metadata

A.6.3 Create Manual Pickup Page

This page is used to create a request for pickup of boxes and files for offsite storage.

To access this page, choose Physical then Offsite Storage then Create Manual Pickup Request from the Top menu.

The fields on this page are determined by Iron Mountain. Consult the Iron Mountain documentation for details.

A.6.4 Browse Uploaded Files Page

This page is used to view a list of all uploaded files and their status.

To access this page, choose Physical then Offsite Storage then Uploaded Files List from the Top menu.

Element | Description
Delete | Deletes a selected item or multiple items.
Resend | Used to resend the checked item.

A.6.5 Browse Processed History Page

This page is used to view a list of all processed history files and their status.

To access this page, choose Physical then Offsite Storage then Processed History Files List from the Top menu.

A.7 Subject to Review (Vital) Interface Pages

The following page is used to manage review information:

Section A.7.1, "Edit Review Information for Retention Category/Folder Page"

A.7.1 Edit Review Information for Retention Category/Folder Page

This page is used to edit information about reviewers for retention categories.

To access this page, find a retention category to edit. Choose Edit then Edit Review from the item's Actions menu. User-friendly captions are noted in parentheses in the following table.

Element
Description

Vital (Subject to Review)
If selected, enables the retention category as a subject to review category. After selecting, enabling, enter a reviewer user name in the text box and select the associated period from the list. Default: Not selected. Not a retention category that is subject to review.

If a retention category has a review period of shorter duration than the review period set for its child record folder, the child record folder assumes the shorter review period and ignores its own setting. The shorter review period takes precedence.

Vital Reviewer (Reviewer)
A reviewer for the item. Use the system default reviewer as specified on the Configure Retention Settings Page or select one from the list. The selected reviewer receives e-mail notification when it is time to review and cycle content items.

Vital Review Period (Review Period)
The number of review periods. Select the review period from the list. Required if Subject to Review is selected.

A.8 Scheduling Interface Pages

The following pages are used for scheduling:

Section A.8.1, "Scheduled Screening Reports Page"

Section A.8.2, "View History Page"

Section A.8.3, "Job Information Page/Edit Job Information Page"

Section A.8.4, "Scheduled Freezes Page"

Section A.8.5, "Edit Recurring Report Schedule Page"

Section A.8.6, "Scheduled Jobs Listing Page"

For details about scheduled Federated events, see Section A.14, "Federated Search and Freeze Pages." For details about scheduled update events, see Section A.3, "Update Interface."

A.8.1 Scheduled Screening Reports Page

This page lists all screening reports scheduled from screening pages.

To access this page, choose Records then Scheduled then Screening Reports from the Top menu.

To see a list of reports that have been produced, choose the Processed Reports option on the Table menu. A listing is displayed showing those reports that have processed.

After processing, information about the report is available. Click the Info icon to view a report's Content Information page. If the report did not process properly, the Info icon displays the error message received during processing.

Reports that were scheduled and are not recurring ('one-time' reports) are not displayed after they are executed but do appear on the Processed Reports page.

Element
Description

Job ID
Assigned identifier for the scheduled job.

Name
Name of the freeze used for the schedule.

Requesting User
User who initiated the scheduled freeze.

Job Type
Job type. One Time indicates the job is run once. Recurring indicates an action done on a repeating schedule. When a job is processed, it is removed from the display.

Start Date
Date the job will be initiated. If the job is a long type, the system checks within one day of the start date to see if the job needs to be run. If it is a short type, the system checks if the needs to be run within the hour of the start date and time.

If the job type is recurring, the job continues executing within a defined interval after the start date.

Last Processed Date
Date and time the recurring action was last generated.

Status
Current status of the scheduled screening report:

Processed: The scheduled report generated successfully and is not scheduled to be repeated.

Exception: The scheduled report did not execute successfully. The log file contains more details on the error(s) that occurred.

Active: The scheduled report is being executed.

Inactive: The scheduled report is in the queue of tasks to be performed and will be generated when scheduled, usually at midnight.

Cancelled: The scheduled report was aborted before it could be completed successfully.

Actions
Menu options relevant to the scheduled screening report. The available options depend on the type and status of the scheduled screening report, and may include:

View Log: Opens the Content Information page of the generated report.

Unschedule: Cancels the scheduling of the report.

Edit Subscription: Allows a user to subscribe or unsubscribe to the report. A subscription e-mail is sent whenever the report changes.

Run Report: Creates the report immediately. After the report is created, click the link in the Name column to view it. The report is in the format specified by the Report Format setting on the Configure Retention Settings Page.

View History: Opens the View History Page.

Edit Schedule: Opens the Edit Recurring Report Schedule Page where the scheduling properties can be modified.

Edit Criteria: Opens the associated screening definition page (for categories, folders, or content items), where the criteria for the screening report can be modified.

Remove: Removes the disposition action from the list of scheduled actions.

Info icon
Opens the Content Information page of the automatically generated report file. Use the Web Location or Native File link to view the file.

A.8.2 View History Page

This page shows a list of generated actions. The page depicted here is for a scheduled screening report. A similar page is used for scheduled recurring freezes.

To access this page, choose View History in the Actions menu for a recurring scheduled screening report.

Element
Description

Name
Name of the screening report as specified in the Scheduled Screening Reports Page. Click the link to open the screening report.

Process Date
Date and time the recurring screening report was generated.

Status
Status of the scheduled screening report:

Succeeded: The scheduled report generated successfully.

Failed: The scheduled report did not execute successfully. The log file contains more details on the error(s).

Cancelled: The report aborted before it could be completed successfully.

Actions
Opens a menu containing options relevant to the scheduled screening report:

View Log: Opens the Content Information page of the generated screening report.

Remove: Removes the disposition action from the list of scheduled actions.

Info
Opens the Content Information page of the automatically generated report file. Use the Web Location or Native File link to view the file.

A.8.3 Job Information Page/Edit Job Information Page

This page shows details about a scheduled recurring action. It can also be used to edit certain information about a scheduled job.

To access this page, choose View Report Info from the Actions menu of a scheduled recurring action (for example, Scheduled Recurring Report or Scheduled Recurring Freeze) on the Scheduled Screening Reports Page. You can also access this page by choosing Info from the Actions menu of a job on the Scheduled Jobs Listing Page.

The information depends on the type of action in question. The page depicted here is for a scheduled screening report.

To access the editable version of this page, choose Edit from the Actions Page menu while viewing the job information. You can also access an editable version by choosing Edit in the Actions menu of a job on the Scheduled Jobs Listing Page. This page is also used to schedule or edits jobs for Oracle WebCenter Content. The following information can be edited when using this page for the Records system.

Element
Description

Description
Description assigned to the job.

Category
Type of job (for example, screening or freeze).

Initial User
User who initiated the scheduled freeze.

Queue Type
Job type. Long indicates the job is run daily. Short indicates an action is done in an hourly timeframe.

Type
Once indicates the job is run once. Repeat indicates an action done on a repeating schedule. Immediate indicates the job should be processed at once.

Start Token
Date and time the job will be initiated.

Status
Current status of the scheduled screening report:

Processed: The scheduled report generated successfully and is not scheduled to be repeated.

Exception: The scheduled report did not execute successfully. The log file contains more details on the error(s) that occurred.

Active: The scheduled report is being executed.

Inactive: The scheduled report is in the queue of tasks to be performed and will be generated when scheduled, usually at midnight.

Cancelled: The scheduled report was aborted before it could be completed successfully.

Actions menu (Job Edit page only)
Opens a menu with options relevant to the scheduled recurring freeze. The available options depend on the status of the scheduled freeze and may include:

Edit: Opens an editable version of the page.

Cancel: Cancels the scheduling of the report.

Delete: Deletes the scheduled job.

A.8.4 Scheduled Freezes Page

This page shows all scheduled recurring freezes.

This page opens when a freeze is scheduled. It can also be accessed by choosing Reports then Scheduled then Freezes from the Top menu.

Element
Description

Job ID
Assigned identifier for the scheduled job.

Name
Name of the freeze used for the schedule.

Requesting User
User who initiated the scheduled freeze.

Job Type
Job type. One Time indicates the job is run once. Recurring indicates an action is done on a repeating schedule. When a job is processed, it is removed from the display.

Start Date
Date the job will be initiated. If the job is a long type, the system checks within one day of the start date to see if the job needs to be run. If it is a short type, the system checks if the needs to be run within the hour of the start date and time.

If the job type is recurring, the job continues executing within a defined interval after the start date.

Last Processed Date
Date and time the recurring action was last generated.

Status
Current status of the scheduled screening report:

Processed: The scheduled report generated successfully and is not scheduled to be repeated.

Exception: The scheduled report did not execute successfully. The log file contains more details on the error(s) that occurred.

Active: The scheduled report is being executed.

Inactive: The scheduled report is in the queue of tasks to be performed and will be generated when scheduled, usually at midnight.

Cancelled: The scheduled report was aborted before it could be completed successfully.

Actions
Opens a menu containing options relevant to the scheduled recurring freeze. The available options depend on the status of the scheduled freeze and may include:

View Log: Opens the Content Information page of the generated report.

Edit: Opens an editable version of the page.

Unschedule: Cancels the scheduling of the report.

Run Freeze: Creates the freeze.

Reschedule: Opens a page where the scheduling properties can be modified. If a job has been cancelled using the Unschedule option, using Reschedule changes the status of the job from Cancelled to Inactive so it is scheduled again.

Edit Criteria: Opens the associated screening definition page (for categories, folders, or content items), where the criteria for the screening report can be modified.

View History: Opens the View History Page.

Remove: Removes the item from the list of scheduled actions.

A.8.5 Edit Recurring Report Schedule Page

This page is used to modify the scheduling properties of a recurring screening report.

To access this page, choose Edit Schedule from the Actions menu of a scheduled recurring screening report in the Scheduled Screening Reports Page.

To modify a recurring screening report to become non-recurring (to run once), run the report manually then cancel it.

Element | Description
Report Name | Name for the scheduled screening report (if required).
Start Date | Date the first scheduled screening report should be generated according to the new schedule. All subsequent reports will be generated at the end of each recurring period after this date.
Period and Period Name | Interval when the recurring screening report should be created (for example, every 2 weeks).

A.8.6 Scheduled Jobs Listing Page

This page lists all scheduled recurring jobs.

To access this page, click Active Scheduled Jobs on a Job Information Page/Edit Job Information Page. This page can also be accessed by choosing Administration then Scheduled Job Administration from the Main menu. Choose Active Scheduled Jobs.

The icons in the Status column are a summary of information about the item. To see the meaning of an icon, hover the mouse cursor over the icon.

Depending on the type of action and the status, the following information may appear:

Priority: An indication of the priority. For example, High Priority.

Status: Status of the item. For example, Inactive.

Occurrence: Whether the item repeats (recurring) or occurs once.

Queue: Indicator of a short or long queue type for this action. A long queue indicates processing in a daily timeframe. A short queue indicates processing in an hourly timeframe.

A.9 Retention Assignment Interface Pages

The following pages are used when processing retention assignments:

Section A.9.1, "Retention Step Search Page"

Section A.9.2, "Schedule Retention Step Audit Report Page"

Section A.9.3, "Failed Dispositions Page"

Section A.9.4, "Pending Dispositions Page"

Section A.9.5, "Pending Reviews Page"

Section A.9.6, "Disposition Information Page"

Section A.9.7, "Disposition Parameter Dialog"

A.9.1 Retention Step Search Page

This page is used to screen disposition rules for specific types of steps.

To access this page, choose Records then Audit then Retention Steps from the Top menu.

The functionality on this page is similar to the functionality on a standard search page. See the Oracle WebCenter Content User's Guide for Records for details about performing searches and scheduling searches.

A.9.2 Schedule Retention Step Audit Report Page

This page is used to schedule a Retention Step Audit Report.

To access this page, click Schedule on the Retention Step Search Page.

Element
Description

Report Name
Name for the scheduled screening report.

Start Date
Date the scheduled screening report will be generated. If the screening report is recurring, the first screening report is generated for the first time on this date and subsequent reports at the end of each recurring period after this date.

If the start date is in the past, the processing is done with the next scheduled run.

Is Recurring
If selected, the scheduled screening report is generated periodically.

Period and Period Name
Interval when the recurring screening report is created (for example, every 2 weeks).

Subscribe
If selected, the logged-in user is subscribed to the checked-in report.

Report Template
Template to use for this report.

A.9.3 Failed Dispositions Page

This page shows disposition actions that have not processed correctly.

This page opens after choosing Records then Audit then Failed Dispositions from the Top menu.

To restart the disposition, select the checkbox for the item and choose Retry from the Table menu.

To mark the disposition as complete regardless of whether the action succeeded or not, select the checkbox for the item and choose Skip from the Table menu. Use this option with caution because it may have unforeseen consequences when a disposition is skipped.

To create a report of failed dispositions, select the items to include in the report then choose Create Reports from the Table menu.

A.9.4 Pending Dispositions Page

This page shows those actions needing approval. This example shows pending dispositions. A similar page is available for Pending Reviews.

Permissions:

The Admin.PerformActions right is required to use this page. This right is assigned by default to the Records Administrator role. In addition, the user must be designated as the notification recipient when performing actions for others.

To access this page, choose Records then Approvals then the type of approval from the Top menu.

Element | Description
ID | Category affected by the disposition and the step involved. Note that processing begins with step 0.
Name | The disposition action.
Filer | User who initiated the disposition.

A.9.5 Pending Reviews Page

This page shows all reviews that need to be performed.

To access this page, choose Records then Approvals from the Top menu. Choose Pending Reviews.

Permissions:

The Admin.PerformActions right is required to use this page. This right is assigned by default to the Records Administrator role. In addition, the user must be designated as the notification recipient when performing actions for others.

A.9.6 Disposition Information Page

This page shows the actions included in a disposition.

To access this page click a disposition name on the Pending Dispositions Page or choose Disposition Information from the Actions menu of a disposition on the Pending Dispositions Page.

A.9.7 Disposition Parameter Dialog

This dialog opens when a disposition action is marked as approved.

This dialog opens when an action is marked for completion on the Pending Dispositions Page. The bottom portion of this dialog is displayed if an action also involves a deletion method.

A.10 Configure Report Settings Page

This page is used to configure reports for retention items, chargebacks, and other functionality.

Permissions:

The Admin.RecordManager right is required to use this page. This right is assigned by default to the Records Administrator role.

To access this page, choose Records then Configure from the Top menu. Choose Reports then Settings.

Element | Description
Template Check In Profile | Profile to use for the template when it is checked in.
Report Check In Profile | Profile to use when the report is checked in.
System Report Format | Default format for reports.
Exclude Report Templates in Search Results | If selected, excludes templates from search activities. This is available for selection only if Enable Report Exclude Search Options is selected on the Configure Retention Settings Page.
Exclude Reports in Search Results | If selected, excludes reports from search activities. This is available for selection only if Enable Report Exclude Search Options is selected on the Configure Retention Settings Page.

A.11 Customization, Monitoring and Audit Pages

These pages are used to add custom scripts, perform performance monitoring, or run audit reports.

Section A.11.1, "Configure Performance Monitoring Page"

Section A.11.2, "Performance Processing Results Page"

Section A.11.3, "Configure Custom Script Page"

Section A.11.4, "Create or Edit Custom Script Page"

Section A.11.5, "Custom Script Information Page"

Section A.11.6, "Configure Audit Page"

Section A.11.7, "Audit Fields Page"

Section A.11.8, "Checked-in Audit Entries Page"

Section A.11.9, "Default Metadata for Checked-In Audit Entries Page"

Section A.11.10, "Search Audit Trail Page"

A.11.1 Configure Performance Monitoring Page

This page is used to set up and use performance monitoring.

To access this page, choose Records then Audit from the Top menu. Choose Configure then Performance Monitoring.

Element | Description
Enable Performance Monitoring | If selected, enables performance monitoring.
Write data to File System First | If selected, enables storage of data before creation of reports. This can speed the process for larger batches of data. If unselected, the data is not saved temporarily before it is compiled into a log file.
Display Time Values In | Format of time value reporting. Options include seconds, minutes, or hours.
Write to Database Table Every | Length of time between writing the performance information to the database.
Query Average Alert (sec) | Average time deemed reasonable for a query. Alerts are issued if the amount exceeds this number.
Validation Average Alert (sec) | Average time deemed reasonable for a validation. Alerts are issued if the amount exceeds this number.
Service Parse Average (sec) | Average time deemed reasonable for a service parse action. Alerts are issued if the amount exceeds this number.
Total Service Average Alert (sec) | Average time deemed reasonable for a service action. Alerts are issued if the amount exceeds this number.
Notify Groups of Alert | Recipients to receive alerts. This list is populated if users and aliases have been added to a My Favorites list. If none are added, click Browse to open a dialog where a user or alias name can be added.
Enable External Batch Monitoring | Begins monitoring of external batch processes.
Failed Batches Alert | Minimum number of batches that can fail before an alert is displayed.
Failed Items Alert | Minimum number of items that can fail in processing before an alert is displayed.
Elapsed Time Alert (sec) | Amount of time that can elapse before an alert is sounded.

A.11.2 Performance Processing Results Page

This page is used to view the results of performance monitoring.

To access this page, choose Records then Audit then Performance Monitoring from the Top menu. This option only appears if performance monitoring has been enabled.

Select any tab to view different data. The default for these pages contains totals for each source and an overall total.

Performance Processing tab: contains a summary of requests processed as well as other information.

Report by Batch tab: contains a summary of batches/items pending and processed with other information.

Report by Item tab: contains the details per batch for a particular source as well as other information.

A.11.3 Configure Custom Script Page

This page is used to configure a security script or a notification script.

To access this page, choose Records then Configure from the Top menu. Choose Security then Custom Scripts. Use this page to configure notification or security scripts. The two types of security creation pages are similar. Only the notification script page is depicted in this documentation.

A.11.4 Create or Edit Custom Script Page

This page is used to enter the Idoc Script needed for a notification or security script or to edit the text of an existing script.

To access this page, click Add on the Configure Custom Script Page. To access the Edit version of this page, choose Edit on the Actions menu of a specific script on that page or use the Delete option on the Edit Page to remove the script.

A.11.5 Custom Script Information Page

The custom script information page shows the content of a custom script.

To access this page, click the script name on the Configure Custom Script Page.

A.11.6 Configure Audit Page

This page is used to determine what will appear on the Audit Page. By default, all options are selected.

Permissions:

The Admin.Audit right is required to use this page. This right is assigned by default to the Records Administrator role.

To access this page, choose Records then Audit from the Top menu. Choose Configure then Audit Trails.

Note:

The Edit Metadata column is only visible if the Log Metadata Changes option is enabled on the Configure Retention Settings Page.

Audited Objects and Elements
Actions Recorded

Series

Category

Folder

Period

Trigger

Custom Direct Trigger

Indirect Trigger

Supplemental Marking

Security Classification

Configuration

Content

Freeze

User Groups

User Accounts

Custom Security Field

Indirect Trigger Data

Related Content Type

Disposition Action

Metadata Set

The actions to be recorded in the current audit trail:

Delete: Records all deletion actions.

Edit: Records all editing actions.

Create: Records all actions during item creation.

Retrieve: Records all items retrieved.

Browse: Records all browsing actions within the retention schedule

Search: Records all searching actions for items. Screening is also captured by the Search action.

Edit Metadata: Records all metadata changes for items, categories, folders, and series. The changed status is recorded and also what the change entails (old and new field values). This column is only visible if the Log Metadata Changes option is enabled on the Configure Retention Settings Page.

The User Accounts column represents users and is not to be confused with the accounts-based security model within Oracle WebCenter Content. The Configure Audit User Accounts option tracks users and not document accounts. The User Groups options tracks users assigned to an alias group.

A.11.7 Audit Fields Page

This page is used to specify which metadata fields should be included in the audit trail.

Permissions:

The Admin.SelectMeta and Admin.Audit rights are required to use this page. Audit.SelectMeta is assigned to the Records Administrator role by default.

To access this page, choose Records then Audit from the Top menu. Choose Configure then Audit Fields. To enable an option, select its checkbox then click Submit Update.

A.11.8 Checked-in Audit Entries Page

This page is used to cut off and check in the audit trail. Archived audit trails can also be searched from this page.

Permissions:

The Admin.Audit and the Admin.RecordsManager right is required to use this page.

To access this page, choose Records then Audit then Checked-In Audit Entries from the Top menu.

Element | Description
Date fields | Date when the audit log will be checked in.
Report Template | Template to use for the checked-in audit log.
Schedule information | Frequency used to schedule a report to be run. Select a range of days and time intervals from the lists. To change a scheduled report, click Reschedule. To remove a report, click Unschedule.
Search information | A beginning date and an ending date for a search of the audit trail.

A.11.9 Default Metadata for Checked-In Audit Entries Page

This screen is used to set the default metadata for checking in archived audit trails.

Permissions:

The Admin.Audit right is required to use this page. This right is assigned by default to the Records Administrator role.

To access this page, choose the Default Metadata for Checked In Audit Entries link on the Checked-in Audit Entries Page.The fields on this page vary according to what is installed at individual sites.

A.11.10 Search Audit Trail Page

This page is used to narrow a search within an audit trail.

Permissions:

The Admin.Audit right is required to use this page. This right is assigned by default to the Records Administrator role.

To access this page, choose Records then Audit then Search Audit Trail from the Top menu.

Search Audit Trail Section
Description

Date
Date or date range used to search the audit trail.

From: Finds actions recorded on or after the From date.

To: Finds actions recorded before but not on the To date.

Click the icon next to each field to choose a date from a calendar.

User
User name to search for in the audit trail. Any actions by the user name that was entered are retrieved in the search audit report. The default is the current user.

Successful
If yes, search is performed for successful actions.

Action
Action used for search. Actions are enabled on the Configure Audit Page.

Type
Type used for search. Types are enabled on the Configure Audit Page.

ID field
Identifier for a series, retention category, record folder, or content item to track. Identifiers of custom periods, custom triggers, supplemental markings, or custom security fields can also be used.

Name
Name of a series, retention category, record folder, or content item to search for in the audit trail. The name of custom periods or triggers, supplemental markings, or custom security fields can also be used.

Details
Keywords containing details to search for in the audit trail. Details tracked include changes to the software configuration, the document ID, the number of results found when searching a folder, and so on.

Comments
A text string used for searching.

The following table discusses sorting options for the audit trail.

Results Options Section
Description

Sort By field
Sorting method (such as by Date or by ID).

Sort By order
Sort order of the search audit results.

Descending (default): Sorts alphabetical results from Z-A, numeric results from 9-0 and date results from newest to oldest.

Ascending: Sorts alphabetical results from A-Z, numeric results from 0-9 and date results from oldest to newest order.

Search
Generates a report in the format specified by the Report Format setting on the Configure Retention Settings Page. If no search criteria is entered, the entire search audit trail is displayed.

A.12 Import/Export Interface Pages

The following page is used when managing the import/export process:

Section A.12.1, "Import/Export Archive Page"

Section A.12.2, "Configure Import/Export Schema Page"

Section A.12.3, "Create Import/Export Schema Page"

Section A.12.4, "Configure Top Level Schema Nodes Page"

Section A.12.5, "Configure Mappings Page"

Section A.12.6, "Import with Schema Page"

Section A.12.7, "Export with Schema Page"

A.12.1 Import/Export Archive Page

This page is used to import or export an archive.

Options on this page are hidden until the plus sign (+) next to the section heading is clicked.

Important:

When using the import/export process, make sure the instance to which you are importing has the same metadata fields, security groups, and accounts as the instance where the export is originating from. Errors can result if there are mismatches.

To access this page, choose Records then Import/Export then Archives from the Top menu.

Note:

When exporting auxiliary metadata, first include additional tables in the Table list in the Configuration Manager applet. See the task documentation in the Oracle WebCenter Content Administrator's Guide for Records for details about this procedure.

Element
Description

Attempt Update
If selected, updates information during the import.

Export Date
Exports only items that changed since a specific date. Enter the start date or select one using the calendar next to the field.

This field is only displayed if Show Export Date on the Configure Retention Settings Page is selected.

Retention Schedule Objects
If selected, include the objects in the archive.

Include Supplemental Markings

Include Classified Markings

Include Custom Categories Metadata

Include Custom Folders Metadata

Include Simple Custom Security

Include Advanced Custom Security

Include Custom Supplemental Markings

Include Periods

Include Triggers

Include Retention Schedule

Include Disposition Actions

Include Freezes

Include Recurring Scheduled Tasks

Include Classification Guides

Include Classification Topics

Physical Related Objects
If selected, objects to include in the archive.

Include Location Types

Include Storage

Include Custom PCM Metadata

Include Charge Types

Include Payment Methods

Include Customers

Include Charge Invoices

Include Charge Transactions

Content Related Objects
If selected, objects to include in the archive.

Include Reservations

Include Dispositions History

If the Show External Sources link is clicked, any external source systems are displayed. Select the appropriate checkboxes to include metadata from the selected source or to include the disposition history from the selected source.

Archive File
A name for the archive file. Click Browse to search for previously created files.

Import or Export
Imports or exports the archive file to a specified location and name.

If an add-on is installed, there may be more items available for export than the ones shown here (for example, items related to external sources).

A.12.2 Configure Import/Export Schema Page

This page is used to choose a schema definition for use or to imitate the addition of a new schema.

To access this page, choose Records then Import/Export from the Top menu. Choose Configure then Import/Export Schema.

Element | Description
Schema Name | Name of the schema to use.
Schema File Name | Archive file name.
Schema Description | Description given for the schema.

A.12.3 Create Import/Export Schema Page

This page is used to add a new schema for importing or exporting.

To access this page, click Add on the Configure Import/Export Schema Page.

Element | Description
Schema Name | The name of the schema to use.
Schema Description | The description given for the schema.
File Encoding | The encoding type used for the schema.
Schema File | The file to be uploaded. Click Browse to choose a file from a list.

A.12.4 Configure Top Level Schema Nodes Page

This page is used to specify nodes for inclusion in the export.

To access this page, choose Configure Top Level Nodes in the Actions menu of an item on the Configure Import/Export Schema Page.

A.12.5 Configure Mappings Page

This page is used to map fields for import and export.

To access this page, choose Map Fields on the Page menu on the Configure Top Level Schema Nodes Page.

A.12.6 Import with Schema Page

This page is used to specify a schema archive for importing.

To access this page, choose Records then Import/Export then Import with Schema from the Top menu.

Element | Description
Schema Name | The name of the schema to import.
Archive File | The archive file to be imported. Click Browse to select a file.
Import All Folders | If selected, all folders are also imported.

A.12.7 Export with Schema Page

This page is used to specify a schema archive for exporting.

To access this page, choose Records then Import/Export then Export with Schema from the Top menu.

Element | Description
Schema Name | Name of the schema to export.
Archive Batch | Archive batch file to be exported.

A.13 FOIA and PA Interface Pages

These pages are used to set up the components needed to process requests for information under the Freedom of Information Act (FOIA) and Privacy Act (PA). This section is divided into two subsections:

Section A.13.1, "FOIA/PA Processing Pages": Screens used during the workflow to process a request.

Section A.13.2, "FOIA/PA Data Pages": Pages depicting forms used to provide supporting documentation for the requests.

This section does not include depictions of those page used to set up the FOIA and PA workflow process. See the Oracle WebCenter Content Application Administrator's Guide for Content Server for details about workflows.

A.13.1 FOIA/PA Processing Pages

The following pages are used to process FOIA requests in workflows:

Section A.13.1.1, "Active Workflows Page"

Section A.13.1.2, "Assignments in Queue Page"

Section A.13.1.3, "Amendment Record Form"

Section A.13.1.4, "Disclosure Request Form"

Section A.13.1.5, "Access Request Form"

Section A.13.1.6, "Request Fee Table"

Section A.13.1.7, "Workflow Content Page"

Section A.13.1.8, "Workflow Review Page"

Section A.13.1.9, "Denial Record Form"

Section A.13.1.10, "Appeal Request Form"

Section A.13.1.11, "Final Result Dialog"

A.13.1.1 Active Workflows Page

This page shows all workflows that are activated. Not all workflows shown here may be in active use.

To access this page, choose Content Management then Active Workflows.

Element | Description
Workflow Name | Activated workflows and sub workflows. This does not imply content is being processed in the workflow, only that the workflow is active and ready to process information.
Description | A description of the workflow, indicating if it is a primary workflow or a sub-workflow.
My Workflow Assignments | A link to the Assignments in Queue Page, listing all current workflow assignments for the logged-in user.

A.13.1.2 Assignments in Queue Page

This page displays all workflow assignments for the logged-in user.

To access this page, choose Content Management then Active Workflows. Click My Workflow Assignments.

Element | Description
Content ID | Content ID of the item in the queue assigned to this user for processing.
Title | Title of the item in the queue.
Last Action | Last action for the content item, usually the name of a workflow step.
Last Action Date | Date and time when the last action was taken.
Enter Date | Date the item entered the current workflow step.
Actions | Actions that can be taken for the item. Click the Workflow Review icon to open the "Workflow Review Page".

A.13.1.3 Amendment Record Form

This form is used to initiate the workflow process for a request for amendment to a record.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Amendment Record Form.

Element
Description

Record Link
Records to be amended. Click Browse to search for the record.

Amendment Justification
Description of the justification given for the amendment.

Amendment Type
Type of amendment:

Deletion: Request for deletion of the record(s).

Correction: Request for correction of information.

Addition: Request for addition of information.

Amendment Request Date
The date the request was received.

Reference Links
Links to record(s) supplied by the requestor as documentary evidence. Click Browse to open a search page to search for the records.

Amendment Resolution
Brief statement of how the amendment request was resolved.

Amendment Resolution Date
Date the request was resolved.

A.13.1.4 Disclosure Request Form

This form is used to initiate a workflow for a disclosure request. Note that this is a Disclosure Request Form, not a Disclosure Record Form.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Disclosure Request Form.

Element | Description
Disclosure Requestor | Contact information for the authorized agent requesting the disclosure.
Disclosure Purpose | Use or purpose for the disclosed information.
Details | Additional details about the requested disclosure.
Disclosure Receipt Date | Date the disclosure request was received.
Individual Consent | Consent form, if required.

A.13.1.5 Access Request Form

This form is used to initiate a workflow to process a request for information.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Access Request Form.

Element
Description

Received Date
Date the request was received.

Requestor's Information
Name, address, phone number, fax number, and e-mail address of the initiator of the request.

Request Type
Type of request:

FOIA Initial

FOIA Referral

FOIA Appeal

If this is a Privacy Act request, the options are:

Privacy Act Review

Privacy Act Dispute

Privacy Act Disclosure Accounting

Access Rule Cited
Title, date, and version of the rule under which the request was made.

Fee Questions
Select Yes or No to indicate if the requestor is willing to pay a processing fee. Required for FOIA requests.

Select Yes or No to indicate if the requestor is requesting a waiver of fees. Required for FOIA requests.

Expedited Processing Requested
Select Yes or No to indicate if the requestor requests expedited processing.

Requestor Category
Required for FOIA requests. Category for the requestor. The category chosen will dictate the fee used, as described in the Request Fee Table:

Commercial

Educational

Non-commercial scientific institutions

News Media

All Others

All Others/Privacy Act

Referring Information
If a referral, information about the referring agency, point of contact, point of contact phone number, and point of contact e-mail address.

File in Folder
The locator links for the current folder.

A.13.1.6 Request Fee Table

This table shows the payments associated with the category of requestor on the Access Request Form.

To access this table, click View Fee Table next to the Requestor Category on the Access Request Form.

A.13.1.7 Workflow Content Page

This page displays items in workflows as well as the stage of the workflow where the item is currently processing.

To access this page, choose Content Management then Active Workflows from the Main menu. This page is also opened whenever an action is taken on the Workflow Review Page.

The Step Name column indicates the stage of the workflow. Note that ExpeditedDecision does not imply that an expedited decision has been requested. It is the name of the stage of the workflow.

A.13.1.8 Workflow Review Page

This page displays the current item in the workflow as well as the Review Workflow Pane, where actions can be taken.

To access this page, click the Workflow Review icon next to an item on the Workflow Content Page. The content of this page varies with the type of request and the stage of the workflow when this page was accessed.

Click Printable View on this page to open a popup message showing the address information for the request. Use this to create a mailing label for acknowledgments and other correspondence.

Links in the Review Workflow pane on the left of the page can be used to initiate actions for the requests. The following links are also available:

The Content Information page for the request item.

The Workflow Information page.

Get Native File, to retrieve the original request.

My Workflow Assignments, which opens the Workflow Assignment Page.

A.13.1.9 Denial Record Form

This form is used to initiate a denial of information to a requestor.

To access this form, choose Recommend Denial - Existing Record or Recommend Denial - New Form on the Workflow Review Pane on the Workflow Review Page.

Element | Description
Denial Authority | Name, title, position, signature or electronic signature of the designated denial authority.
Denial Date | Date the denial was initiated.
Denial Reason | Reason for denial from the list. Choose View Denial Reason Guide for a list of denial reasons and descriptions.
Exemption Category | If an exemption is warranted, select the category from the list. Click View Exemption Reason Guide for a list of exemptions and descriptions.
Exemption Category Summary | If needed, enter a summary of the exemption decision.
Appeal Suspense | Suspense duration for the denial. Currently set at 60 calendar days according to DoD 5015.2 specifications.
Appeals Officer | Name, title, position, signature, or electronic signature of the designated authority.
File in Folder | The locator links for the current folder.

A.13.1.10 Appeal Request Form

This form is used to start an appeal when a FOIA or PA request is denied.

To access this form, choose Appeal Received - New Form in the Review Workflow pane on the Workflow Review Page. Appeals are always linked to denials.

Element
Description

Denial ID
The ID of the record denial being appealed. Click Browse to search for and link to the record. The ID of the request is inserted and this appeal is then associated with it.

Nature of Appeal
Type of appeal:

Review

Dispute

Disclosure Accounting

Details of Appeal
Further details about the appeal.

Appeal Date
Date the appeal was received.

A.13.1.11 Final Result Dialog

This dialog is used to collect request processing information for reports.

This dialog is displayed when a request workflow completes, either after the request is serviced or if the request for information is denied.

Element
Description

Final Result
Appeal result. Options include:

Granted in Full

Denied in Part

Denied in Full

Other Reason

Fees Collected
Decimal amount for fees, excluding the dollar sign.

Staff Allocated
Integer indicating the number of people who were allocated to service the request.

Amount Spent Servicing
Total amount spent to service the request.

A.13.2 FOIA/PA Data Pages

These pages are used to provide details about the requests processed in the Records system. Depending on the type of request, a variety of forms are used. For complete details about these forms and when they are used, see the DoD 5015.2 specification.

The following forms are described here:

Section A.13.2.1, "Access Record Form"

Section A.13.2.2, "Accounting Record Form"

Section A.13.2.3, "Disclosure Record Form"

Section A.13.2.4, "Dispute Record Form"

Section A.13.2.5, "Exemption Record Form"

Section A.13.2.6, "Matching Program Records Form"

Section A.13.2.7, "Privacy Act File"

Section A.13.2.8, "System of Records Form"

A.13.2.1 Access Record Form

This form is used to document the collection of records for an access request.

To access this form, choose Create then FOIA Requests or Privacy Acts Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then choose Access Record Form.

Element
Description

Access Type
How the records are gathered for the request:

In Person

By Authorized Agent

By Mail

By FAX

By E-mail

Via Internet

Access Date
Date the records were accessed:

In person: Date the person visited

By Mail or By FAX: Date the package was sent

By E-mail: Date the e-mail was sent

via Internet: Timestamp on the retrieval

Records Accessed
Records accessed by or provided to the individual.

Record Description
Summary of the record state (original, redacted, summary, etc.)

File in Folder
Locator links for the current folder are displayed.

A.13.2.2 Accounting Record Form

This form is used to track disclosures of information from the System of Records (SOR). This form is linked to disclosures in review.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then Accounting Record Form.

Element | Description
Accounting Review Date | Date the disclosure was reviewed.
Accounting Reviewed By | Name and contact information for the person conducting the review.
Disclosure ID | Disclosure ID. Click Browse to enter metadata for searching or click Search to return all items. Select the checkbox of the item to use for linking then click OK.
Accounting Release Date | Date accounting was released to the individuals involved.
Access Request | Original access request. Click Browse to search for the request.
File in Folder | Locator links for the current folder are displayed.

A.13.2.3 Disclosure Record Form

This form is used to create a record of disclosure.

To access this form, choose Create then FOIA Requests then Disclosure Record Form from the Actions menu of a folder used to store FOIA or PA information. Choose Other then choose Disclosure Record Form.

Element
Description

Disclosure Request
Disclosure ID or NARA transfer identifier or click Browse to search for the ID. Select the checkbox of the item to use for linking then click OK.

Disclosure Date
Date disclosure was made.

Disclosure Description
Description of the information released. This may also include links to the actual records disclosed.

Disclosure Purpose
Reason for the disclosure.

Disclosure Recipient
Recipient of the disclosed records.

Disclosure Recipient Unit
Organization receiving the disclosed records.

Disclosure Notes
Discussion of deletions or changes to the disclosed records. This may include other information that is pertinent to the disclosure.

Preparer
Person responsible for preparing the disclosure.

Released By
Person responsible for releasing the disclosure.

Records Disclosed
Link to the records disclosed. Click Browse to search for items. Select the checkbox of the item to use for linking then click OK.

Dispute Information
Indication if the disclosed information has been corrected or disputed.

Request Type
The type of the request. If a FOIA request or Privacy Act request, click Browse to search for the request.

If used for another type of request (such as court order, subpoena, and so on) indicate that type in the Other Request field.

A.13.2.4 Dispute Record Form

This form is used to add details about disputed records.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then Dispute Record Form.

Element | Description
Disclosure ID | Link to the disclosure record. Click Browse. A search page opens. Enter the metadata for searching or click Search to return all items. Select the checkbox of the item to use for linking then click OK.
Dispute Author | Name of the person initializing the dispute.
Dispute Date Received | Date the organization received the dispute.
Dispute Date Closed | Date of the final action on the dispute.
Nature of Dispute | Summary of the dispute allegations.
Discussion | Discussion of the dispute allegations.
Resolution | Discussion of the final resolution of the dispute.
Statement of Disagreement | Statement prepared by the dispute author.
Civil Action | Civil action arising from the dispute.
Preparer | Person preparing the disclosure or the individual access response that led to the dispute. Required if the dispute is related to a disclosure.
Released By | Person approving the disclosure or the individual access response. Required if the dispute is related to a disclosure.
Request ID | Link to the original access request. Required if the dispute is related to a disclosure or individual access response. Click Browse to search for the request.
File in Folder | Locator links for the current folder.

A.13.2.5 Exemption Record Form

This form is used to detail information about an exemption request.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then Exemption Record Form.

Element | Description
Privacy Act Exemption Reference | Reference in the Privacy Act that allows the exemption.
Privacy Act Text | The text that matches the chosen reference is inserted. Optional text can be added.
General Exemption | Select Yes or No to indicate if this is a general exemption.
Specific Exemption | Select Yes or No to indicate if this is a specific exemption.
File in Folder | Locator links for the current folder.

A.13.2.6 Matching Program Records Form

This form is used to add information about records that will be cross-matched.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then Matching Program Record Form. See the DoD 5015.2 specification for details about this form.

Element | Description
Sibling System Identification | System name or identifier of systems used to cross-match the information.
Sibling System POC | Point of contact for the matching system.
Data Integrity Board | Name of the board verifying the match.
Purpose | Purpose of the matching program.
Notices | Notices associated with this form.
Adverse Actions | Adverse actions associated with this form.
File in Folder | Locator links for the current folder.

A.13.2.7 Privacy Act File

This form is used to create a privacy act case file.

To access this form, choose Create then FOIA Requests then Access Request Form from the Actions menu of a folder used to store FOIA or PA information. Choose Other then Privacy Act File. See the DoD 5015.2 specification for details about this form.

Element | Description
File ID | Privacy act file ID. Enter a maximum of 21 alphanumeric characters.
File Name | File name. Enter a maximum of 55 alphanumeric characters.
File in Folder | Locator links for the current folder.

A.13.2.8 System of Records Form

This page is used to prepare the systems of record (SOR) components.

To access this form, choose Create then FOIA Requests or Privacy Act Requests from the Actions menu of a folder used to store FOIA or PA information. Choose Other then System of Records Form. See the DoD 5015.2 specification for details about the sections of the specification pertaining to this form.

Element | Description
System Identification | ID of system used. Enter a maximum of 21 alphanumeric characters.
System Name | Name of the system used. Enter a maximum of 55 alphanumeric characters.
Responsible Official | Title and business address of the responsible agency official.
System Location | Addresses of each location where the system or segment of the system is maintained. Classified addresses are not listed but the classification of a system should be noted.
Category of Individuals | Description of the specific categories of individuals to whom the records pertain.
Category of Records | Descriptions of the types of records maintained in the system.
Authority | Links to authority records.
Routine Uses | Description about how the information will be used. Examples include Law Enforcement, Taxing Authorities, or Congressional Inquiry. See the DoD 5015.2 specification for more details.
Rules | Documentation providing the access rules. Click Browse to search for documentation.
NID | Notice identifier.
NType | Notice type. Options include New, Alteration, Amendment or Deletion.
NPosting | Date and volume of the Federal Register.
NDate | Date the notice was published in the Federal Register.
NComments | Comments about unique circumstances of this notice.
Preparer | Author or preparer of the System of Record Notification (SORN).
Released By | Person responsible for ensuring the publication of the SORN.
Purpose of System | Discussion of the system purpose. This is required for new systems.
Nature of Last Change | Discussion of changes to the purpose or use of the system. This includes deletions. This is required for altered systems.
Exemptions | Section reference of the exemption. Required if exemptions apply. See the DoD 5015.2 specification for details about exemptions regarding classifications.
Matching Programs | Links to matching program records or descriptions. This is required if SOR participates in one or more matching programs. Click Browse to search for records.
Notices | Links to or from notices about this SOR. Click Browse to search for notices.
Information Collection | ID or Links to form(s) used to collect the personal information stored in the system.
Failure to Provide Notice | Description of the reason for a failure to provide notice.
File in Folder | Locator links for the current folder.

A.14 Federated Search and Freeze Pages

The following pages are used when performing Federated searches and freezes.

Section A.14.1.1, "Federated Query Builder Page"

Section A.14.1.2, "Federated Searches List Page"

Section A.14.1.3, "Federated Search Details Page"

Section A.14.1.4, "Federated Search Results Page"

A.14.1 Federated Search Pages

The following pages are used to schedule Federated searches.

Section A.14.1.1, "Federated Query Builder Page"

Section A.14.1.2, "Federated Searches List Page"

Section A.14.1.3, "Federated Search Details Page"

A.14.1.1 Federated Query Builder Page

This page is used to build a query for a Federated search.

To access this page, choose Search then Global Search from the Top menu. Choose the type of search to perform. A similar page is used for all three types of searches: Central Catalog, Remote Repository, and SES Search.

When using a Remote Repository search, an Include Content checkbox is available, used to retrieve copies of the content that match the search criteria. Do not select this box unless search results are certain. Returning a copy of the data takes a long time and uses space. Fine tune the query first and verify what items will be returned before actually retrieving the content.

Click the Federated Searches List link to see a list of a previously scheduled searches.

Element
Description

External Sources
Repositories to be used in the search.

Searches are not performed immediately. If an external repository has been chosen, the adapter schedules the search using its previously established configuration parameters.

If local repositories on the Records system server are chosen in this field, they are searched during regularly scheduled search batches, scheduled by default for midnight.

Search Builder
Fields available for searching. The fields displayed are those in use on the Records system server. These fields should be mapped to those on remote repositories in order to assure correct retrieval.

When a field is selected, additional search options appear, allowing a user to match the field to a specific value.

See the Oracle WebCenter Content User's Guide for Content Server for details about using the Query Builder tool.

Full-text Search
Area used to enter terms for searching. Not all remote repositories will be configured for full-text searching. If using this option, make sure the repositories selected for searching allow this type of search.

Search Name
Name for the search. Federated Searches are performed by adapters and thus conform to an adapter schedule. A meaningful search name helps track the progress of the search.

Results section
Number of results per page. Default: 20.

Sort By attribute list
One or more attributes used to sort the results. The list contains all of the screening criteria options.

Sort order list
Sort order of the screening results:

Descending: (default) Sorts alphabetical results in Z-A order, numeric results in 9-0 order and date results in newest to oldest order.

Ascending: Sorts alphabetical results in A-Z order, numeric results in 0-9 order, and date results in oldest to newest order.

Save
Prompts the user to save the query under a query name. Once saved, the query is available in the My Saved Query section of the My Content Server menu.

A.14.1.2 Federated Searches List Page

This page displays a list of all scheduled searches and their progress.

To access this page, choose Federated Searches List from the Federated Query Builder Page or by choosing Records then Scheduled then Federated Searches.

Element | Description
Search Task ID | Assigned ID for the scheduled search.
Search Task Name | Name given to the search on the Federated Query Builder Page.
Sources | Number of sources chosen for the search.

A.14.1.3 Federated Search Details Page

This page shows the details of a scheduled search.

To access this page, choose Show Search Details from the Actions menu of a search on the Federated Searches List Page.

A.14.1.4 Federated Search Results Page

This page shows the results of a search.

To access this page, choose Show Search Results from the Actions menu of a search on the Federated Searches List Page.

Index

A  B  C  D  E  F  G  H  I  J  L  M  N  O  P  Q  R  S  T  U  V  W 

Numerics

3of9 barcoding, 7.3

A

accented letters and barcodes, 7.3

Access Record Form, A.13.2.1

Access Request Form, A.13.1.5

accession events, 10.3.1

Accounting Record Form, A.13.2.2

actions for request items

Cancel, 7.2.1.4

Check Out, 7.2.1.4

Delete, 7.2.1.4

Deny, 7.2.1.4

Not Found, 7.2.1.4

Returned, 7.2.1.4

Unavailable, 7.2.1.4

actions in barcode files, 7.3.1.1

Activate (disposition action), 10.3.2

Active Workflows Page, A.13.1.1

AllowMultipleRequests parameter, 7.1

alternate reviewer, 10.1.6

Amendment Record Form, A.13.1.3

Appeal Request Form, A.13.1.10

approval, 10.1.2, 10.1.2

Approve Deletion (disposition action), 10.3.2

approve deletion events, 10.3.2.1

archive events, 10.3.1

archived audit trail

searching an, 12.3.6

viewing, 12.3.7

archives

exporting, 13.2.1

importing, 13.2.2

importing --, 13.2.3

overview, 13.1

archiving audit trail, 12.3.5

archiving metadata sets, 13.1.1

ASAP Rush (priority), 7.2.1.3

Assignments in Queue Page, A.13.1.2

Audit Fields Page, A.11.7

audit logs for processed events, 6.3.4

audit trail, 6.3.4, 13.2.3

archiving, 12.3.5

checking in, 12.3.5

configuring, 12.3

overview, 12.3

searching an archived, 12.3.6

searching within, 12.3.3

specifying metadata fields to audit, 12.3.2

viewing an archived, 12.3.7

auxiliary metadata sets

exporting, 13.1.1

B

barcode actions

Check In, 7.3.1.1.1

Check Out, 7.3.1.1.2

Set Home & Actual, 7.3.1.1.3

barcode data

saving -- to file, 7.4.3

uploading -- to PCM, 7.4.2

Barcode File Processed Page, A.5.7

barcode files, 7.3.1

saving data to --, 7.4.3

uploading -- to PCM directly, 7.4.2

Barcode Processing Page, A.5.6

barcode scanner

programming --, 7.4.1

Barcode Upload Results screen, A.5.4

Barcode Upload screen, A.5.2

Barcode Utility

installing --, 7.3

saving barcode data to file, 7.4.3

saving barcode to file, 7.4.3

starting --, 7.3

tasks, 7.4

uploading barcode data to PCM, 7.4.2, 7.4.4

uploading data to PCM directly, 7.4.2

uploading data to PCM manually, 7.4.4

user interface, A.5

Barcode Utility screen, A.5.1

barcodes

accented letters, 7.3

actions, 7.3.1.1

Code 3 of 9, 7.3

double-byte characters, 7.3

lower-case letters, 7.3

processing barcode files, 7.4.5

saving barcode data to file, 7.4.3

standard used by PCM, 7.3

uploading data to PCM, 7.4.2, 7.4.4

basic concepts, 2.2

retention schedules, 2.2

basic processes, 2.5

batch processing, 10.1.5

batch services, 10.1.5

Browse Processed History Page, A.6.5

Browse Uploaded Files Page, A.6.4

C

Cancel (request item action), 7.2.1.4

canceling

content, 5.1.2.3

content items, 5.1.2.3

Cancelled (request status), 7.2.1.1

categories

definition, 2.2

Check In (barcode action), 7.3.1.1.1

Check Out (barcode action), 7.3.1.1.2

Check Out (request item action), 7.2.1.4

Checked Out (request status), 7.2.1.1

Checked-In Audit Entries Page, A.11.8

checked-out items, location of --, 7.2.1.1, 7.2.1.4

Checkin New Revision (disposition action), 10.3.2

checking in audit trail, 12.3.5

Choose District Mapping Page, A.6.2.1

classification

definition, 2.2

classification guide

definition, 2.2

classified content, 2.1.3.2

classified metadata history, 5.1.1.4

Close (disposition action), 10.3.2

Code 3 of 9 barcoding, 7.3

completed reservation requests, 7.1.1, 7.2.1.1

completion, 10.1.2

configuration

audit trail, 12.3

exporting, 13.2.1

importing -- settings and data, 13.2.3

metadata field to audit, 12.3.2

configuration variables

AllowMultipleRequests, 7.1

Configure Audit Page, A.11.6

Configure Custom Script Page, A.11.3

Configure Host List screen, A.5.3

Configure Import/Export Schema Page, A.12.2

Configure Mappings Page, A.12.5

Configure Performance Monitoring Page, A.11.1

Configure Physical Content Management Page, A.2, A.2

Configure Report Settings Page, A.10

Configure Retention Settings Page, A.1

Configure Top Level Schema Nodes Page, A.12.4

Container Details link, A.2.1

content

classified, 2.1.3.2

declassified, 2.1.3.2

downgrading classification of, 5.2.2

expiring, 5.1.2.3

external, 2.1.3.1, 2.1.3.1

internal, 2.1.3.1, 2.1.3.1

life cycle, 2.1.2

making obsolete, 5.1.2.4

marking as reviewed, 5.1.3

moving, 5.1.4.1

overview, 2.1

recent reviews, 5.1.1.2

review history, 5.1.1.2

subject to review, 10.1.1

unclassified, 2.1.3.2

unfreezing, 5.1.2.2

upgrading classification of, 5.2.2

content information, 5.1.1

content information page, 5.1.1

content items

assigning disposition schedule to, 5.1.4.3

cancelling, 5.1.2.3

deleting, 5.1.4.2

freezing, 5.1.2.2

subject to review, 2.1.3.3

unfreezing, 5.1.2.2

viewing information about, 5.1.1

viewing the life cycle of, 5.1.1.1

content link

definition, 2.2

Copy (transfer method), 7.2.1.2

Create Import/Export Schema Page, A.12.3

Create Manual Pickup Page, A.6.3

Create or Edit Custom Script Page, A.11.4

creating

physical item labels, 6.1.3

current location

of checked-out items, 7.2.1.1, 7.2.1.4

Custom Script Information Page, A.11.5

cutoff, 2.1.2

Cutoff (disposition action), 10.3.2

Cutoff and Create Volume, 10.3.2

D

declassified content, 2.1.3.2

Declassify (disposition action), 10.3.2

Declassify Page, A.4.3

declassifying content, 5.2.3

Default Metadata for Audit Entries, A.11.9

default reports

creating, 11.3.1

Define Query Page, A.3.1, A.3.1

definition

classification, 2.2

classification guide, 2.2

content link, 2.2

disposition, 2.2

disposition instruction, 2.2

freeze, 2.2

record folder, 2.2

retention category, 2.2

series, 2.2

time period, 2.2

trigger, 2.2

Delete (request item action), 7.2.1.4

Delete All Revisions (disposition action), 10.3.2

Delete Old Revisions (disposition action), 10.3.2

Delete Previous Revision (disposition action), 10.3.2

Delete Revision (disposition action), 10.3.2

deleting, 5.1.4.2

content items, 5.1.4.2

metadata history, 5.1.2.1

physical items, 6.1.1

Deliver To Location field, 7.2.1.1

Denial Record Form, A.13.1.9

Denied (request status), 7.2.1.1

Deny (request item action), 7.2.1.4

Disclosure Record Form, A.13.2.3

Disclosure Request Form, A.13.1.4

disposition

assigning schedule to content, 5.1.4.3

definition, 2.2

event-based, 2.5

time-based, 2.5

time-event, 2.5

disposition actions, 6.3.2

Activate, 10.3.2

Approve Deletion, 10.3.2

Checkin New Revision, 10.3.2

Close, 10.3.2

Cutoff, 10.3.2

Cutoff and Create Volume, 10.3.2

Declassify, 10.3.2

Delete All Revisions, 10.3.2

Delete Old Revisions, 10.3.2

Delete Previous Revision, 10.3.2

Delete Revision, 10.3.2

Downgrade Classification, 10.3.2

Expire, 10.3.2

log files for processed, 6.3.4

Mark Related Content, 10.3.2

No Action, 10.3.2

Notify Authors, 10.3.2

Obsolete, 10.3.2

Review Classification, 10.3.2

Supersede, 10.3.2

Upgrade Classification, 10.3.2

disposition events for physical items, 6.3.2

Disposition Information Page, A.9.6

disposition instruction

definition, 2.2

disposition of physical items, 6.3.1

Disposition Parameter Dialog, A.9.7

disposition processing

approval, 10.3.1.1

completion, 10.3.1.2

destroy, 10.3.1

single step, 10.3.2

Dispute Record Form, A.13.2.4

District Mapping Pages, A.6.2

documentation, 1.4

double-byte characters and barcodes, 7.3

Downgrade Classification (disposition action), 10.3.2

downgrading classification of content, 5.2.2

E

Edit Job Information Page, A.8.3

Edit Recurring Report Schedule Page, A.8.5

Edit Review Information Page, A.7.1

E-mail (transfer method), 7.2.1.2

enabling

user-friendly caption for screening, 4.1.1

event dispositions, 2.5

event processing

accession, 10.3.1

archive, 10.3.1

event processing, audit logging of --, 6.3.4

events

approve deletion, 10.3.2.1

destroy, 10.3.1

processing pending, 10.2.6

Exemption Record Form, A.13.2.5

Expire (disposition action), 10.3.2

expiring

content, 5.1.2.3

Export with Schema Page, A.12.7

exporting archives, 13.2.1

exporting configuration settings, 13.2.1

external content, 2.1.3.1, 2.1.3.1

external items, 2.2

F

Failed Disposition Page, A.9.3

failed dispositions

viewing, 10.2.2

Fax (transfer method), 7.2.1.2

features of Physical Content Management, 2.3

Federated Freeze, 15.3

freezing search results, 15.3.1

viewing, 15.3.2

Federated Query Builder Page, A.14.1.1

Federated Search, 15.1.1

overview, 15.1

query builder, 15.1.1

Federated Search Details Page, A.14.1.3

Federated Search Results Page, A.14.1.4

Federated Searches List Page, A.14.1.2

filing date, 2.1.2

Final Result Dialog, A.13.1.11

FOIA, 14

and DB2 databases, 14.1

workflow overview, 14.2

FOIA/PA

Access Record Form, A.13.2.1

Access Request Form, A.13.1.5

Accounting Record Form, A.13.2.2

Active Workflows Page, A.13.1.1

Amendment Record Form, A.13.1.3

Appeal Request Form, A.13.1.10

Assignments in Queue Page, A.13.1.2

Denial Record Form, A.13.1.9

Disclosure Record Form, A.13.2.3

Disclosure Request Form, A.13.1.4

Dispute Record Form, A.13.2.4

Exemption Record Form, A.13.2.5

Final Result Dialog, A.13.1.11

Matching Program Records Form, A.13.2.6

Privacy Act File, A.13.2.7

Request Fee Table, A.13.1.6

System of Records Form, A.13.2.8

Workflow Content Page, A.13.1.7

Workflow Review Page, A.13.1.8

FOIA/PA workflow

acknowledge appeal, 14.3.7.2

acknowledge request, 14.3.4.2

create request, 14.3.3.2

create request folder, 14.3.3.1

denial approval, 14.3.6.2

denial decision, 14.3.6

denial refusal, 14.3.6.1

deny request, 14.3.5.2

details, 14.3.1

expedited vs. non-expedited, 14.3.4

initiate appeal, 14.3.7.1

move folder, 14.3.8

overview, 14.3

processing time limits, 14.3.1

review appeal, 14.3.7.3

review request, 14.3.4.1

service request, 14.3.5.1

setup, 14.3.2

folders

definition, 2.2

Freedom of Information Act, 14

freeze

definition, 2.2

freezes

event processing, 10.1.3

recurring, 9.2.4

scheduling, 9.2.4

unscheduling, 9.2.4

freezing

content items, 5.1.2.2

physical items, 6.1.2

frozen items, 10.1.3

G

group reports, 11.2.4

group-user reports, 11.2.5

H

history of reservations, 7.1.1

I

Import with Schema Page, A.12.6

Import/Export Archive Page, A.12.1

importing archives, 13.2.2

importing configuration settings, 13.2.2

importing PCM data, 6.2

file format, 6.2.1

importing PCM settings and data, 13.2.3

In Process (request status), 7.2.1.1

installation

Barcode Utility, 7.3

interface

Audit Fields Page, A.11.7

Barcode File Processed Page, A.5.7

Barcode Processing Page, A.5.6

Barcode Upload Results screen, A.5.4

Barcode Upload screen, A.5.2

Barcode Utility Screen, A.5.1

Browse Processed History Page, A.6.5

Browse Uploaded Files Page, A.6.4

Checked-In Audit Entries Page, A.11.8

Choose District Mapping Page, A.6.2.1

Configure Audit Page, A.11.6

Configure Custom Script Page, A.11.3

Configure Host List screen, A.5.3

Configure Import/Export Schema Page, A.12.2

Configure Mappings Page, A.12.5

Configure Performance Monitoring Page, A.11.1

Configure Report Settings Page, A.10

Configure Retention Settings Page, A.1

Configure Top Level Schema Nodes Page, A.12.4

Create Import/Export Schema Page, A.12.3

Create Manual Pickup Page, A.6.3

Create or Edit Custom Script Page, A.11.4

Custom Script Information Page, A.11.5

Declassify Page, A.4.3

Default Metadata for Audit Entries, A.11.9

Disposition Information Page, A.9.6

Disposition Parameter Dialog, A.9.7

District Mapping Pages, A.6.2

Edit Job Information Page, A.8.3

Edit Recurring Report Schedule Page, A.8.5

Edit Review Information Page, A.7.1

Export with Schema Page, A.12.7

Failed Disposition Page, A.9.3

Federated Query Builder Page, A.14.1.1

Federated Search Details Page, A.14.1.3

Federated Search Results Page, A.14.1.4

Federated Searches List Page, A.14.1.2

Import with Schema Page, A.12.6

Import/Export Archive Page, A.12.1

Job Information Page, A.8.3

Map Metadata Pages, A.6.2.2

Offsite Storage General Setup Page, A.6.1

Pending Disposition Page, A.9.4

Pending Reviews Page, A.9.5

Performance Monitoring Results Page, A.11.2

Physical Item Information Page, A.2.1

Program Videx Barcode Wand screen, A.5.5

Review Classification Page, A.4.1

Schedule Retention Step Audit Report Page, A.9.2

Scheduled Freezes Page, A.8.4

Scheduled Jobs Listing Page, A.8.6

Scheduled Screening Reports Page, A.8.1

Scheduled Update Page, A.3.3

Search Audit Trail Page, A.11.10

Update Preview Page, A.3.4

Upgrade or Downgrade Classification Page, A.4.2

View History Page, A.8.2

internal content, 2.1.3.1, 2.1.3.1

Internal Item Detail Report, 11.3.2

Iron Mountain, 8.1

J

Job Information Page, A.8.3

L

labels

creating physical item labels, 6.1.3

LaserLite barcode scanner, 7.4.1

layouts supported, 2.4

layouts supported in product, 2.4

life cycle

content items, 5.1.1.1

life cycle of physical items, 6.3.1

lifecycle of retained content, 2.1.2

location of checked-out items, 7.2.1.1, 7.2.1.1, 7.2.1.4

log files for processed disposition events, 6.3.4

lower-case letters and barcodes, 7.3

M

Mail (transfer method), 7.2.1.2

making obsolete

content, 5.1.2.4

managing

physical items, 6.1

Map Metadata Pages, A.6.2.2

marking as reviewed

content, 5.1.3

Matching Program Records Form, A.13.2.6

metadata history, 5.1.1.3

items, 5.1.2.1

moving

content, 5.1.4.1

multi-stage dispositions, 10.3.1

N

new features, 1.3

No Action (disposition action), 10.3.2

No Priority (priority), 7.2.1.3

non-permanent item, 2.1.3.3

Not Found (request item action), 7.2.1.4

Not Found (request status), 7.2.1.1

Notify Authors (disposition action), 10.3.2

O

Obsolete (disposition action), 10.3.2

offsite storage

default information, 8.2.1

file transfer, 8.2.6

manual pickups, 8.2.3

mapping districts, 8.2.2

processed files, 8.2.5

uploaded files, 8.2.4

Offsite Storage General Setup Page, A.6.1

Overdue (request status), 7.2.1.1

overview, 2.2

P

PA, 14

pending approvals, 10.2.6.3

Pending Dispositions Page, A.9.4

pending events, 10.2.6

pending review, 10.2.6.4

Pending Reviews Page, A.9.5

performance alert details, 12.1.3

performance alerts, 12.1.3

Performance Monitoring Results Page, A.11.2

permanent items, 2.1.3.3

Physical Content Management

features, 2.3

overview, 2.3

Physical Content Manager

importing settings and data, 13.2.3

uploading barcode data to --, 7.4.2, 7.4.4

Physical Item Information Page, A.2.1

physical item labels

creating --, 6.1.3

physical items

creating --, 6.1

deleting --, 6.1.1

disposition, 6.3.1

disposition actions, 6.3.2

disposition events, 6.3.2

freezing --, 6.1.2

life cycle, 6.3.1

printing labels for --, 6.1.3

retention assignments, 6.3.3

retention schedules, 6.3.1

unfreezing --, 6.1.2

Pickup (transfer method), 7.2.1.2

priority, 7.2.1.3

ASAP Rush, 7.2.1.3

No Priority, 7.2.1.3

This Morning, 7.2.1.3

This Week, 7.2.1.3

Today, 7.2.1.3

Privacy Act, 14

Privacy Act File, A.13.2.7

process for reservations, 7.2

processing

batch or scheduled, 10.1.5

processing barcode files, 7.4.5

processing events, 10.1.2

approve deletion, 10.3.2.1

completion, 10.1.2

frozen items, 10.1.3

scheduling, 10.1.5

product

documentation, 1.4

product overview, 2.2

product processes, 2.5

Program Videx Barcode Wand Screen, A.5.5

programming the barcode scanner, 7.4.1

Q

Query Schedule Section, A.3.2

R

Records Destruction Certificate Report, 11.3.4

recurring screening reports

definition, 9.2.2

history, 9.2.3

schedule, 9.2.3

reports

audit trail, 12.3

group, 11.2.4

group-user, 11.2.5

role, 11.2.3

user, 11.2.1, 11.2.2

Request Fee Table, A.13.1.6

request item actions, see 'actions for request items'

request status, 7.2.1.1

Cancelled, 7.2.1.1

Checked Out, 7.2.1.1

Denied, 7.2.1.1

In Process, 7.2.1.1

Not Found, 7.2.1.1

Overdue, 7.2.1.1

Returned, 7.2.1.1

Unavailable, 7.2.1.1

Waiting List, 7.2.1.1

reservation requests

properties, 7.2.1

reservations, 7

completed --, 7.1.1

history, 7.1.1

overview, 7.1, 7.1

priority, 7.2.1.3

process, 7.2

properties, 7.2.1

request status, 7.2.1.1

transfer method, 7.2.1.2

retention assignments, 10.1

retention assignments for physical items, 6.3.3

retention assignments, see 'processing events' retention assignments, A.9

retention schedule, 2.2

retention schedules for physical items, 6.3.1

Retention Step Search Page, A.9.1

retention steps

overview, 10.1.4

screening, 10.2.1

Returned (request item action), 7.2.1.4

Returned (request status), 7.2.1.1

Review Classification (disposition action), 10.3.2

Review Classification Page, A.4.1

review history

content, 5.1.1.2

review information

editing, 10.2.5

reviewer, alternate, 10.1.6

reviewing

classification, 5.2.1

content, 5.1.3, 5.1.3

reviewing classification, 5.2.1

reviews, 10.2.4

reviews, performing, 10.2.4

role reports, 11.2.3

running updates, 4.2.1

S

saving barcode data to a file, 7.4.3, 7.4.3

schedule freeze inclusion, 9.2.4

Schedule Retention Step Audit Report Page, A.9.2

Scheduled Freezes Page, A.8.4

Scheduled Jobs Listing Page, A.8.6

scheduled screening reports

start date, A.9.2

Scheduled Screening Reports Page, A.8.1

Scheduled Update Page, A.3.3

scheduling, 10.1.5

changes from 10g, 9.1.1

screening reports, 9.2.1

scheduling updates, 4.2.1

screening

overview, 4.1

user-friendly captions, 4.1.1

screening reports

scheduling, 9.2.1

screening retention steps, 10.2.1

Search and Update, 4.2.1

Search Audit Trail Page, A.11.10

Search Results Report, 11.3.3

search templates, 2.4

search templates supported in product, 2.4

searching an archived audit trail, 12.3.6

searching within audit trail, 12.3.3

security classifications

declassifying, 5.2.3

downgrading of content, 5.2.2

reviewing, 5.2.1

upgrading, 5.2.2

series

definition, 2.2

Set Home & Actual (barcode action), 7.3.1.1.3

space management, see 'storage space'

start date

scheduled screening reports, A.9.2

starting

Barcode Utility, 7.3

status of request items, 7.2.1.1

subject to review content, 10.1.1

subject to review items, 2.1.3.3

Supersede (disposition action), 10.3.2

System of Records Form, A.13.2.8

T

This Morning (priority), 7.2.1.3

This Week (priority), 7.2.1.3

time dispositions, 2.5

time period

definition, 2.2

time-event dispositions, 2.5

Today (priority), 7.2.1.3

transfer method, 7.2.1.2

Copy, 7.2.1.2

Email, 7.2.1.2

Fax, 7.2.1.2

Mail, 7.2.1.2

Pickup, 7.2.1.2

trigger

definition, 2.2

types of content, 2.1.3

U

Unavailable (request item action), 7.2.1.4

Unavailable (request status), 7.2.1.1

unclassified content, 2.1.3.2

undoing cutoff, 5.2.4

unfreezing

content items, 5.1.2.2

unfreezing physical items, 6.1.2

Update Preview Page, A.3.4

updating information, 4.2.1

Upgrade Classification (disposition action), 10.3.2

Upgrade or Downgrade Classification Page, A.4.2

uploading barcode data to PCM, 7.4.2, 7.4.4

directly, 7.4.2

manually, 7.4.4

user reports, 11.2.1, 11.2.2

user-friendly captions

screening, 4.1.1

V

variables

AllowMultipleRequests, 7.1

Videx LaserLite barcode scanner, 7.4.1

View History Page, A.8.2

viewing an archived audit trail, 12.3.7

viewing classified metadata history, 5.1.1.4

viewing failed dispositions, 10.2.2

viewing information

content items, 5.1.1

viewing information about actions, 10.2.3

viewing life cycle

content items, 5.1.1.1

viewing metadata history, 5.1.1.3

viewing pending actions, 10.2.3

viewing pending reviews, 10.2.3

viewing review history

content, 5.1.1.2

viewing scheduled jobs, 9.2.5

W

Waiting List (request status), 7.2.1.1

Workflow Content Page, A.13.1.7

Workflow Review Page, A.13.1.8

workflow steps, 14.2

workflow types, 14.2

This workflow diagram shows the branching points if a denial is approved, in which case an appeal can be filed, or if a denial is refused, in which case the request is serviced. If a denial is approved and no appeal is filed, the workflow is exited and no action is taken.

This flowchart shows the acknowledgement step followed by a decision point of service or denial of service. Branches indicate steps taken to either deny the request or service the request.

This image depicts a life cycle by showing a horizontal bar with "Filing Date" on the far left of the image, "Cutoff" in the middle, and "Destruction?" on the far right. The length of time is indicated by an arrow going from left to right above the horizontal bar showing the life cycle of the process.

This image depicts a workflow indicating that an acknowlegement is sent followed by servicing of the request.

This flowchart shows that an appeal was received and acknowledged. If the appeal if approved, the request is serviced. If the appeal is not approved, the workflow is exited and no action is taken.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2010, Oracle and/or its affiliates. All rights reserved.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Hazardous Applications Notice

This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.

Trademark Notice

Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Third-Party Content, Products, and Services Disclaimer

This software and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.