search

eXtensibleCatalog / Drupal-Toolkit

The eXtensible Catalog Drupal Toolkit
0 stars 0 forks source link

Date Sort - make work correctly #330

Open patrickzurek opened 7 years ago

patrickzurek commented 7 years ago

JIRA issue created by: rcook Originally opened: 2011-05-23 04:05 PM

Issue body: (nt)

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-23 04:07 PM

Comment body:

With the upgrade to Solr 3.1, the multi value sort options we previously had no longer work.

Jennifer to supply input to Peter on now to make the Date facet work.

Per discussions at team meeting today, we mostly likely will defer Author and Tilte searches.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-23 07:22 PM

Comment body:

So, it sounds like we want this:

Three sorting options:

1) Relevance 2) Date (newest to oldest) 3) Date (oldest to newest)

We would not offer any other sorting options at this time.

So we want Peter to implement a mechanism that allows us to sort by the muti-valued date field (which Peter said he could do, by creating a new field). In cases where there are multiple dates in a single record (which will rarely happen), the Drupal Toolkit can just use the first date it finds.

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-24 02:22 PM

Comment body:

Below is copied from Email thread.

Yes, the admin ui to select the date field is good.

Like we discussed, the ability to display items with multiple authors is not possible in the way you described it yesterday (filing the titles in multiple places in the results list). It is only possible in the two ways peter described, and I then summarized in the meeting yesterday, and only with additional work.

I do not think it is worth any of Peter's time to build an author sort given other items on his plate. We have more work to do to determine how we want it to work and whether we can make it work in a useful way before we use developer time on it.

On May 23, 2011, at 4:14 PM, Bowen, Jennifer wrote:

Yes, I’ll look at the date fields and make sure those are the ones we need.

I like the idea of setting up the Admin UI – would this approach allow us to handle multiple authors as well? That’s the way I interpret Peter’s note. Although that could be something we add later.

From: Lindahl, David Sent: Monday, May 23, 2011 3:32 PM To: Kiraly, Peter Cc: Bowen, Jennifer; Cook, Randall Subject: Re: date sorting

I think jennifer needs to answer the question about which of the two date-like fields to use: dcterms:date or dcterms:issued

I do not think you need to collect information about records with multiple date fields.

On May 23, 2011, at 2:31 PM, Péter Király wrote:

1) How much time will it take Peter to implement this? If we "hardwired" it (without admin UI to select a field to be sortable) it takes 2 hours. With admin UI it takes 4-6 plus hours, but the result will work with any fields, not just dates.

2) Are there any unresolved issues that Peter has - Peter do you have any questions for us? Yes: 1) do you want DT to collect information about the records with multiple date fields? 2) which field we are talking about. We have two date-like fields: dcterms:date, and dcterms:issued.

Péter

patrickzurek commented 7 years ago

JIRA Comment by user: rcook JIRA Timestamp: 2011-05-25 06:51 PM

Comment body:

Jennifer and I want to check what the DT will do if it encounters multiple values for the dcterms:issued field. Please advise via email when you work on this.

Copy from email.

The only date field that we are populating from MARC records right now is dcterms:issued. As I said in my earlier email, it is possible that a record might have more than one instance of this field.

Since the XC Schema contains all DC elements and properties, there are a bunch of other dcterms date fields that are valid in the schema: date available created dateAccepted dateCopyrighted dateSubmitted modified valid

As soon as we start dealing with DC data we will start seeing records with these data elements populated coming through. 'date' is the one we'll see first since that is in oai_dc.

I think ideally we would want to configure Drupal such that it looks for data in one data element and uses that for the sort element; if that date isn't present, it looks for a different data element, then another -- and that a library could configure this.

If I understand things correctly, this is still possible, but the problem is when there are two instances of the same field, right? In that case would we want it to choose the first one it finds?

patrickzurek commented 7 years ago

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

Comment body:

Issue 815 added to limit sort options for demo 3 release. This issue is to make the date sort options work correctly (post demo 3 release).

patrickzurek commented 7 years ago

JIRA Comment by user: pkiraly JIRA Timestamp: 2013-06-20 04:39 PM

Comment body:

What is missing right now is to use alternative fields for the sorting. Now we can select which fields we want to make sortable, and DT generates two special fields for each of them for the minimal and maximal value. For example: if there are multiple dates in a record, the date_min will be the smallest date value, and date_max will be the largest one. But both date_min and date_max based on only one metadata field: date. The suggested change is that these sortable fields should be based on multiple, alternative metadata fields.

It requires the following input fields in admin UI:

Requirements in indexing time: