A product may require specific documentation based on a model or software version.
In this use case, a program has new features in its 3.0 version. Content publishers can add the "version": "2.9"
to the relevant documents, and add the "version": "3.0"
to the relevant topics or documents.
If metadata values for a single key is not consistent throughout the documentation (capitalization, switched first and last name of author, etc.), it is possible to use the Enrich and Clean feature to homogenize metadata.