(permalink)

I propose to (mis)use this extension here by supplying class
…
and event date as the importance parameter, followed by "G" symbol for international news like "windows died" or "ubuntu 24.4 released" or "L" for regional news, followed by "m" for minor edut required or "M" for major revision, followed by a custom note
…
Like: Class = D

Importance = 2025-05-14 G m add location in first paragraph

I do not think Page Assessments is the right solution for this. What you're proposing would inefficient in terms of storage and could cause performance problems. Both the project and assessment are meant to be one of a small number of finite values.

Page Assessments could be used to provide only the proposed class values, and a dummy value for the project. At that point though, why not just use categories?

@Gryllida: Could you please answer the last comment? Thanks in advance!

Hi @MusikAnimal

I believe page assessments are most useful for pages which are not yet archived. There usually is less than 50. After a news is old, it is no longer editable, and page assessment does not matter. Would this help to address the issue?

Hi @Aklapper and @MusikAnimal

Please see my comment above.

• As noted in it, I believe that using page assessment on newly created wiki pages and then deleting the page assessment tag after the page was archived, will help the performance issues. In that case, page assessment would be required for less than a thousand of pages.

• Although, please also note, that I do not see how this is an issue seeing that Wikipedia has PageAssessments installed and has a lot of pages tagged with it, so based on my limited awareness of the issue I do not believe that scalability is a valid concern. If it is, I would like to get more information about this issue.

Your further action on this would be appreciated.

It's been three workdays only, I'd say no need yet to ping. I myself cannot take further action.

Hi @MusikAnimal and @Aklapper

Please advise how i should proceed. MysikAnimal is or was AWOL.

This is pre req or blocker for the other task

https://phabricator.wikimedia.org/T403330

Your assistance would be appreciated.

Please read my previous comment again.

Sorry for the delay in response, @Gryllida! I have been extremely busy with the day job and this slipped my mind.

I am trying to understand exactly how PageAssessments will help you. Do you have a centralized template or module for displaying assessments? Could you point me to it so that I can review the implementation?

As for the {{#assessment:}} parser function itself, what would you be putting for the "project" parameter? The discussion didn't mention that. The "project" parameter would be required as per the database schema. Also, your example value for "importance" was 2025-05-14 G m add location in first paragraph. This won't fit in the database column. Further down you mention having just "one parameter 'event date' and nothing else". I would need to see exactly how the extension would be used in order to evaluate if it's the right fit. Misusing the extension beyond its intended purpose could cause a number of problems, if not for you as users, then to my team as maintainers.

I believe page assessments are most useful for pages which are not yet archived. There usually is less than 50. After a news is old, it is no longer editable, and page assessment does not matter. Would this help to address the issue?

Yes. That more or less eliminates any concern with storage. How does the archiving process work? I think we'd either need to use the same template that uses the {{#assessment:}} parser function and conditionally call it, or we'd need to be sure the assessment template is removed during the archiving process.

I am not yet convinced however that PageAssessments is the right solution here. Is it just the Special:PageAssessments interface you want (i.e. a table view)? Have you considered using Petscan or other tools to do category intersections?

Hi @MusikAnimal

I anticipate "project" called "eventDate" with an assessment parameter in YYYY-MM-DD format. The special page would show all pages which have the date set. This would help to sort pages by event date and help to prioritise review of pages based on event date.

There is a script to "approve/publish" a page, it can automatically remove the assessment tag.

Does this fully resolve the question? Thank you!

Hi @Aklapper

I am requesting information whom I can ping to take further action please.

Thank you!

No need to ping Andre. I will see any replies. I've got my Phabricator inbox situation figured out now :)

There is a script to "approve/publish" a page, it can automatically remove the assessment tag.

Can you point me to this script?

I also need an answer to this question:

Do you have a centralized template or module for displaying assessments? Could you point me to it so that I can review the implementation?

"No" is a satisfactory answer, but we'll need a working template (minus the {{#assessment]} call) to deploy the extension. I don't want to make you do this work and the extension still doesn't get deployed, but I imagine streamlining the process in this way would be beneficial to the project regardless.

My gut feeling is there's still a more appropriate solution than PageAssessments, but until I have all the technical details, I can't say for sure. In particular, I'm curious why normal categorization does not suffice? You could have categories like 2025-05-14 G m and you still get the same granularity and organization of pages that you're looking for, no? Even with separate categories for the date and assessment, there are tools available that allow you to union them and view it in a table, like Petscan. There's also CirrusSearch (i.e. incategory:"2025-01-01" incategory:"Assessment G" or whatever) which will give you a nice snippet of each article.

PageAssessments was designed more for data consumption than data display. It seems like you are more interested in the latter. For example, there is PageAssessments integration in XTools, Tool-Pageviews, Education-Program-Dashboard and many other tools, gadgets and user scripts. It's also part of CirrusSearch, i.e. you can do searches like inproject:"New York City". This won't work in your case as all pages will have the same project. Similarly, changes would need to be made to XTools and Pageviews Analysis and any other integrations so that they know to ignore assessments on EnWikinews, since we don't have all the things we normally have (such as icons), not to mention the confusing bit of every page having the same project and us referring to it as a "WikiProject". Projects also need a category, so you'd have just a dummy called Category:Eventdate.

All in all, while feasible, using PageAssessments for your purpose feels quite clunky and not worth the headaches it will cause. It would be a "hack" to say the least. Hackiness may be acceptable for scripts and gadgets, but for MediaWiki extensions it is likely to cause unforeseeable problems for both users and maintainers.

Hi @MusikAnimal

I do not have emial notifications sorted out, sorry. Please do ping me in your reply.

https://en.wikinews.org/wiki/MediaWiki:Gadget-easyPeerReview.js is the gadget that can be modified to automatically remove a page assessment tag when a page is approved for publishing.

Do you have a centralized template or module for displaying assessments? Could you point me to it so that I can review the implementation?

I do not understand what this question means. I would be viewing a "Special:PageAssessments" page to see list of pages and their tags.

I couldn't understand the rest of your comment about data consumption or display. I do not know what these other tools do. As Wikinews is a small wiki, I cannot learn the entirety of the software, only the little bit that works for me. This page on testwiki is an example of the output that I would like to be able to view:

https://test.wikipedia.org/wiki/Special:PageAssessments?project=EventDateAndUrgency&namespace=0&page_title=

Please let me know the easiest, and fastest, way to achieve this outcome at Wikinews. Not having this function is holding back editing work on the project as I have to manually make such a table on a piece of paper or a wiki page, and manually delete approved pages from it, which is unnecessarily time consuming.

Thank you again for your time and attention to this. I hope to hear from you soon.

I tried adding categories. This is messy as the output of a category members is not on one page. Category of 5th of May would be one page and 3rd of May is another page. That's undesirable.

They do already have a set of templates for pending, submitted, etc. I'm not sure where the work needs to be done to make having those things more useful. I think the ideal goal would be to have a leaderboard of all articles in a subset of states and have their most recent change date and that the change was listed. This would be looked at by people with reviewer rights, who, as I understand it, currently have to spend a good deal of time amassing that data themselves every day.

Is that making any sense?