Ticket #758 (closed enhancement: fixed)

Opened 11 months ago

Last modified 4 months ago

browseIssue.action and getFeed.action - article order

Reported by: rich Assigned to: alex
Priority: medium Milestone:
Component: ambra Version: 0.8.2-SNAPSHOT
Keywords: browseIssue Cc:
Blocking: Blocked By:

Description

The article order in the ToC should be by date published, then by DOI. Also need the same ordering in browse.action.

Dependency Graph

Change History

01/14/08 10:57:18 changed by russ

in case any clarification is needed:

the browseIssue page is currently grouped by article type.

the article type groups are ordered in config.

within each article type, articles should be ordered by pub date, then by doi (alphabetically)

this ordering should be the default (browseDate and browseSubject pages, as well as the feed, should follow these rules too). i'm not sure if this ticket needs to be broadened or if we need multiple tickets for this...

02/04/08 17:46:33 changed by rich

  • priority changed from medium to critical.

02/05/08 12:13:35 changed by alex

The "browse by" functionality orders articles by date, then description. Do we really want to change this functionality? I'd like to verify... Why do we want to order by DOI? I feel that DOI should not play a role in the external behavior or requirements of the PubApp?.

02/06/08 11:41:05 changed by alex

  • owner changed from alex to russ.

I've added ordering to the BrowseIssue? TOC and have updated the OQL queries used in BrowseService? to 2nd-order sort by article DOI.

Rich suggested that I assign back to Russ to verify if the RSS feeds are generated by a script, and if so to check the queries in those scripts. Please see my changes to #4640 in BrowseService? for the OQL query update.

02/08/08 13:20:52 changed by russ

  • owner changed from russ to alex.
  • summary changed from browseIssue.action - article order to browseIssue.action and getFeed.action - article order.

feeds are not generated by a script, but rather by getFeed.action:

it looks like the relevant file to modify is

plos\webapp\src\main\java\org\plos\article\action\ArticleFeed.java

around line 285...i'm not quite comfortable making this change, as the OTM query is being generated differently than in browseService.java...

02/11/08 16:09:11 changed by rich

  • priority changed from critical to medium.

02/19/08 10:09:26 changed by alex

(In [4743]) re#758 merge r4711 from head. This allows us to create criteria based on the "id" of the OTM object.

02/19/08 10:12:24 changed by alex

  • status changed from new to closed.
  • resolution set to fixed.

(In [4744]) fixes #758 - Added search result secondary ordering criteria to sort by "id" ascending.

03/20/08 17:32:08 changed by alex

(In [5070]) Recorded merge of revisions 4743 via svnmerge from http://gandalf.topazproject.org/svn/branches/0.8.2.1

........

r4743 | alex | 2008-02-19 10:09:25 -0800 (Tue, 19 Feb 2008) | 1 line

re#758 merge r4711 from head. This allows us to create criteria based on the "id" of the OTM object.

........

03/20/08 17:47:21 changed by alex

(In [5071]) Merged revisions 4744 via svnmerge from http://gandalf.topazproject.org/svn/branches/0.8.2.1

........

r4744 | alex | 2008-02-19 10:12:24 -0800 (Tue, 19 Feb 2008) | 1 line

fixes #758 - Added search result secondary ordering criteria to sort by "id" ascending.

........

07/16/08 11:01:22 changed by

  • milestone deleted.

Milestone pubApp_0.8.2.1 deleted