Differences

This shows you the differences between two versions of the page.

@@ Line 1: / Line 1: @@
+<html>&#091;</html>[[start#iview | Up To Index ]]<html>&#093;</html>
+====== Configuring iView 6 Archives ======
+Menu IVIEW, option 1:
+{{pub:iview6:iviewarchivedef.png?600|}}
+This display is used to add or change an archive definition, although one can not\\
+change the meta data fields after the archive is created.
+===== Archive Options =====
+  * **Application Name**: Use 10 characters alphanumeric. Embedded blanks are not recommended.
+  * **Library**: This is the library in which the meta data file is stored and is a global setting stored in data area DSIVIEWLIB.
+  * **Directory**: This is the root of the iView IFS archives. It is a global setting stored in data area DSIVIEWDIR.
+  * **File Name**: Specify the file system object name of the archived document using constants and these keywords:\\
+<html><pre>
+    *DATE to include QDATE
+    *TIME to include QTIME
+    *INDEX01 - *INDEX20 to include the current values of these meta data fields
+</pre></html>
+  * **Disposition Options**: This controls the fate of the original spool file:
+<html><pre>
+  *RETAIN        Retain in Outqueue
+  *ORIGINAL      Archive Original
+  *SYSTEM        Archive Post Processing
+  *NONE          Do Not Archive
+</pre></html>
+  * **Table Import**: Controls use of tables when importing from prior implementations of iScan. This field is not used
+with current software and should be set to N.
+  * **Processing Options**: Process spool file under the iView user profile or under the profile of the spool file owner.
+This will impact what profile owns the spool file post-processing.
+<html><pre>
+  *SYSTEM        Use iView System Profile
+  *SPLFOWNER     Use Splf Owner Profile
+</pre></html>
+iDocs Application: If you want the spool file processed through iDocs before archiving specify the
+application here. If specified what is archived is a laser document, else it is a pdf document made from the
+text spool file.
+Product: Specify IDOCS to create a laser document using the iDocs Suite. Otherwise leave blank.
+This field is used for integrations with other document products.
+Storage Format: Specify the document type of the file. *PDF is the usual selection due to ease of use
+with a browser. PDF is also the front end default and any other selection may require front end configuration changes.
+<html><pre>
+  *PDF           *USERASCII PDF Conversion
+  *TIFF          Tiff Image
+</pre></html>
+===== Meta Data Fields =====
+The meta data fields are defined by their position in a *SCS spool file.
+**Seq#**: You can change the order of the columns of the meta data table by keying a different sequence number\\
+and pressing <enter>.
+**Page#**: Use keywords *FIRST, *LAST, *ALL, or a specific page number to specify from which page the meta data\\
+value is scraped.
+**No. Pgs Indexed**: Key the number of pages from which spool text is scraped and concatenated to form the \\
+meta data for the meta data field. Left blank, 1 page is scraped unless *ALL pages is specified.
+Sorting is specified as it is in iDocs:
+<html><pre>
+          Primary Sort Ascending
+          Primary Sort Descending
+          Secondary Sort Ascending
+          Secondary Sort Descending
+          Third Sort Ascending
+          Third Sort Descending
+          Forth Sort Ascending
+          Forth Sort Descending
+          Fifth Sort Ascending
+</pre></html>
+Since this is text against which users will search in a browser, the normal practice
+is to define short, one line text fields as meta data. Fields such as customer name, customer number, etc.
+You can define text blocks as meta data but the searching dynamics should be considered.
+\\
+Meta data is stored in the meta data file, having the same name as the archive application, in the iView library.
+Bursting works as it does in iDocs and as one would intuitively expect.
+===== Path Variables =====
+{{pub:iview6:iview6archivepathdef.png?600|}}
+A path is defined to create a directory structure in the archive. The directories
+are in the IFS and are real, not virtual. The archived document is placed in the path
+created by the path definition.
+At archive time the engine creates a file path using the specified meta data fields,
+creates the directories if they are not present, then places the archived document in the
+path.
+Example:
+Archive application is INVOICES.\\
+*PATH01 is INDEX01, which evaluates to 100100 at archive time for a specific document.\\
+*PATH02 is INDEX02, which evaluates to 2013JANUARY at archive time.\\
+The iView IFS root is /iview6 ( data area DSIVIEWDIR ).\\
+The archived document ( named 01000010001.pdf ) is placed thus:\\
+/iview6/invoices/100100/2013JANUARY/01000010001.pdf
+\\
+----
+<html>&#091;</html>[[start#iview | Up To Index ]]<html>&#093;</html>