How it works
Classification is defined centrally and applied by everyone:- Tags categorize assets with values drawn from a controlled, hierarchical list. Namespaces are the allowed keys and Tags the allowed values, so a Project can carry
business-domain:oncologyanddata-sensitivity:confidentialat once. - Properties capture typed information that no fixed list can hold, such as a last-validated date or an internal model ID.
- Admins and Librarians define the tag structure and the available Properties, so classification stays consistent across teams. Everyone applies them to their own assets: Apps, Projects, Project Templates, Datasets, NetApp Volumes, and Models.
- Search closes the loop. Global search, entity listing filters, and the Tag Browser surface classified work across the deployment, within each user’s permissions. Projects set to Searchable appear in results even when their contents stay restricted, so colleagues can discover that relevant work exists and request access.
Choose between tags and properties
Tags organize entities so people can find them. Properties document information about an entity. Pick based on the shape of the value you need to capture:
Use Tags when the set of allowed values is finite and known in advance: users pick from a controlled list, and parent-child relationships let you model nested categories. Use Properties when the value can’t be enumerated up front. Most teams use both, Tags for organization and Properties for documentation.
Work with knowledge management
Tags
Build a tag structure, apply tags to your assets, and find tagged work.
Properties
Define typed fields and record values on your assets.
Related
- Use Domino search: find files, Projects, Jobs, and comments across the deployment.
- Collaboration: share and discover work across teams.
- Projects: the unit of organization most classified assets belong to.