Answered by Eliot Davidoff

Ringtail has a number of different tools to organize documents to suit different purposes and preferences. Four key organizational structures are binders, issues, levels and saved searches.

  • Binders are containers of documents. You can add documents to a binder to save them for later review, or so that another user can access the binder to see the documents that you added. Binders are static, so documents are only added or removed by an explicit user action. A document may be in any number of binders. 
  • Issues are similar to binders, but they have a hierarchical structure. They can be used for document coding using a tree interface, but are more commonly used for organizing related groups of documents for tasks like research or production preparation. Like binders, issues are static, and a document may be in any number of issues. Security is configured on each root issue, and applies to all child issues underneath it. 
  • Levels reflect the underlying file folder structure Ringtail uses to store the image and native files associated with documents. Levels are defined when documents are added to a case, typically reflecting the way the files were organized upon load. A document may only have one level. Levels are used to control document security
  • Saved searches are a dynamic way to organize documents based on their attributes. Rather than saving a static group of documents, you can save a set of criteria as a saved search. When you run the search, you will get documents in your results that meet the search criteria at the time you run it, which may be different from the documents that met those same criteria when the search was created. Saved searches are useful for accessing changing document sets based on field coding or new documents being added to the case. For example, use a saved search to find all documents marked responsive that have not been produced.