FAQ: How do I handle the 63 Responsive Issue limit in Discovery?

Follow

Nextpoint allows for the creation of up to 63 Responsive Issues when you are working in any given Discovery database. If you meet the 63-issue limit, you will receive a notification stating you have reached the maximum number of issues allowed in that particular database, and you will not be able to create additional issues.

Note: There is currently no issue limit in LITIGATION

What do you do if you receive the above notification?  While the 63-issue limit is inflexible when working in Discovery, outlined below are several workflow solutions which will assist in navigating an alternative approach if needed:

  1. If two issues are similar, you can merge into one comprehensive issue to free up the secondary issue.

    The easiest way to consolidate two issues is to Filter for all documents tagged with Issue A  Select All from your Grid View of results  Bulk Actions

    Consolidate_Issues1.png

    Consolidate_Issues2.png

    In Bulk Action pop-up, set Relevancy status Responsive as to "Issue B".  

    Note: Any bulk actions related to Responsive issues (both adding + removing) are additive and subtractive functionalities, respectively.  In other words, if you perform a bulk action update tagging 2 documents with responsive issue B, when they are already tagged with responsive issue A, then the resulting coding for those documents will be responsive issues A AND B.

    Consolidate_Issues3.png

    Then, Filter for all documents with tagged with "Issue B"  Select All from your Grid View of results  Bulk Actions  Remove Responsive Issue A.

    Consolidate_Issues4.png

    Consolidate_Issues5.png

  2. Create an additional (custom) Field titled "Additional Responsive Issues", set as a picklist field type, and add your remaining issues as values to this field.

    additional_responsive_issues.png

    It is important to note:

    Be considerate of any potential Bulk Actions you will need/want to make, as Bulk Actions for Picklist type fields will overwrite any existing selections for that field.

    For example, if you were to select a series of documents tagged with the Pricing and Fraud values of an "Additional Responsive Issues" picklist type field, and then make a Bulk Action to mark all documents with the Contract "Additional Responsive Issues" value, all selected documents would then only be tagged with the Contract issue.

  3. If some of your issues fit into a particular category/categories, you may want to consider setting up a field for that category in order to free up some space for your other issues.

    For example, if you are tagging documents as to multiple states, instead of creating a Responsive Issue per state, you can create a field titled "State", and then list all possible values below.



    Note:  As in the (red) important note above, if you choose a Picklist field type, be considerate of any potential Bulk Actions you will need/want to make, as Bulk Actions for Picklist type fields will overwrite any existing selections for that field.

 

Return to Discovery Workflow here.

 

 

 

 

0 out of 0 found this helpful

Comments

0 comments

Please sign in to leave a comment.