hbz / nwbib

Die Nordrhein-Westfälische Bibliographie
http://nwbib.de
3 stars 2 forks source link

Improve behaviour when classification notation is chosen #336

Closed acka47 closed 8 years ago

acka47 commented 8 years ago

Reported by H.F. via email on 2016-07-27:

während der Arbeiten am Artikel fielen mir noch zwei Dinge zur Systematiksuche auf. Einmal bricht nach der Anwahl einer Systemstelle die Nutzerinformation über die ausgeführte Suche ab. Könnte man hier analog zu anderen Suchen oberhalb der Treffer die für die Trefferanzeige relevante Systemstelle anzeigen z.B. "Sachgebiet" und dann "402340 Grundrechte"?

Das andere ist die Facette "Sachgebiete" nach Auswahl einer Systemstelle. Hier steht die formale Info, dass man eine Stelle ausgewählt hat, das ist in Ordnung. Dann werden aber stets nach jeder Systemstellenauswahl dieselben Sachgebiete beginnend mit "Geschichte (23307)" genannt. Da man nach Auswahl einer einzelnen Systemstelle die gefundenen Titel allerdings mit anderen Systemstellen nicht weiter einzugrenzen vermag, müssten der Hinweis "1 ausgewählt" eigentlich reichen und die weiteren Hinweise auf Systemstellen entfallen.

acka47 commented 8 years ago

We probably can't implement the first suggestion But we should implement the second point, i.e. when I click on a notation under "Sachgebiete". The checked notation should be the first in the "Sachgebiete" facet. This currently works for some (e.g. s240500) but not for all (e.g. s402340).

Regarding the request to not show the other notations when one is chosen, I will make clear that this actually makes sense with the "or" connection of notations.

fsteeg commented 8 years ago

Deployed to staging, see:

http://test.nwbib.de/search?nwbibsubject=http%3A%2F%2Fpurl.org%2Flobid%2Fnwbib%23s240500

http://test.nwbib.de/search?nwbibsubject=http%3A%2F%2Fpurl.org%2Flobid%2Fnwbib%23s402340

http://test.nwbib.de/search?nwbibsubject=http%3A%2F%2Fpurl.org%2Flobid%2Fnwbib%23s402340%2Chttp%3A%2F%2Fpurl.org%2Flobid%2Fnwbib%23s240000&sort=

For details, see comment in https://github.com/hbz/nwbib/commit/6b2e9932c6feafa83dd9fb833c0c3f46eb90bae3.

acka47 commented 8 years ago

The behaviour is strange when I select a subject directly from a single entry, e.g. for subject "Umsiedlung": http://test.nwbib.de/search?subject=http%3A%2F%2Fd-nb.info%2Fgnd%2F4061614-9: It says "0 ausgewählt" in the subject facet.

acka47 commented 8 years ago

It works for "Sachgebiete", though, e.g. http://test.nwbib.de/search?nwbibsubject=http%3A%2F%2Fpurl.org%2Flobid%2Fnwbib%23s572030.

fsteeg commented 8 years ago

Fixed on staging: http://test.nwbib.de/search (click subject links from detail pages).

fsteeg commented 8 years ago

The changes in this issue are only consistent together with #341 (otherwise the preview numbers in the facet don't match actual results). Moving to backlog.

fsteeg commented 8 years ago

Deployed to staging, see: http://test.nwbib.de/search

Facets support drill down (AND for facet and results), except for type and owner facets (they still use OR).

acka47 commented 8 years ago

Great, this makes so much mor esense for the facets. +1

dr0i commented 8 years ago

I don't like that an owner query works as AND (using multiple values for the paramter) while others will work as OR. Also, it's an API break, even if the API examples site doesn't explicitly mentioned subject comma-separated queries. I for myself already have used the comma-separated subject queries as OR-queries . I would like the queries work all the same. That way it is intuitive to work with the API. Is there a need to break this old behaviour?

fsteeg commented 8 years ago

Deployed to production, closing. See facet behavior at http://nwbib.de/search