Selecting an action on this form will result in that action being performed on the actual archive records identified in the search list.
Be sure to review the contents of the list completely before performing a task.
Note that if there are archives from multiple libraries in the search list, they will be consolidated in the target path.
Clicking on a blue arrow will open additional help instructions on the form.
Do What?
| • | Save archives to HTML Creates an independent browse-able directory of uncompressed and unencrypted documents that can be copied to any other file system or media. |
| • | Save list to tab-separated values file The file is created from the perspective of the UnForm server location, not the local client workstation. To return a CSV file to the desktop use the 'Export' option which is a separate button on the Search results page. |
| • | Transfer archives to a library Copies documents out of the current library to another library, and REMOVES them from the current library. Used for purging. See additional information below under 'Where'. |
| • | Copy archives to a library Copies documents out of the current library to another library without removing them. |
Duplicates?
Replace or Skip
Archives are uniquely identified by a document type and ID. Archive images are similarly identified by type, ID, and a Sub ID. Please note the following regarding duplicate handling:
| • | HTML exports only go to empty directories, so this setting does is ignored. |
| • | Export lists must go to a new (non-existing) file |
| • | If transferring (rather than copying) and a duplicate record is skipped, the original record is NOT removed. |
| • | Duplicate conficts will be logged temp/srch/logs/0000000005.log. |
To Where?
This is a path on the UnForm archive server that is treated in the following ways:
| • | For HTML, this path is the top level of the archive browsing structure. There will be an index.html file that leads to a browsing structure to all the selected archives. This path structure can be copied to any other file system or media. To prevent accidental corruption of existing HTML resources, the path must initially be empty or non-existent to export HTML. |
| • | For export lists, the path is created as a text file and all records in the search list are written to it. The format of the exported data is Library <tab> Document Type <tab> Document ID. |
| • | For Transfers, this is a target library to which the archives will be moved. The archives will no longer be in their source library. This option can be used to purge records, by first transferring them to an interim library, then backing up and removing that library from the file system. |
| • | For Copies, this is the target library to which the archives will be copied. The archives will remain in the source library as well. |
What Sub-Id's?
This option applies only to HTML exports. For any given document, there may be multiple document versions, identified by sub-IDs. List the document sub-IDs, or sub-ID wildcards, separated by semi-colons, that you want to add to the HTML export. If you leave this field blank, all document sub-IDs will be exported.
For example: @unform will just export the PDF documents originally added to the archive by UnForm jobs. @unform; scan* will add the original UnForm job PDF's, plus any sub-IDs that begin with the letters "scan". The names are not case-sensitive, so sub-IDs of Scanned and scan01 would both be added.