Page MenuHomePhabricator

Provide tooling to track event date for new pages
Open, Needs TriagePublic

Description

Following up T397853 the declinedness of which I disagree with

I do not understand technical reason why the proposed extension would not do the job.

Please provide me with the name of another user or group who can fullfill this task.

This is an urgent issue that needed to be implemented a few years ago and is causing burden on volunteers and reducing productivity as they need to track event date manually.

The key requirements are

  1. A user can easily specify event date for a page without needing to edit Json or a table
  2. A list of pages is generated with event date specified for each page and optionally a comment
  3. Event date tag can be removed easily, as the pages which were reviewed and approved no longer need to be listed in output for item 2
  4. Tool should be available for all, ideally without JavaScript

Hope you can assist.

Many thanks.

Event Timeline

I can understand your frustration @Gryllida — but I'm not sure that demands for highly specific custom tools are going to go down particularly well.

Bugreporter2 raised the priority of this task from High to Needs Triage.Oct 11 2025, 12:00 PM

The onus of addressing the request and finding suitable tool is now on you.

@Gryllida: No, it is not. MusikAnimal already wrote in T397853#11266110 that they are "sorry I am not able to assist with this further!" and was even kind enough to provide hints how to approach an alternative implementation.
Nobody is obliged to get involved in implementing your vision of how something should work unless you signed a contract with each other.
Putting pressure on people is not welcome. Please refrain from such comments and see https://www.mediawiki.org/wiki/Phabricator/Etiquette if you would like to be active here.

If you don't wish to do this or are not available,

MusikAnimal already wrote in T397853#11266110 that they are "sorry I am not able to assist with this further!"

please provide me with the name of another user who can fullfill this task.

That's up to you. Feel free to check https://www.mediawiki.org/wiki/Communication for venues where you could potentially bring this up.

I'm closing this ticket as it targets a specific individual who already explicitly stated they cannot assist with this. For future reference, please use the feature request form (linked from the top of the task creation page) to create feature requests, and fill in all the sections in the template. Thanks.

@Aklapper - there is consensus that was created on wiki to get Page Assessments installed - I require a replacement contact and tool for it is not my personal wish

Gryllida assigned this task to Aklapper.

Link to consensus

https://en.wikinews.org/wiki/Wikinews:Water_cooler/technical/archives/2025/June#Propose_to_install_Page_Assessments_extension_at_this_wiki

Please advise where to find replacement tool. This request needs to be addressed. I am going to rephrase it as per your request but it needs to stay open until fixed.

Apologies to @MusikAnimal for wording the task too specific and I request that some resource is provided when consensus derived requests are declined

Thanks for your time

Thanks

Gryllida updated the task description. (Show Details)
Gryllida updated the task description. (Show Details)
Gryllida removed a subscriber: MusikAnimal.

Done editing, sorry for the noise. Will probably be back on Friday or so.

Gryllida assigned this task to Aklapper.

@Gryllida: You have been warned more than once not to assign tasks without consent and to respect the Phabricator Etiquette.
Consider this your last warning.

@Aklapper - there is consensus that was created on wiki to get Page Assessments installed - I require a replacement contact and tool for it is not my personal wish

See https://meta.wikimedia.org/wiki/Limits_to_configuration_changes . There is nothing to "replace" if nothing was in place before.

See the header of that page pointing to https://meta.wikimedia.org/wiki/Tech instead.

Please avoid spamming random individuals for no good reason.

  1. What limit is being a problem here?
  1. Posted https://meta.wikimedia.org/wiki/Tech#Tool_to_get_a_wiki_Page_tagged_for_a_custom_date
  1. I can elaborate about the reason for that choice on-wiki
  1. For example Changes to use unsupported technologies, or abuse them in unsupported ways. The point I was trying to make though is that community consensus does not imply that changes will take place as requested.

I appreciate you being verbose about the rule

Noting that PageAssessments special page is "supported" and reading it is a "supported way" and I am not convinced what was the whole point of the declination given that extension is used on thousands of pages at enwp, while it is proposed to use it at less than 100 pages here.

Noting that I was asking for replacement a dozen of times and was not advised.

I have requested assistance on-wiki that another user proceed to push this forward and I need to step away. I am way too frustrated by this to continue productively. Hope you hear from someone else soon.

I am not convinced what was the whole point of the declination

See the content of the task which you linked in this task description, and the conversation in this task.

I think the main problem with this task is that people (at least I have) have a hard time following what the end result is and what @Gryllida is trying to accomplish. What I was able to understand from the message was that this sounds like a problem that could be solved with DynamicPageList and templates already. DPL is installed on Wikinews and widely used.

@Zache Hi, I do not see how DPL can help to tag a page with an event date. Often, it is a day or two before the wiki page was even created. DPL has no knowledge of that.

Yeah, i still think that you should do much clearer explanation about the feature what you would need and how it should work so other people understand what you would like to accomplish. Currently you wont get any useful answers because people wont understand you.

Yeah, i still think that you should do much clearer explanation about the feature what you would need and how it should work so other people understand what you would like to accomplish. Currently you wont get any useful answers because people wont understand you.

Well, that, any like on Wikipedia communities, you need to be very polite as people pay more attention to the etiquette violations than the request.

Even then, some people will close valid requests and not understand things that have been very carefully explained to them.

This probably should be filed to MediaWiki-extension-requests — but the request needs to be very specific about what you want it to do.

I've taken a look at this, and it's much messier then it logically should be. First off, DynamicPageList by itself can't do this because DPL leaves no way to postprocess its output (not even by Lua; Lua only sees it as an opaque strip marker). So the only formatting options you have for DPL-formatted lists are those the extension itself gives you, which aren't useful here, or those you construct yourself from multiple DPL lists.

If you didn't need to have comments in addition to the date then you could revert @Michael.C.Wright's edit here https://en.wikinews.org/w/index.php?title=Template:Date&diff=prev&oldid=4878292, which would cause articles pending review to be in date categories, and then make a boatload of dynamic pages lists of each page in both the date category and "Category:Review". Or you could create a separate "date drafts" tree and either let them be red (DPL probably won't care) or have twice the manual work creating them. Neither of these are optimal, and this can't add any more metadata because of the exponential growth of separate lists.


If we had T199126, then this step would be much easier, and you could proceed with just getting each relevant article and running some sort of parser on it to decode whatever data you want to smuggle in, and, with MediaWiki as currently coded, the only option if you want to go further than this is to write a bot that uses the API to generate a report itself, which is unideal (and more manual work keeping it running et al. -- I'm not volunteering)


What you really want here, though, isn't that category abuse that I just described but the "page properties" functionality and then you could use https://en.wikinews.org/w/index.php?title=Special:PagesWithProp to read it out. Probably because of its obscurity, there's no code that lets you write custom properties to page_props, and none of the existing properties seems abusable for this purpose, so that, while close, is another non-starter.


I personally (and futilely) wish that we abandoned the culture of Phabricator stifling wikis' attempted innovations and moved much closer to one in which wikis could elect their own sysadmins, with all that entails. But we're nowhere near that point, and not heading any closer to it, and so it goes.

Good input @Pppery

I agree the ability to add custom tags to pages would be useful. The tags could be defined in a MediaWiki namespace definition page, giving flexibility to individual wikis to decide what tags they want.

This does have parallels to MediaWiki-extensions-Disambiguator (which adds the __DISAMBIG__ magic word), and a separate proposal I've made for tagging redirect pages as “bad” for being misspellings or misnomers (T393668: Extension to create magic word for bad redirects).

Things I have understood so far:

  1. Reviewers will be able to set the event date and a short comment for an article.
  1. This information will be stored on a JSON page.
  1. Reviewers can change the date or comment later if they want.
  1. A report page will be generated, listing all articles along with their event dates, comments.
  1. Published articles will not have this tag.

N.b. may not be limited to reviewers only (items 1 and 3)

We already has multiple extensions that can do such things: Semantic MediaWiki, Cargo and VisualData. The first two have more features (event date and short comment can simply set by templates) but are not suitable for Wikimedia wikis, since they may create infinite number of new database tables. The last one has more potential, though setting data needs a dedicated interface.

In Wikimedia the intended method to manage structured data is via Wikidata, but (1) it does not support on-wiki query for now; (2) it does not handle project-internal data.

First off, DynamicPageList by itself can't do this because DPL leaves no way to postprocess its output (not even by Lua; Lua only sees it as an opaque strip marker).

This is why there is https://www.mediawiki.org/wiki/Extension:DynamicPageListEngine, a Lua-integrated version of DPL. Previous attempt to deploy it is at T90573: Review and deploy DynamicPageListEngine.