Do you want a metaproperty option to only show in the upload screen when another metaproperty is selected first? Metaproperty dependencies allow you to make a metaproperty option dependent on one or multiple other metaproperty options. Start making use of metaproperty dependencies and keep your upload screen clean and well organized without showing unnecessary options to your users.
There are two types of metaproperty dependencies that you can set up. The first option is to set the dependencies on a metaproperty level, which allows you to manage the visibility of your metaproperties in the upload screen. By default, the label of a metaproperty is shown. In case you have a lot of metaproperties your users can get overwhelmed and be presented with unnecessary information. To keep your upload screen clean and well-organized it can be useful to only show a metaproperty when another metaproperty is selected first.
This is where metaproperty dependencies come in. By setting up dependencies on a metaproperty level you can manage the visibility of metaproperties during upload and completely hide their labels from the upload screen.
Let's say we have a Country and a City metaproperty and we only want to show the City metaproperty once a Country has been selected. By making all the City metaproperty options dependent on the corresponding Country option the system knows that it should hide the label of the City metaproperty in the upload screen until a Country has been selected.
Once you have set up the dependencies on a metaproperty level you will need to set up the same dependencies on a metaproperty option level as well. This allows the system to determine which options need to be shown the moment a metaproperty is clicked. The system checks whether the option(s) they're dependent on are already selected and in case the dependency is met the option(s) will show. You can set up set up a single dependency or a group dependency.
For example, the moment a user selects a Country all cities will show under the City metaproperty, since the metaproperty dependencies only manage the visibility on a metaproperty level. We now want the system to only show the cities that correspond to the selected Country and this we can manage by setting up dependencies on a metaproperty option level. By making the city Berlin dependent on the country Germany the system will only populate Berlin once Germany has been selected. By making all other City options dependent on a Country option as well you can ensure that only German cities are shown once a uploader selects Germany
As a rule of thumb you can think of metaproperty dependencies as a way to hide metaproperty labels from the upload screen and the metaproperty option dependencies as a way to manage which options will be shown the moment a metaproperty is clicked.
Note
Did you know?
Dependencies can play a big role in your taxonomy. Avoid confusion and check out the information below to have a better understanding of metaproperty dependencies.
-
Once you have set a metaproperty option dependency do not forget to set the dependencies for the other options that belong to that same metaproperty as well. If not, these options will not have a dependency and, therefore, not show in the upload and/or edit screen.
Let's have a look at an example. A portal has a Country and a City metaproperty. The City metaproperty contains the following three German cities: Berlin, Hamburg and Cologne. The moment you make Berlin dependent on the Country option Germany Berlin will only show in the upload and edit when Germany is selected.
If users select Germany they will only see Berlin and not the other German cities Hamburg and Cologne. In order to see these options as well when Germany is selected both City options will have to be made dependent on the Country option Germany as well.
-
When you edit assets and you change the parent metaproperty option, its dependencies get cleared. For example, if cities are dependent on countries, and you edit your assets and change your selection of the country, the formerly selected city option gets cleared.
-
Metaproperty dependencies are not respected when batch editing. For example, when you want to change the City metaproperty option your assets are tagged with and your batch edit includes assets tagged with different Country options, the system will show all cities in the batch editing screen. In order to avoid dependency conflicts and to allow saving your batch edit the metaproperty dependencies can no longer be applied.
-
Go to
Settings > Taxonomy > Metaproperties management. -
Click the
button next to the name of the metaproperty that you want to make dependent on another metaproperty. -
Go to the Metaproperty Dependencies section and click the Choose metaproperty dropdown.
-
Search and select the metaproperty for the dependency. The Choose linked options dropdown will appear.
-
Click the Choose linked options dropdown. Search and select one of the available metaproperty options.
-
Click the + Add button to add the dependency.
-
Repeat steps 4-6 till all the metaproperty options that belong to the metaproperty, chosen in step 4, are added.
Once you metaproperty dependencies are set up start configuring the dependencies on a metaproperty option level. Read more about it in the section below.
Note
You can't set up both single and group dependencies for the same metaproperty. Make sure that all options within the same metaproperty have the same type of dependency set up, so either a single or a group dependency. Read more about dependencies here.
Filter Dependencies as Active Filters
With active filters you can make sure that smart filters automatically open when a user clicks an option from a metaproperty overview page.
In the below example you see that the smart filter Terms of use automatically opens after clicking Logo from the metaproperty overview page.
Note
The active filter only opens when triggered from the Metaproperty Tile view (with filter).
-
Create an overview page for a metaproperty using the Metaproperty Tile view (with filter). Read more about it here.
-
Go to
Settings > Taxonomy > Metaproperties management. -
Click the
button of the metaproperty that contains the metaproperty option, which should open a smart filter when clicked.Tip
Use the search bar in the right top corner to search specific metaproperty options. Enter the name or label of the option you’re looking for and click Search. Click Reset to show all options again.
-
Click the
button of the metaproperty option for which you want to set up the active filter. -
Click the Choose linked options dropdown in the Filter dependencies section. Search and select the metaproperty that you want to open when this metaproperty option tile is clicked and click the + button to set up the active filter.
Create a Single Dependency
You can set up metaproperty options so that one is dependent on the other. This means that a certain metaproperty option will only display during upload if another specific metaproperty is selected first. For example, if you select the option Germany under the metaproperty Country, the metaproperty option Berlin will become available under the metaproperty City. On the other hand, when you select the option France, the option Paris will display. This is because, the options Berlin and Paris are dependent on the corresponding countries.
-
Go to
Settings > Taxonomy > Metaproperties management. -
Click the
button of the metaproperty that contains the metaproperty option for which you want to set up a dependency.Tip
Use the search bar in the right top corner to search specific metaproperty options. Enter the name or label of the option you’re looking for and click Search. Click Reset to show all options again.
-
Click the
button of the metaproperty option for which you want to set up the dependency. -
Make sure that no group dependencies are set up for this metaproperty option and any other options within the same metaproperty. A metaproperty can't have both single and group dependencies set up.
-
Click the Choose metaproperty dropdown. Search and select the metaproperty that you want this option to be dependent on. The Choose linked options dropdown will appear.
-
Click the Choose linked options dropdown and search and select the metaproperty option that you want this option to be dependent on.
-
Click the + Add button to set up the dependency.
Create a Group Dependency
With group dependencies you can set up multiple dependencies for a metaproperty option. This means that the metaproperty option will only show during upload when the other dependent metaproperty options are selected first. For example, when you want the city Athens to only show when the continent Europe and the country Greece are selected.
-
Go to
Settings > Taxonomy > Metaproperties management. -
Click
for the metaproperty whose option should be dependent on other metaproperty optionsTip
Use the search bar in the right top corner to search for specific metaproperty options. Enter the name or label of the option you’re looking for and click Search. Click Reset to show all options again.
-
Click the
button of the metaproperty option for which you want to set up the group dependency. -
Make sure that no single dependencies are set up for this metaproperty option and any other options within the same metaproperty. A metaproperty can't have both single and group dependencies set up.
-
Select the Create new dependency group option.
-
Click the Choose metaproperty dropdown. Search and select the metaproperty that you want this option to be dependent on. The Choose linked options dropdown will appear.
-
Click the Choose linked options dropdown and search and select the first metaproperty option that you want this option to be dependent on.
-
(Optional) Set up more dependencies for your dependency group. Click the first dropdown again to select another metaproperty and click the second dropdown to select another metaproperty option. Repeat this step as often as necessary to add as many dependencies as needed.
-
Click the + Add button to set up the group dependency.
Comments
0 comments
Article is closed for comments.