In https://eactive.atlassian.net/browse/INTEGRATED-1765 a new media overview is introduced. This media overview has the possibility to categorize media items. For this a “Media taxonomy” content type is used, to allow other Integrated features (use the content type for relations, linked by, bulk actions etc.).
For this purpose the Media taxonomy contenttype should be always available. In https://eactive.atlassian.net/browse/INTEGRATED-1789 this is arranged. But it is also important that the relation always exists. Media items cal always be categorized.
Requirements
Make sure the Media Taxonomy relation exists
Options brainstorm:
The media taxonomy can be chosen on all File content types (including Image and Video). I think the relation needs to be added by the RelationType or by an event listener? (note: there is some idea to modify the content form to add a formtype for each relation type, instead of one formtype for all relations, to change the order of all fields including relations in the future)
Some configuration in attributes which alles to add a relation. Would be very cool if relations could be created in code by defining the classes, but this has some challanges
Some hook to create / modify a locked relation specific events like cache warmup and content type creation
@Marijn Otte the current logic is dependend on the database. example: vendor/integrated/integrated/src/Bundle/ContentBundle/Provider/ContentProvider.php
can we implement it like vendor/integrated/integrated/src/Common/ContentType?
Background
In https://eactive.atlassian.net/browse/INTEGRATED-1765 a new media overview is introduced. This media overview has the possibility to categorize media items. For this a “Media taxonomy” content type is used, to allow other Integrated features (use the content type for relations, linked by, bulk actions etc.).
For this purpose the Media taxonomy contenttype should be always available. In https://eactive.atlassian.net/browse/INTEGRATED-1789 this is arranged. But it is also important that the relation always exists. Media items cal always be categorized.
Requirements
Make sure the Media Taxonomy relation exists
Options brainstorm:
The media taxonomy can be chosen on all File content types (including Image and Video). I think the relation needs to be added by the RelationType or by an event listener? (note: there is some idea to modify the content form to add a formtype for each relation type, instead of one formtype for all relations, to change the order of all fields including relations in the future)
Some configuration in attributes which alles to add a relation. Would be very cool if relations could be created in code by defining the classes, but this has some challanges
Some hook to create / modify a locked relation specific events like cache warmup and content type creation