The Tag Wizard criteria builder offers a wide range of fields for defining smart tag conditions. Fields fall into three categories: Document Metadata, File Properties, and Relationships. Each field supports specific operators that vary by data type.
Document Metadata fields
Document Metadata fields come from the content of your files during processing. Hintyr analyzes each document and identifies structured information like named individuals, document classifications, and dates referenced in the text. These fields let you build criteria based on what a document says, not just its file properties.
- People - Individuals mentioned in or associated with the document. Operators: contains any of, contains all of, contains none of, is empty, is not empty. Values come from a multi-select dropdown populated with names found in your case.
- Document Type - The classification of the document (e.g., Email, Contract, Letter, Memorandum). Same list operators as People.
- Physical Evidence - Indicators that the document references tangible items or physical objects. Same list operators.
- Forensics - Forensic analysis markers such as hash values or authentication indicators. Same list operators.
- Email From - The sender address for email-type documents. Operators: equals, not equals, contains, starts with, ends with, is empty, is not empty.
- Email To - The recipient address(es) for email-type documents. Same text operators as Email From.
- Dates Mentioned - Calendar dates referenced in the document text. Operators: before, after, between, on, is empty, is not empty. A date picker or date range picker appears depending on the operator.
- Privilege Type - The privilege designation assigned to the document (e.g., Attorney-Client, Work Product, Joint). Same list operators as People.
File Properties fields
File Properties fields describe attributes of the file itself: its name, format, size, and filesystem timestamps. These fields are available for every file in the case regardless of whether content processing has finished.
- File Name - The original name of the uploaded file. Operators: equals, not equals, contains, starts with, ends with. You can type a value or select from existing file names in the case.
- File Type- The MIME type of the file (e.g., "application/pdf", "message/rfc822"). Same text operators as File Name, with values populated from the types in your case.
- File Size - The size of the file in bytes. Operators: equals, not equals, greater than, less than, greater than or equal, less than or equal.
- Created Date - The date the file was originally created. Operators: before, after, between, on, is empty, is not empty.
- Modified Date - The date the file was last modified. Same date operators as Created Date.
Relationship fields
Relationship fields let you build criteria based on how files connect to other organizational features in Hintyr, such as other tags and custodians. These fields enable layered categorization where one tag can reference another.
- Has Tag - Matches files that belong to a specific tag. Operators: equals, contains any of. A dropdown shows all existing tags in the case. Useful for layered smart tags like "All PDFs in the Key Documents tag."
- Custodian - Matches files assigned to a specific custodian. Operators: equals, contains any of. A dropdown shows all custodians defined in the case.
Tag dependency and circular prevention
When you use the Has Tagfield, you create a dependency between two tags. If Smart Tag A has a condition "Has Tag equals Tag B," then Tag A depends on Tag B. Hintyr prevents circular dependencies to keep evaluation consistent. If Tag A already depends on Tag B, Tag B can't reference Tag A in its own criteria. The wizard automatically excludes tags that would create a circular reference from the Has Tag dropdown.
This protection ensures tag evaluation always terminates correctly. When you re-evaluate a smart tag that references other tags, Hintyr resolves dependencies in the correct order so results stay consistent.
Universal operators
In addition to the field-specific operators listed above, every field supports is empty and is not empty. These match files where the field has no value or any value at all. They don't require a value input, making them useful for filtering out files with missing data or confirming that a field has been populated.