Remove Insights tab in DAM Asset Meta Data | Community
Skip to main content
V
vsharm
Level 4
April 19, 2018
Solved

Remove Insights tab in DAM Asset Meta Data

  • April 19, 2018
  • 5 replies
  • 5481 views

We are trying to implement custom meta along with some OOTB meta data. Our issue is that the last tab always comes up with the "Insights" tab which our product team does not want. It is coming OOTB but wondering if there is a way for us to hide it. We try looking at the - /libs/granite/ui/components/coral/foundation/tabs which is responsible for rendering the tabs but dont see anything there.

Does anyone know if it is possible to remove/customize the "Insights" table? We are using AEM 6.3.

Thanks,

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by vsharm

Overlay solution did not work because the configuration are under /config folder in aem 6.3. If it was under /app or /etc then we could have used overlay.

We created a separate clientLib with the categories as - categories="[dam.gui.coral.metadataeditor,granite.ui.coral.foundation]"/> and added our custom javascript which will loop through and hide the insights tab something like -

$( document ).ready(function() {
   var dataElements = document.querySelectorAll('[data-foundation-tracking-event]');

   for(var i=0; i < dataElements.length; i++) {

   if(dataElements[i].textContent == 'Insights') {
   dataElements[i].style.display = 'none';

  }

  }
});

5 replies

smacdonald2008
smacdonald2008
Level 10
April 19, 2018

As this is not documented - we asked the team to look here.

    khamat_bn
    khamat_bn
    Level 4
    April 1, 2021

    Hi @smacdonald2008  @vsharm ,

     

    is there any documentation or any update available on this ?

      S
      Adobe Employee
      shrotiAdobe Employee
      Adobe Employee
      April 20, 2018

      The Insights form exist at location [0]. Try overlay the form using [1] and hide. If it doesn't work then log a hotfix request to get fix from Product.

      Thanks

      [0] /libs/dam/content/schemaeditors/forms/insights

      [1]Apache Sling :: Resource Merger (org.apache.sling.resourcemerger)

        V
        vsharmAuthorAccepted solution
        Level 4
        April 23, 2018

        Overlay solution did not work because the configuration are under /config folder in aem 6.3. If it was under /app or /etc then we could have used overlay.

        We created a separate clientLib with the categories as - categories="[dam.gui.coral.metadataeditor,granite.ui.coral.foundation]"/> and added our custom javascript which will loop through and hide the insights tab something like -

        $( document ).ready(function() {
           var dataElements = document.querySelectorAll('[data-foundation-tracking-event]');

           for(var i=0; i < dataElements.length; i++) {

           if(dataElements[i].textContent == 'Insights') {
           dataElements[i].style.display = 'none';

          }

          }
        });

          S
          Adobe Employee
          shrotiAdobe Employee
          Adobe Employee
          April 24, 2018

          Then I would consider this as a product bug and overlay extension should work.

          The form under /libs goes to /conf when extended at the project level (Administrator role).

          All customizations needed at a project level for OOTB forms /libs go to /apps. (Solution Integrator role)

          Say at the project level, it is decided to hide Insight Tab so that any user admin can't see when metadata schema is being defined under /conf for the project. Then OOTB form offered from location /libs should be extensible through /apps overlay and further User Administrators can define project level forms under /conf using the merged resource form (/libs + /apps).

          The JS approach works but not elegant as Project administrator can still see Insights under /conf structure.

            S
            Shaheena_Sk
            Level 4
            July 15, 2020
            I am using 6.5, is there any solution to this yet?
              Terms & ConditionsAccessibility statement

              Loading footer...