Page MenuHomePhabricator

PageAssessments deployment to WMF wikis
Closed, ResolvedPublic

Description

This is the Epic task for tracking stuff that needs to be done before the extension is deployed to production.

https://www.mediawiki.org/wiki/Extension:PageAssessments

Related Objects

StatusSubtypeAssignedTask
ResolvedNone
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
ResolvedNiharika
Resolvedkaldari
Resolvedjcrespo
ResolvedSamwilson
Resolvedkaldari
InvalidNone
Resolvedkaldari
ResolvedPRODUCTION ERRORkaldari
ResolvedMusikAnimal
OpenNone
ResolvedMusikAnimal
OpenNone
ResolvedMusikAnimal
DeclinedNone
OpenNone
DeclinedNone
OpenNone
ResolvedMusikAnimal
ResolvedMusikAnimal
OpenBUG REPORTNone
Resolved NRodriguez

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes

Not to mention that Wikidata items are about concepts, not specific Wikipedia articles. So it would be inappropriate to attribute things to “Zika fever” the disease when you should be attributing them to “Zika fever” the English Wikipedia article.

@Lydia_Pintscher

Jep that is a correct assessment of the current situation from my side. Wikidata items are indeed about concepts and not about articles.

Badges are per-article assessments and only include the basic good/featured tiers.

Isn't that just because the others were not created yet?

WikiProject A may rate an article differently from WikiProject B.

That does not seems to be the case for all wikis (at least for ptwiki there is a single quality for a given article, independently of wikiprojects - only the importance changes from wikiproject to wikiproject)

DannyH renamed this task from Investigation for PageAssessments deployment to WMF wikis (at least enwiki) to PageAssessments deployment to WMF wikis (at least enwiki).Mar 24 2016, 5:25 PM

PageAssessments has been deployed to Beta Labs. Please test it out and report any issues here. Currently, the extension consists of the {{#assessment}} parser function and 2 APIs: projectpages and pageassessments.

Querying for project(s):
http://simple.wikipedia.beta.wmflabs.org/w/api.php?action=query&list=projectpages&wppprojects=Medicine&wppassessments=true

Querying for page title(s):
http://simple.wikipedia.beta.wmflabs.org/w/api.php?action=query&prop=pageassessments&titles=Bandage&formatversion=2

The next step will be testing on test.wikipedia.org.

I noticed you've embedded the {{#assessment}} parser function on the ns 0 Medicine rather than the ns 1 Talk:Medicine. Would it make a difference if you embedded it on a talk page instead of the non-talk page? I am assuming you would be embedding the parser function WikiProject templates, and those reside on the talk page.

I noticed you've embedded the {{#assessment}} parser function on the ns 0 Medicine rather than the ns 1 Talk:Medicine. Would it make a difference if you embedded it on a talk page instead of the non-talk page? I am assuming you would be embedding the parser function WikiProject templates, and those reside on the talk page.

No, it wouldn't make a difference. I'll generate some more test cases later today.

Here, http://simple.wikipedia.beta.wmflabs.org/w/api.php?action=query&list=projectpages&wppprojects=Botany|Clothing&wppassessments=true
Both of those pages have the assessment on the Talk page.

Change 294656 had a related patch set uploaded (by Kaldari):
Make sure PageAssessments extension is automatically branched

https://gerrit.wikimedia.org/r/294656

Change 294656 merged by jenkins-bot:
Make sure PageAssessments extension is automatically branched

https://gerrit.wikimedia.org/r/294656

kaldari renamed this task from PageAssessments deployment to WMF wikis (at least enwiki) to PageAssessments deployment to WMF wikis.Sep 7 2016, 11:07 PM

PageAssessments has been deployed to English Wikivoyage and integrated into the master assessment template there. No problems were encountered during deployment. Deployment to English Wikipedia will be next (possibly within a week or two). To reiterate, this extension makes no user-facing changes other than making 2 new APIs and a parser function available. Otherwise, it is a completely invisible deployment.

Remember that someone could put "JohnDoe(555)555-1234" in there, or even "JohnDoeIsAPedophile".

Did you remember to remove the value when the page is deleted, oversighted, or page moved? And copy the value again after page move, undeletion, un-oversight?

Remember that someone could put "JohnDoe(555)555-1234" in there, or even "JohnDoeIsAPedophile".

Did you remember to remove the value when the page is deleted, oversighted, or page moved? And copy the value again after page move, undeletion, un-oversight?

Did you test this before asking? If you had, or reviewed the implementation, then you would have noticed that this uses the standard mechanisms for page properties and handles all of those automatically.

Assigning to Ryan since he's looking over this now.

I went to test this out on enwp today but I'm getting:

{
    "error": {
        "code": "internal_api_error_DBQueryError",
        "info": "[WWfbIQpAEDMAAFYiJJ4AAACS] Database query error."
    },
    "servedby": "mw1286"
}

That's a timeout on

SELECT  pa_page_id AS `page_id`,pa_project_id AS `project_id`,page_title AS `title`,page_namespace AS `namespace`,pap_project_title AS `project_name`
    FROM `page_assessments`
        JOIN `page` ON ((page_id = pa_page_id))
        JOIN `page_assessments_projects` ON ((pa_project_id = pap_project_id)) 
    ORDER BY pa_project_id, pa_page_id
    LIMIT 11
Peachey88 added a subscriber: Peachey88.

Changing Project tag from Tracking-New Ending to Epic as per task description.

Although, Could this task be closed? Is there a need to link all the different deployments of this tool across the wmf cluster?

Jdforrester-WMF added a subscriber: Jdforrester-WMF.

Changing Project tag from Tracking-New Ending to Epic as per task description.

Although, Could this task be closed? Is there a need to link all the different deployments of this tool across the wmf cluster?

I think it's fine to call this Resolved.