Follow

How to Set Up Fields in DISCO

Setting Up Fields in the Document Viewer

To set up your custom Fields in DISCO, you will first navigate to the main menu and select Fields located under SETUP. To be able to add a new Field, you must have Admin level access in your DISCO matter.

To add a new Field, you will start typing the desired title where it says  ‘Add a new field…’ on the very left of your Fields page.

For purposes of this example, we will add a new Field labeled “Internal Identifier Field”. You will then select who has access to your Field by clicking on the drop down menu under ‘ACCESSIBLE TO’. You can select ‘All users’ or ‘Select users’ to only allow a certain set of Reviewers to have access to your custom Field.

In the Document Viewer, the custom Fields created will display in the coding panel located on the very left, just under Tags.

You may enter the data you wish within each of the custom Fields created by clicking on the arrow icon in the FIELDS section. You also have the option to hide empty fields.

You will click the arrow icon in the FIELDS section again to hide the text entered within the custom Fields created. The FIELDS section will still display the fact that there are two fields with data entered, even after collapsing the section.

Access Levels in regards to Fields creation:

  • Admins - can create and see all Fields created on the “Fields” creation page as well as view all custom Fields in the Doc Viewer
  • Reviewers & Restricted Reviewers - can only see Fields in the document viewer that they have been given access to and will not have access to create custom Fields.

Adding Fields to Your Review Stage Decision Panel

The custom Fields created in your DISCO matter can also be incorporated in the decision panel when setting up a Review Stage.

Please note that only those users who have access to the Field has the ability to add and edit the field data.

Searching for Fields

You can search the contents of Fields to which you have access using the Field name. For example:

  • To find documents that contain the word ‘important’ in a Field named ‘Deposition’, search for:
    deposition(important)
  • To find documents that contain the words ‘possibly privileged’ in a Field named ‘PSL Notes’, search for:
    “psl notes”(“possibly privileged”), or
      psl_notes(“possibly privileged”)
  • To find documents that contain the word ‘important’ in any Field to which you have access, search for:
    fields(important)
  • Wildcard (*) and truncation (!) can be used in the Field name and the contents in the examples above. For example, you can search any Field name starting with ‘PSL’ which contain variations of the word ‘depo’:
    psl!(depo*)

You can also search to find documents that have any data in a Field, regardless of the contents:

  • To find documents that have any contents in a Field named ‘Deposition’, search for:
    hasDeposition(), or
    hasDeposition(true)
  • To find documents that have any contents in a Field named ‘PSL Notes’, search for:
    has”PSL Notes”(), or
    has”psl notes”(true)
  • To find documents that have any contents in any Fields, search for:
    hasFields(), or
    hasFields(true)
  • Wildcard (*) and truncation (!) can be used in the Field names above. For example, to find documents that contain any data in any Field names starting with ‘PSL’,  you can search for:
    hasPSL!(), or
    haspsl!(true)
  • Conversely, specifying ‘false’ instead of ‘true’ this the examples above will return documents that do not contain data in the Fields.

As mentioned above, when using searching, it is scoped to only search Fields to which the user has explicit permission to access.

Fields + Custom Columns

If there are custom fields ingested into your DISCO database via loadfile, you can view these fields as columns in your view. For more information on how to set up your Custom Columns in DISCO, please read DISCO's Custom Column User Guide.

Search Results Index Reports

You have the ability to also export DISCO Fields in Search Results Index Reports. Furthermore, these reports are private, limiting users who don't have access to certain fields from downloading them from the Reports page. 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments