Details

    • Release notes required:
      Yes
    • Sprint:
      Basel 139
    • Story Points:
      3
    • Magnolia Release:
      5.6.6

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response: