Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27034

Improve the 'ezobjectrelation' content type search UI, so that searches are made by content_id instead of location_id

    Details

      Description

      Use case:

      • There is a problem with search under content of type 'ezobjectrelation';
      • It is looking for location, not content;
      • Now, there is small problem with it, as "text" copy field that is used to search text on is only existent in content type solr documents (document_type_id=content);
      • So it looks like this is being solved by using the document structure (content is parent locations are children) and query similar to this one is used:

      q= {!lucene}{!child of='document_type_id:content' v='document_type_id:content AND (text:(John Smith))'}
      fq={!lucene}((document_type_id:"location") AND (meta_indexed_is_main_translation_b:"true") AND *:*)
      

      • Unfortunately, using `child` query parser stops solr from calculating the score making everything 0 and equally good resulting in mixed up results perceived by editors;
      • Maybe the simplest way is to change this to work like the main search and search for content, not for location.

        Issue Links

          Activity

          Hide
          André Rømcke added a comment - - edited

          Actually this is reported wrong, the issue here is that UDW Search Widget should use content query and not location query so results when using Solr is returned in proper ranked order by score.

          Score is not supported when doing location query yet in SolrBundle, and won't for quite some time. However UDW is used for many use cases, some where location id should be returned, so we might not be able to change this to use content search as it might have a negative effect on location use cases. TBD.

          Show
          André Rømcke added a comment - - edited Actually this is reported wrong, the issue here is that UDW Search Widget should use content query and not location query so results when using Solr is returned in proper ranked order by score. Score is not supported when doing location query yet in SolrBundle, and won't for quite some time. However UDW is used for many use cases, some where location id should be returned, so we might not be able to change this to use content search as it might have a negative effect on location use cases. TBD.
          Hide
          André Rømcke added a comment - - edited

          Closing as duplicate of EZP-26775, please watch that issue for further updates.

          Once documentation anyone interested in trying to test it out can test the current v1.3.0-alpha tag prior to 1.9 release in April. Will also look into making Solr Bundle 1.3 work with version 1.7LTS as reported here.

          Show
          André Rømcke added a comment - - edited Closing as duplicate of EZP-26775 , please watch that issue for further updates. Once documentation anyone interested in trying to test it out can test the current v1.3.0-alpha tag prior to 1.9 release in April. Will also look into making Solr Bundle 1.3 work with version 1.7LTS as reported here.
          Hide
          André Rømcke added a comment - - edited

          To add more info here this is an issue in Solr in it's block join implementation, which is solved in later versions.

          While we could have changed Universal Discovery Widget Search (which is what the component with this issue, despite what this jira issue is describing), this is also used in cases where we actually need the location back, hence it needs to do location search, hence why we solve this by instead rolling out a new SolrBundle 1.3 with Solr 6 support.

          Show
          André Rømcke added a comment - - edited To add more info here this is an issue in Solr in it's block join implementation, which is solved in later versions. While we could have changed Universal Discovery Widget Search (which is what the component with this issue, despite what this jira issue is describing) , this is also used in cases where we actually need the location back, hence it needs to do location search, hence why we solve this by instead rolling out a new SolrBundle 1.3 with Solr 6 support.

            People

            • Assignee:
              Unassigned
              Reporter:
              Nuno Oliveira (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: