Delete Update About Batch Loading

3-16 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server ■ Second record: dDocName=HR003 dDocTitle=Performance Review primaryFile=hr003.doc dIndate=31597 EOD

3.6.1.4 Delete

The delete action deletes one or all revisions of an existing file from the Oracle Content Server repository. If the specified Content ID dDocName does not exist in the Oracle Content Server database, no action is performed. Figure 3–2 illustrates the delete action. Figure 3–2 The Delete Action Sequence Managing System Processes 3-17

3.6.1.4.1 Delete Requirements The following table defines the fields required for

successful performance of a delete action.

3.6.1.4.2 Delete Example The following example shows the batch load file syntax for

deleting files. This example shows two file records. The first file record will delete all revisions of the Content ID HR001. The second file record will delete revision 2 of the content item HR002. Action=delete dDocName=HR001 EOD Action=delete dDocName=HR002 dRevLabel=2 EOD

3.6.1.5 Update

The update action updates existing content items. One of the following actions occurs, depending on what items are present in the file record and what content exists in the system: ■ A new revision of an existing content item is created. ■ An existing files metadata is updated. ■ A new content item is inserted Action=insert is performed. A new revision is created when one of the following scenarios occur: Required Items Definition Action=delete The command to delete a file. The term Action is case sensitive and must be initial capitalized. dDocName The metadata field named Content ID. EOD Indicates the end of data for the file record. Note: Batch loaded revisions will not enter a workflow even if they meet the criteria for an active workflow. Scenario Content ID dDocName Revision dRevLabel Release Date in Batch Load file dInDate Scenario 1 Exists in Oracle Content Server instance Not specified in the batch load file. After the release date of the latest revision of the file in the system. Scenario 2 Exists in Oracle Content Server instance Specified in the batch load file, but does not exist in the Oracle Content Server instance. After the release date of the latest revision of the file in the system. 3-18 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server Figure 3–3 The Update Action Sequence

3.6.1.5.1 Update Requirements The following table defines the fields required for

successful performance of an update action. Required Items Field Lengt h Carrie d Over Definition Action=update NA Yes The command to update a file. The term Action is case sensitive and must be initial capitalized. dDocName 30 No The metadata field named Content ID. dDocType 30 Yes The metadata field named Type. dDocTitle 80 No The metadata field named Title. dDocAuthor 30 Yes The metadata field named Author. dSecurityGroup 30 Yes The metadata field named Security Group. Managing System Processes 3-19

3.6.1.5.2 Update Example 1 This example assumes that two files are already checked

into the system with the following metadata: ■ HR001 has a Release Date of 92698 and Revision of 1 ■ HR002 has a Release Date of 31599 and Revision of 2 The first file record, Content ID HR001, exists in the system, but it does not have a Revision dRevLabel specified in the batch load file. Therefore, the Batch Loader will compare the Release Date of the latest revision in the system with the Release Date specified in the batch load file. Since 22099 is after 92698, a new revision 2 for HR001 is added. The second file record, Content ID HR002, exists in the system and has a Revision dRevLabel specified, but Revision 3 does not exist in the system. Therefore, a new revision 3 for HR002 is added. Action=update dDocName=HR001 dDocType=Form dDocTitle=New Employee Form dDocAuthor=Olson dSecurityGroup=Public primaryFile=hr001.doc DInDate=22099 primaryFile NA NA The metadata field named Primary File. If only the metadata is being updated, the primaryFile field is not required but dRevLabel is required. If the optional dRevLabel field is specified and matches a revision label that exists in the Oracle Content Server instance, the primaryFile field is not required; the primary file specified for that revision is used. It is important to note that although dRevLabel is not a required field, if the primaryFile is not present, then dRevLabel becomes a required field. The Primary File name can be a complete path or just the file name. If a file name only is specified, the location of the file is determined as follows: ■ If the SetFileDir optional parameter has been set in this file record or any previous file record, the directory specified in SetFileDir will be used. ■ If the SetFileDir parameter has not been set, the batch load file path is used. The path is specified in the Batch Load File field on the Batch Loader Screen . dInDate NA No The metadata field named Release Date. ■ The dInDate must use the date format of the locale of the user executing the Batch Loader. For example, the US English date format is mmddyy hh:mm:ss ampm. ■ Time information is optional. If you specify the time, only the hh:mm part is required. The ss and ampm parts are optional. EOD NA NA Indicates the end of data for the file record. Required Items Field Lengt h Carrie d Over Definition 3-20 Oracle Fusion Middleware System Administrators Guide for Oracle Content Server EOD dDocName=HR002 dDocTitle=Payroll Change Form primaryFile=hr002.doc DIndate=22099 dRevLabel=3 EOD

3.6.1.5.3 Update Example 2 This example assumes that one file is already checked into

the system with the following metadata: ■ Content ID = HR003 ■ Release Date = 31597 ■ Revision = 1 ■ Title = Performance Review ■ Author = Smith Because Revision 1 of the Content ID HR003 exists in the system and is not in an active workflow, the revision will be updated with the new Title, Author, and Release Date metadata. Action=update dDocName=HR003 dDocType=Form dDocTitle=Performance Review Template dDocAuthor=Smith primaryFile=hr003.doc dIndate=22099 dRevLabel=1 EOD

3.6.1.6 Optional Parameters