One of our primary business cases for related assets is to relate talent releases (model releases, etc) or creative licenses to the asset to show that we have the right to use images, music and other creative materials. We would like to be able to clearly call out when an asset relationship is for this pupose to drive compliance with intellectual property laws and guidelines.
Use-case:
A user creates an asset relationship between an asset like a photo or video and the model release provided by a person whose likeness is used in the aset, and relates the model release as an asset reference, with the type of "Release", rather than "Other".
Current/Experienced Behavior:
A user loads a new photography asset into AEM Assets that has a recognizable face in it. The user uploads a PDF version of a model release from the person whose likeness appears in the image, and from the original image, creates a relationship type of "Other" from the image to the PDF model release. Future viewers of the image asset see a relationship type of "Other" and need to rely on the asset title of the model release, or viewing the model release itself, to understand if there is a release related to the photo.
Improved/Expected Behavior:
A user loads a new photography asset into AEM Assets that has a recognizable face in it. The user uploads a PDF version of a model release from the person whose likeness appears in the image, and from the original image, creates a relationship type of "Other" from the image to the PDF model release. Future viewers of the image asset see a relationship type of "Other" and need to rely on the asset title of the model release, or viewing the model release itself, to understand if there is a release related to the photo.
Environment Details (AEM version/service pack, any other specifics if applicable):
Thanks for reaching out and proposing the idea. We would need some more details on the use case to see the behavior at our end before qualifying the request. Could you please share the detailed steps to see the above behavior on the out of the box AEM system with the expected and experienced behavior.
@Akash_Kapoor , thank you for the update, I realize I entered the wrong information in the Improved/Expected Behavior section. I can't update the original request, so I will enter it here.
Improved/Expected Behavior: A user loads a new photography asset into AEM Assets that has a recognizable face in it. The user uploads a PDF version of a model release from the person whose likeness appears in the image, and from the original image, creates a relationship type of "Release" from the image to the PDF model release. Future viewers of the image asset see a relationship type of "Release" and it is clear in the user interface that the asset linked under the header of "Release" is a model release.
