Managing Physical Content 6-7
Include any custom fields or other fields required for import.
6.3.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=60109 5:00 PM
blDateFormat={ts yyyy-MM-dd HH:mm:ss{.SSS}[Z]}tAmericaChicago 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
hasCustomRightsecm.pcm.physical.read Service
EXPORT_EXTERNAL_ITEMS dSource,Physical
6-8 Oracle Fusion Middleware Administrators Guide for Universal Records Management
hasCustomRightsecm.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
Managing Physical Content 6-9
6.4 Processing Physical Content
This section explains how to process physical items used by PCM. It discusses the following topics:
■
Retention Schedules for Physical Items on page 6-9
■
Disposition Events for Physical Items on page 6-9
■
Pending Options for Physical Items on page 6-10
■
Audit Log Files for Processed Events on page 6-10
6.4.1 Retention Schedules for Physical Items
Physical items can be assigned retention schedules which 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.4.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:
1.
Approving the event
2.
Performing the actions associated with the event such as physical destruction of the affected items.
3.
Marking the event as completed.
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 Fusion
Middleware Setup Guide for Universal Records Management.
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:
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.
Kategori