10-2 Oracle Fusion Middleware Administrators Guide for Universal Records Management
■
Frozen Items and Event Processing on page 10-3
■
Searching Retention Steps and Actions on page 10-3
■
Using Batch Processing on page 10-3
■
Specifying an Alternate Reviewer on page 10-3
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, content 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.
Content that is 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 click Records then Approvals from the Top menu. Click Pending Reviews
.
If you are a member of the RmaReviewers alias, click List All on the Table menu on the page. This shows all items awaiting review and the person assigned to do those
reviews. Click 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 dispostions 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. See
Multi-Step Disposition Processing
on page 10-9 for details.
To view items awaiting disposition click Records then Approvals from the Top menu. Click Pending Dispositions. To also access pending dispositions click My Content
Server
then My Records Assignments from the Main menu.
Processing Retention Assignments 10-3
10.1.3 Frozen Items and Event Processing
