Standard Workflows
      Back to home
      1. Reveal Knowledgebase
      2. Workflows
      3. Standard Workflows

      Using Is Native File Function

      Creating a field to add additional natives to a document record.

      The Is Native File function when creating a field allows you to upload additional natives to records. This can be particularly useful when trying to examine documents containing more than 16MB of text.

      For performance reasons there is a hard limit of 16MB expanded text size for indexing documents in the Native / HTML text set. While settings in Review Manager may be set to indicate a larger limit, any document exceeding the 16MB limit will not index and an error will appear in the indexing log. We strongly recommend contacting Reveal Support if encountering this limitation.

      Note:  The native and text file sizes differ from the expanded file sizes. The expanded file size is the size of the text set created.

      1. Create the Field

        1. Log into Review Manager with an Administrator account.
        2. Expand the Project Setup pane in Review Manager.
        3. Open Fields.
        4. Use New Field to create a new field with the Is Native File Field setting selected. This allows native documents to be moved into the field. Native File Workflow-01
        5. See How to Load Data - Third Party Production for further details on this modal.

      2. Populate the field with natives.

        1. Import the natives via load file, the same way you would load to the Exported Native File field. This might require a forced move during Document Import.
        2. Prepare a CSV with the BegNum (control number) and path to the added native file, here "ExtraNative". 
          Native File Workflow-02
        3. In Review Manager, open Import > Documents.
        4. Enter the required information for importing the CSV to your project and select Force Move to import the referenced native file to the project's S3 data store.
          Native File Workflow-03

      3. Check that the file(s) is now in S3.

        1. View the contents of the native file field (here ExtraNative). Native File Workflow-04

      4. The file can now be exported in a production or downloaded from the viewer.

        1. Click on the Download Native button to see the new native. Native File Workflow-05

      5. Create a Text Set and reference the new field. This will allow us to view the extra native file in a new viewer.

        1. You will notice that there is no "ExtraNative" viewer, as this requires you to create a text set that references the secondary native field as the "load field".
        2. In Review Manager, open Project Setup > Text Sets.
        3. Create a new text set for the added native file field as shown in the illustration below.Native File Workflow-06
        4. See Creating Document Text Sets for further details on this process.

      6. Index the New Text Set.

        1. This will create the new Text Set viewer for the native in the "ExtraNative" field.
        2. Create a list of documents (by control number) containing the addition native file field to be indexed, and save it as a TXT file.
        3. In Review Manager, open the Create pane.
        4. Choose Indexes.
        5. For your project, select the DocList TXT file and the new text set to be indexed.Native File Workflow-07
        6. See How to Index Data for further details on this topic.

      7. Review the New Text Set.

        1. Once the text set that references the second native is indexed, you will have a viewer. Native File Workflow-08

         

        Last Updated 1/23/2024