Page MenuHomePhabricator

Category pages should expose the timestamp sort option
Open, LowPublicFeature

Description

Author: gryllida

Description:
str:

  1. visit https://en.wikipedia.org/w/api.php?action=query&list=categorymembers&cmtitle=Category%3APages%20with%20script%20errors&cmprop=title%7Ctimestamp&cmlimit=500&cmsort=timestamp&cmdir=desc&format=xml
  2. visit https://en.wikipedia.org/wiki/Category:Biology

expected result:

  1. category page exposes options to sort by either timestamp and by sortkey

actual result:

  1. category page only allows to sort by sortkey

Version: unspecified
Severity: enhancement

Details

Reference
bz70819

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:59 AM
bzimport set Reference to bz70819.
bzimport added a subscriber: Unknown Object (MLST).

[The ticket does not describe a bug but a request for additional functionality. Hence setting priority to "enhancement".]

Sounds like a WONTFIX, this is what CategoryTree or DynamicPageList are for. Maybe move in the component of either, to offer an in-category interface as well?

Semi related to bug 69417.

I think exposing an interface would make sense if we already have an interface for multiple collations. Thus I'm going to mark this as being dependent on bug 44667. I'm not overly a fan of making competition interfaces for how to sort a category, so I'd like to simply add it to the options for multiple collations. (OTOH, it appears that multiple collation support is a bit "stuck" right now).

Use case wise: There's lots of use cases for maintinance categories on wikipedia, as well as certain categories on commons (e.g. The uploaded by mobile web category, it would be useful in order to get an idea of latest uploads by mobile).

gryllida wrote:

Nemo said

Sounds like a WONTFIX, this is what CategoryTree or

This does not appear to be able to sort by time.

Nemo said

DynamicPageList are for.

DPL does not scale for big wikis. This could or could not change with the help of Wikidata, I dunno.

Even if DPL scalability gets fixed, I can see many people using categories for maintainance tasks, -- and manually placing a DPL tag on /all thousands/ of categories doesn't appear to make sense to me.

Bawolff said

... would make sense if we already have an interface for multiple collations

Sorry, I'm not sure what a "collation" *is*. I have no idea on the implications here.

I suppose implementing this bug might involve extra prefs for user's preferred default mode for viewing categories.

Bawolff said

... would make sense if we already have an interface for multiple collations

Sorry, I'm not sure what a "collation" *is*. I have no idea on the
implications here.

Collation is fancy word for "way to sort something". Liangent was working on a thing to allow categories to be sorted multiple different ways (The "chinese-collation" branch). I'm not really sure what the status of that work is now, it seems stalled, but if we're doing that, it seems like tacking sort by date on to that work makes sense (Even if on the backend its implemented totally differently). [I should note: I say this without looking at the code and only vague memories of how the chinese collation stuff would look like]

One potential complicating factor, is that sort by date is only efficient if we don't separate out into three separate sections for subcats, pages, and files (due to current db indexes), which might complicate an interface.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:12 AM