Ticket #1085 (closed task: fixed)

Opened 12 years ago

Last modified 12 years ago

Support sort on column headings

Reported by: mpritcha Owned by: sdonegan
Priority: critical Milestone: MEDIN
Component: discovery Version:
Keywords: discovery medin Cc:

Description (last modified by mpritcha) (diff)

Should be possible to support ordering by any column in the discovery index. Assuming new columns (for searches of specific to enable searches against specific MEDIN elements) are already defined, this task requires:

  • check that required ordering field is supported in discovery index
  • update orderByList to reflect additional orderByField
  • update search code to implement ordering by this field

(should not require change to WSDL unless considering multiple order-by (e.g. order by field 1, then by field 2)

To clarify : current system allows specification of required order-by column in the search request. The client currently supports re-ordering of results only by re-submitting the search request with a different order-by field (not client-side manipulation of the result set, which has been avoided for performance reasons. It is possible, however, to request the entire result set and to implement code for client-side maniuplation of the result set ...but this would be a portal issue).

Will look at altering search and present responses to provide additional (specified?) elements to represent fields from the discovery index. E.g. Current search response is just a list of document ids. Could be extended to contain abstract, start, end dates, bounding boxes, etc., for an "intelligent" client to do what it wants with.

Change History

comment:1 Changed 12 years ago by mpritcha

  • Priority changed from blocker to required
  • Type changed from defect to task
  • Description modified (diff)

comment:2 Changed 12 years ago by mpritcha

  • Priority changed from required to critical
  • Description modified (diff)

comment:3 Changed 12 years ago by sdonegan

  • Status changed from new to assigned

The Discovery API now supports sending information on the actual ordered field back to the client - in addition to this we have recieved a request to supply extra information in the doSearchReturn documentBrief and documentFull types that match the termTarget list - this functionality enables the client more information as well as the actual ordering metric value to present to the user.

Where required, the client can request full information return as part of the doSearchReturn to allow ordering by the client, but ordered information is still available using the doPresent operation.

comment:4 Changed 12 years ago by sdonegan

  • Status changed from assigned to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.