The ability to bulk tag is a very powerful feature. In that same regard, it can also be very dangerous. Always be sure to check your search and document counts prior to finalizing a batch tagging command.
On a technical level, there is really no difference between tags/folders on different tabs – a tag is a tag wherever it may reside. They are arranged as they are for organizational or security purposes. One feature we do enable is that any tag that is clicked on the Review tab, will also tag the document as Reviewed. ***Keep in mind that bulk tagging can be used to isolate a subset of documents under any tag, but it can also be used to bulk review. If using bulk tagging for review, it ignores the folder rules described above, as well as the radial tagging that only allows one choice in a group. As a result, you will also need to also remove the range from ‘Not Reviewed’ and add it to ‘Reviewed’.***
In the example above, I left the search modifier on &, so the two searches are combined together with an and query. This can be changed to Single Search or by clicking on the icon. The default for the database is &, but it will keep a setting you change it to until you log out. The search above would effectively isolate a group of documents by date and a custodian tag. The number 51/51 (upper right hand corner of the table) shows that it includes 51 documents, out of 51 in the database.
Once your search is isolated, you can add them to an existing tag.
The folder icon with a + will allow you to create a new folder – the red x will let you delete one. The page icon with a + will allow you to add selected documents or a full search to a folder – the red x will remove them.
In the example of batch coding for review: If I determined these documents were irrelevant, I would click the page icon with the + and the left click on the Irrelevant tag on the review tab. This will put the top level tag name into Folder Name box. All Documents – adds all documents in the existing search to the tag. Selected Documents – adds only documents checked in the table view next to the Rec#. Documents in Range – adds a range IE 1-200 (affected by document sort).
I would then do the same thing for the ‘Reviewed’ tag, and then use the page icon with the red x to remove this range from the ‘Not Reviewed’ tag.
*As a side note, if document groups are turned on, the Entire Family will also receive the same coding. If you want to tag only the documents responsive to the search, disable document groups prior to batch coding.*
**If bulk coding without a search in place, the entire database will be your current search. Be careful not to code the full database**
Leave A Comment?