Project

General

Profile

Actions

bug #9966

open

Search order in advanced search not correct

Added by Andreas Müller 11 months ago. Updated 5 months ago.

Status:
In Progress
Priority:
Priority14
Category:
cdm-dataportal
Target version:
Start date:
04/19/2022
Due date:
04/30/2022 (about 9 months late)
% Done:

10%

Estimated time:
5:00 h
Severity:
critical
Found in Version:
Tags:

Description

ERS:

Das ist die nicht-alphabetische Ausgabe der Search results in der advanced search (also bei Setzen eines Geo-Filters). Es ist eine sehr häufige Anforderung, dass man z. B. die Arten einer Gattung in einem bestimmten Areal sucht.

Ich suche z.B. nach Arten der Gattung Brassica auf Sizilien:

Im Berlin-Model kriegt man dann eine schön sortierte Liste, die man sogar ausdrucken kann:
https://ww2.bgbm.org/EuroPlusMed/RegionalTaxon.asp?PTNameFk=14195&Name=Brassica&PTRefFk=7200000&Region=683&AreaFk=&Print=1

In der Plattform dagegen eine unsortierte Liste, die gerade bei etwas größeren Gattungen nur wenig nützt, weil man nichts mehr findet:
https://europlusmed.org/cdm_dataportal/search/results/taxon?ws=portal%2Ftaxon%2Fsearch&query=Brassica&form_build_id=form-KP34ii2zjTu8VUIf8_y5Iag8oy55fkUXClwmqc820IE&form_token=CZ3tAXLR_ajab1qBspOIC_bdAaYKdnIq3uxiqe23i5A&form_id=cdm_dataportal_search_taxon_form_advanced&search%5BpageSize%5D=25&search%5BpageIndex%5D=0&search%5Bareas%5D%5Bareas_filter%5D=Sici&search%5Bareas%5D%5Barea%5D%5B0%5D%5Bdb1facf2-58a5-483e-9b2a-eb4290ca1b71%5D=db1facf2-58a5-483e-9b2a-eb4290ca1b71&search%5Btree%5D=314a68f9-8449-495a-91c2-92fde8bcf344&search%5BdoTaxa%5D=1&search%5BdoSynonyms%5D=1

(die inhaltlichen Unterschiede bitte nicht beachten, wurde mittlerweile stark verändert).

Ich denke, das kann doch nicht so schwierig sein, die Ergebnisse auch einer advanced search alphabetisch zu sortieren, weil doch bei der einfachen Suche in der Plattform auch eine alphabetisch sortierte Liste herauskommt (der entsprechende Programmiercode also bekannt sein müsste, wie ich laienhafterweise annehme?):
https://europlusmed.org/cdm_dataportal/search/results/taxon?ws=portal%2Ftaxon%2Ffind&query=Brassica&form_build_id=form-3C9wUHyQOMKOHwlK1LcHWz2xldBtTOk0IPRoMkbo9eg&form_token=q8cLoeokwFEZcTeh6KVVRil7w7i-az91aYHwcvy6qOM&form_id=cdm_dataportal_search_taxon_form&search%5BdoTaxaByCommonNames%5D=&search%5BdoSynonyms%5D=1&search%5BdoTaxa%5D=1&search%5BpageSize%5D=25&search%5BpageIndex%5D=0


Related issues

Related to EDIT - feature request #7158: Add pro parte misapplied name to the concept relationship typesFeedbackAndreas Müller

Actions
Actions #1

Updated by Katja Luther 11 months ago

The lucene search uses the OrderHint NOMENCLATURAL_SORT_ORDER, which sounds good, but at the end the id is used for ordering. We need an implementation similar to the "order by rank and name"

Actions #2

Updated by Andreas Müller 11 months ago

  • Due date set to 03/22/2022
  • Start date set to 03/11/2022
Actions #3

Updated by Andreas Müller 11 months ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10
Actions #4

Updated by Andreas Müller 10 months ago

  • Estimated time set to 5:00 h
Actions #5

Updated by Andreas Müller 10 months ago

  • Due date changed from 03/22/2022 to 03/31/2022
  • Priority changed from New to Highest
  • Start date changed from 03/11/2022 to 03/25/2022
  • Severity changed from major to critical

This ticket is not so much related to the current milestone so I move further to next week. Maybe we have to think about moving it fully to the performance milestone 5.33 if there is no time left for fixing now. However priority is high and same with severity

Actions #6

Updated by Andreas Müller 10 months ago

  • Related to feature request #7158: Add pro parte misapplied name to the concept relationship types added
Actions #7

Updated by Andreas Müller 10 months ago

  • Assignee changed from Katja Luther to Andreas Müller
Actions #8

Updated by Andreas Müller 10 months ago

  • Due date changed from 03/31/2022 to 04/30/2022
  • Target version changed from Release 5.31 to Release 5.32
  • Start date changed from 03/25/2022 to 04/19/2022
Actions #9

Updated by Andreas Müller 6 months ago

  • Priority changed from Highest to Priority14
Actions #10

Updated by Andreas Müller 6 months ago

  • Target version changed from Release 5.32 to Release 5.33
Actions #11

Updated by Andreas Müller 5 months ago

  • Target version changed from Release 5.33 to Release 5.36
Actions

Also available in: Atom PDF