search

eXtensibleCatalog / Drupal-Toolkit

The eXtensible Catalog Drupal Toolkit
0 stars 0 forks source link

Search results order - in search A-Z author order, what happens after there are no authors #363

Open patrickzurek opened 7 years ago

patrickzurek commented 7 years ago

JIRA issue created by: rcook Originally opened: 2011-03-10 07:26 PM

Issue body: (nt)

This issue has attachments associated with it (external links): Secondary Sorts in Drupal Toolkit.docx sortoption-edit.png sortoption-list.png sortoption-reorder.png

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-03-10 07:28 PM

Comment body:

Not all search results have authors. Need to decide what to do with the order of the results next. I think it should jump to Alpha by Title at that point.....right now there is no apparent order.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-03-22 06:14 PM

Comment body:

Secondary sort will be Title...so that same author will then sort the works by titels. All the things with no authors would come at the end and be sorted by title.

Jennifer (as Dave) will define primary and secondary for all search. then comes back to Peter.

patrickzurek commented 7 years ago

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-03-22 07:22 PM

Comment body:

[JB] - attaching document that shows this.

patrickzurek commented 7 years ago

JIRA Comment by user: pkiraly JIRA Timestamp: 2011-03-22 08:08 PM

Comment body:

There is one question the document doesn't cover: is there something we have to show to the user from the secondary sort? I mean: the list he currently use contains only the primary sort order, do we diplay the secondary one?

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-09 08:39 PM

Comment body:

No, that should be in the documentation (and probably configurable by institution). Let's not change anything in display at this point, just do the primary and secondary sorts as Jennifer defined.

patrickzurek commented 7 years ago

JIRA Comment by user: pkiraly JIRA Timestamp: 2011-05-19 01:59 PM

Comment body:

I have created an admin UI to create the sort options. Here I atteched some screenshots. After I updated on the actual demo site, it came out, that Solr was changed in this aspect: it is impossible to sorting by multivalue fields. Multivalue fields are those, which can have more than one instance in the same document. Unfortunatelly except the identifier type fields, all fields are multivalue in DT (since technically it was working in 1.4.1). The consequence: currently most of the sort options are not working.

There is a solution, although it requires some more work. We can create a new field type, which would be a single value, and stores whole phrases. After the admin selected the fields to index, and created the facets, he can select from this list of fields, which ones could be used in sorting. This selection would based on checkboxes like this one:

[x] dcterm:title [ ] xc:author [x] facet:author_contributor ...

The DT would store this list, and when transforms metadata into Solr document, it iterate over these fields, and by duplication of the value of the selected ones it creates a sortable pair of that fields, like

dcterm__title_s (the Solr field name of the original field) -> dcterm__title_sortable (the Solr field name of the sortable field)

In some conversations about this topic, Solr gurus suggested that it worth creating two fields one for min value and another one for max value, and using them separatelly in A-Z and Z-A ordering. According to this, we shouly contain all values (like all authors), and order them, and select the first/last as author_contributor_min_sortable and author_contributor_max_sortable. E.g. we have a book writen by "Ilf" and "Petrov" (note: translated by Kostya), the author_contributor_min_sortable field's value will be "Ilf" and author_contributor_max_sortable field's value will be "Petrov". There is possible another solution, where the first field instance will be the value of the sortable field, and we doesn't make distinction between min and max.

What is your opinion about this problem?

patrickzurek commented 7 years ago

JIRA Comment by user: dlindahl JIRA Timestamp: 2011-05-21 11:27 PM

Comment body:

I don't understand, so we will need to discuss this at the next Drupal meeting.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-24 01:50 PM

Comment body:

Per discussion at team meeting on 5/23/2011, we will be proceeding without Author searches at this point. Deferring.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-08-30 04:09 PM

Comment body:

Today, when testing for the demo 3 release, I found that these sort options were still present. Opened issue 815 to limit sort options for demo. Issue 606 is open to make date sort work correctly post demo 3. We will revisit Author searches sometime in the future, as we had noted in this issue when we deferred it.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-08-30 06:24 PM

Comment body:

This is possible future work and is in a deferred milestone. It needs to stay open until we decide we are never going to do anything with it.