By using the Diva Archive Content Action node within a stream it is possible to trigger an archive object job in Diva.
For proceeding the job a unique "Object name" and “Object Category” must be defined. The "Object category" (a.k.a collection) must be an existing one in the system. The "Source" identifies the source (server or disk such as FTP or CIFS from where the files are ingested (e.g. for FTP insert "ftp"). The "Media name" identifies the DIVArchive media name and refers to a collection of object instances stored on the same or similar disk or tape media.
"Files path root" identifies the source root path from where the files should be archived from. The corresponding files that should be archived will be identified in the node's property "Files names list" by giving the name of the file(s) incl. extension. You can use a comma separated list or multiple individual entries that can be created with the plus button of this input field. Further, the "Quality of service" (Default, CacheAndDirect, CacheOnly, DirectAndCache, DirectOnly) can be defined. It controls how requests are cached during processing. The "Priority level" of the job may be configured as well and can be any number between -1 and 100 where -1 stands for unset and is the lowest and default value.
Optionally, "Comments" can be attached to the job in Diva. With “Archive options”. To visualize the status of the job a "Job start message" and "Job finish message" can be defined and will displayed in the IO job dashboard.
„Archive options“ identifies additional options for the archive command. These options are typically prefixed with a dash (similar to command line options). Some options can override parameters for the Source/Destination. Some typical archive options include:
r: Recursively archive subdirectories.
gcinfilelist {gctype}: Specify the type of genuine checksum. The default type is MD5.
Following the example values from Diva - Object category: PROJ PARK HELMUT - Source: EDITSHARE_ARCHIVE - Media name: PARKINZON