...
Since each category can be linked to a specific Wikidata page, we can unify our understanding and vocabulary regarding category names. This standardization helps avoid confusion in daily conversations with our colleagues.
he The ID for each category typically looks something like this: Q3196
This text is an identifier that can be used to link to a human-readable entry in the Wikidata database.
...
Change the hierarchy tree
Go to Settings → CategoryThe category hierarchy tree is fully customizable. Simply drag and drop items within the Tree View to change the order and parent/child relationships of categories. You can add new categories as needed or modify existing ones by clicking on a category and updating the data in the Details View.
...
Edit hierarchy menu bar
...
Hierarchy | current hierarchy to view/edit |
Hierarchy path | file path to hierarchy file on disk |
Search | search for category name in hierarchy |
sort alphabetically | sort the categories in hierarchy in alphabetically order |
add category | adds a new item to the hierarchy |
delete all categories | ⚠️ deletes all the categores of the hierarchy tree |
reset 🔄 | restore state before making changes to the hierarchy tree |
save hierarchy | save changes to the file on disk if no changes have been made the button is deactivated |
Hierarchy tree file
The category hierarchy tree will be saved to a file called hierarchy.json
This hierarchy tree data will be used across all loaded libraries.
Since version 2.1.0+ a different hierarchy tree can be defined for each library.
To ensure the software can locate custom hierarchy data, the file must be either placed in the resources folder (DASELEMENT_RESOURCES) at the following specific location or in the folder defined by the hierarchy environment variable (DASELEMENT_HIERARCHY):
| Code Block |
|---|
$DASELEMENT_RESOURCES/hierarchy/hierarchy.json |
...
or ...
$DASELEMENT_HIERARCHY/hierarchy.json |
Hierarchy tree overwrite per library
To define a specific hierarchy tree for a library, create an override in the library settings.
Create overwrite
...
Overwrite active
...
The order of loading the hierarchy:
use hierarchy defined in the library hierarchy overwrite
if not found, use hierarchy defined with environment variable (
DASELEMENT_HIERARCHY)if not found, use hierarchy defined with environment variable in global resources folder (
DASELEMENT_RESOURCES)if not found, use default hierarchy of the installed Das Element version
Edit the hierarchy tree
Each category has the following fields: an ID (by default, the Wikidata ID), a human-readable label, a description text, and synonyms.
Both the category ID and the category name can be used in the Path Builder, the custom command line as well as the ingest view for tags and metadata. Use is as the Path Value tokens, e.g. <category.name>
The user can add, delete, or modify existing synonyms in the details view on the right side. Searching for a synonym will always bring up the corresponding category in views such as the gallery view or the ingest view.
The category hierarchy tree is fully customizable. Simply drag and drop items within the Tree View to change the order and parent/child relationships of categories. You can add new categories as needed or modify existing ones by clicking on a category and updating the data in the Details View.
| Info |
|---|
You can even customize the hierarchy tree to function as a VFX project with sequences and shots. In this setup, the top-tier categories are the sequence names (001, 002, etc.), and the child categories are the shots (001_0010, 001_0020, etc.). |
Default hierarchy file structure
...