Capture digital rights management with asset's intention of use from user as textfield | Adobe Higher Education
Skip to main content
Rohit_Utreja
Community Advisor
Rohit_UtrejaCommunity Advisor
Community Advisor
August 21, 2023
Répondu

Capture digital rights management with asset's intention of use from user as textfield

Hello,

 

We are working on a use case where we have to capture 'intention of use' when a user is trying to download assets from AEM assets and Adobe Brandportal.

Is there any way to capture 'intention of use' as an input from a user when downloading?

There are some open questions related to the same?
1. How to add a form field(textfield) to capture 'intention of use'?

2. How to handle the data captured during this process?

 

Ce sujet a été fermé aux réponses.
Meilleure réponse par Adilos-Cantuerk

@adilos-cantuerk  thanks a lot for sharing these details. I appreciate it.

If I have to give a textfield inside the value of 'adobe_dam:restrictions.' such as below (along with copyright information)
<input type="text" id="fname" name="./fname" value="John DDOE"><br>

How to save the value of this textfield and reflect it within Download report?
any clue?

 

TIA,

Rohit


I don't know how to do that.
I am very interested if you do get this to work and how you did it, in case you figure it out.
I fear that this might be best archieved outside of AEM, since i do not know if it is possible to get the info from Brandportal back into AEM.

The current Copyright Management Page is best to tell a user that he has to use it in a certain way, but does not give any feedback to the company other than did the user clicked on "agree" - because otherwhise he could not have downloaded the asset. Maybe it is possible to add more options here, but i don't know how you would write the info back into the asset.

Even if you create a html within adobe_dam:restrictions, that somehow disables the download button within the copyright management page unless the user first selects his choices and then creates a report based of the URL of the current copyright management page - make the html in a way that the "Agree" selector is disabled until the user selects and comfirms his selection - (Use for online marketing) - (use for print) (5k Flyers) - To have this info and his user ID written  - into the asset, in another multi value property, for example./jcr:content/metadata/LicensedUse  Or something like that, might be possible. BUT then you would have to find a way to get this  from Brandportal back into AEM without overwriting the other entries.

1 commentaire

Adilos-Cantuerk
Community Advisor
Adilos-CantuerkCommunity Advisor
Community Advisor
August 21, 2023

This might be relevant - but it is possible to add adobeDAM:restrictions as a text field into an asset.
This will then gets displayed within AEM and Brand Portal in the copyright management page.
This allows the corporation to describe to a user in which way the asset is allowed to be used - but it does not give feedback to the corporation. 

Sadly this does not apply for licenses (xmpRights:WebStatement) since they are located in AEM - and they do not transfer into Brand Portal. 

    Rohit_Utreja
    Community Advisor
    Rohit_UtrejaCommunity AdvisorAuteur
    Community Advisor
    August 21, 2023

    thanks for your response @adilos-cantuerk 

    As per the documentation, 

    • The value of the asset metadata property adobe_dam:restrictions is a raw HTML that specifies the license agreement.

    If we add texfield with adobe_dam:restrictions, where and how this value will be saved in AEM?

    Could you share some details on that if possible?

      Adilos-Cantuerk
      Community Advisor
      Adilos-CantuerkCommunity Advisor
      Community Advisor
      August 22, 2023

      Hi @rohit_utreja ,

       

      of course. I gladly share my experience with the matter.
      adobe_dam:restrictions will be saved within the asset itself, under metadata.

       

      Since this information is saved within the asset - this will work with AEM as well as with Brand Portal.
      The other thing in the documentation gives me trouble atm. 
      We would like to use xmpRights:WebStatement.

      But there is no way to move the licenses from the Production enviroment over to the brand Portal.
      I do not want to hijack this thread with my struggles, but if you are interested - i have another ticket open for that. 
      In case you want to have a look 

       

        Conditions d'utilisationAccessibility statement

        Loading footer...