Uploaded image for project: 'Magnolia DAM Module'
  1. Magnolia DAM Module
  2. MGNLDAM-667

Fix full text dam search (Assets app)

XMLWordPrintable

    • Yes
    • Basel 139
    • 3

      Currently you can use SearchTemplatingFunctions (searchfn) to search the DAM. The problem is that binary data itself gets stored on a resource sub node. So if I have a PDF and I search mgnl:asset nodes then I cannot find terms that may be located in the binary data itself. That will only search the metadata of the asset node. On the other hand, if I search mgnl:resource nodes then I will not find terms located in the asset metadata.

      Two solutions to the problem could be:

      1. We add a searchAssets() function to the DamTemplatingFunctions (damfn) that considers both levels of data and wraps everything into a single call.
      2. We add another aggregation entry to the indexing_configuration.xml 
        <aggregate primaryType="mgnl:asset”>
    <include primaryType="mgnl:resource”>*</include>
</aggregate>

      In the second method we can then use the SearchTemplatingFunctions since all the data will be aggregated into a single document. The preferred way from an efficiency standpoint.

       

      As a result of the fix, asset search in Assets app works now properly.

        Acceptance criteria

          1. dam-workspace.png
            dam-workspace.png
            34 kB

              fgrilli Federico Grilli
              rgange Richard Gange
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved:

                  Bug DoR
                  Task DoD