Page MenuHomePhabricator

Deleting Ns:104 in it:voy
Open, Needs TriagePublic

Description

I would like to request deletion of the namespace:104 (Tematica) from it:voy. The pages that were in it have already been moved to the ns:0. I ask for this deltation after following discussion: https://it.wikivoyage.org/wiki/Wikivoyage:Lounge/Archivio/2014/11#Namespace_Tematica
This was already done, some time ago, in the German version.

Event Timeline

Change 750814 had a related patch set uploaded (by Juan90264; author: Juan90264):

[operations/mediawiki-config@master] Delete Tematica namespace (NS:104) in Italian Wikivoyage

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

Aklapper renamed this task from Delting Ns:104 in it:voy to Deleting Ns:104 in it:voy.Jan 3 2022, 6:46 PM

Change 750814 merged by jenkins-bot:

[operations/mediawiki-config@master] Delete Tematica namespace (NS:104) in Italian Wikivoyage

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

Mentioned in SAL (#wikimedia-operations) [2022-01-05T01:49:11Z] <ebernhardson@deploy1002> Synchronized wmf-config/InitialiseSettings.php: Config: [[gerrit:750814|Delete Tematica namespace (NS:104) in Italian Wikivoyage (T298315)]] (duration: 01m 07s)

Juan90264 moved this task from Working on to Resolved on the User-Juan90264 board.

@3Pappa3: The Tematica (NS:104) and Discussioni_tematica (NS:105) namespace are deleted.

There are still a couple of pages defined in that now-undefined namespace in the database. This shoul be fix before closing this issue.

37 rows in 105 => 'Discussioni_tematica'

sql
SELECT page_title
FROM page
WHERE page_namespace = 105;

and 226 rows in 104 => 'Tematica'

sql
SELECT page_title
FROM page
WHERE page_namespace = 104;

this should be cleaned up. I do not know whom to ping, who may do it.

Change 952817 had a related patch set uploaded (by Caenus; author: Caenus):

[operations/mediawiki-config@master] Deleting Ns:104 in itwikivoyage

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

This comment was removed by Caenus.

@Aklapper sorry for ping. Do you know who can clean the database? There are still pages defined in that now-undefined namespace in the database.

This would need to be done with a script via MW, we do not execute commands directly on the DB.

I don't know if @Ladsgroup can help with this or we need Platform Engineering for it.

37 rows in 105 => 'Discussioni_tematica'
and 226 rows in 104 => 'Tematica'
this should be cleaned up. I do not know whom to ping, who may do it.

What should be done with those pages? Should they be deleted? Or moved to another namespace (which one)? Note that if we delete the pages, they won't really be accessible (just as they aren't accessible right now), because they'd still be in an undefined/deleted namespace, just also deleted by the MediaWiki's delete page option.

Unrelated note: Why is your Wikimedia account locked?

37 rows in 105 => 'Discussioni_tematica'
and 226 rows in 104 => 'Tematica'
this should be cleaned up. I do not know whom to ping, who may do it.

What should be done with those pages? Should they be deleted? Or moved to another namespace (which one)? Note that if we delete the pages, they won't really be accessible (just as they aren't accessible right now), because they'd still be in an undefined/deleted namespace, just also deleted by the MediaWiki's delete page option.

Unrelated note: Why is your Wikimedia account locked?

All those pages were just redirects, so I think they can easily be deleted.

This database also poses a problem for the bots that generate reports on Wikidata. You can see an example of this issue at https://www.wikidata.org/wiki/Wikidata:Database_reports/Sitelink_to_redirect_with_unconnected_target. The bot owner, @MisterSynergy, has mentioned that he is aware of the situation concerning itwikivoyage. This project used to have a namespace 104 ("Tematica"), and there are still a couple of pages defined in that now-undefined namespace in the database, including the five ones listed on the report. It appears that the database was not properly cleaned up after the namespace reorganization.

General question: is there a way to automate the process of ensuring that the database is consistently cleaned up after namespace reorganizations?