Ask The Tropers

Would be best to move the disambiguation to Main/. Once that's done, then it would be safe to convert the original into a redirect.

Edit: Looks like that's covered with an auto-disambig. I'll speak with the rest of the staff.

To be clear, our policy is that when a work title conflict exists on the wiki, all articles related to it should be disambiguated by title.

In other words, WesternAnimation.Primal 2019 is fine. The video game should be moved to VideoGame.Primal 2003. The fic should be moved to Fanfic.Primal Fan Fic or however we typically do that (I can't remember offhand and don't feel like checking).

The disambiguation would be Main.Primal.

Typically we disambiguate fanfics by author name, so this would be Fanfic.Primal Nexus The Dark.

Maybe it's a policy (I'd like to know where it is exactly, though). That said, I disagree with the idea of always separating works if they have the same title. I thought that namespace system was introduced to help separate works from other same-name works or tropes, because if it's not, I don't think we should have bothered. We could have just done a Work/ namespace if it's true that even if there are two differently namespaced works, they have to be title-split by year/author/other if they have the same name.

For just one example, look at Flight. There's the trope Flight, ComicBook.Flight, Film.Flight, Literature.Flight, and VideoGame.Flight (there are several fanfics called Flight too, but no-one has created a page about any). Thanks to the namespace system, the trope and these pieces of media can't be confused with each other, and the namespace system ensures you comfortably link to the one you want as well. Now, you could argue that there is a problem with subpage collision, but one can always specifically mark what part of the subpage is related to what (YMMV.Flight marks film YMMV, comic YMMV, and video game YMMV for instance). Splitting these things would only likely lead to harder linking (a large amount of links to such works are put as Film.{{Flight|2012}}, but I find such formatting annoying and I don't think there's a need to hide years), plus ultimately devalue the namespacing which I think was made to help split works with the same name as mentioned previously. I'm perfectly fine with splitting media with the same namespace and same year so that there's no confusion (VideoGame.The Messenger 2001 and VideoGame.The Messenger 2018 with a disambiguation at VideoGame.The Messenger is a great example), I just feel that splitting stuff with the same name but different namespace is overkill.

That was a load of text, but I wanted to share what I think. Thank you if you read it.

^^ Fanfics are usually disambiguated by source work if possible. This one's a crossover (and appears from a quick look to be an actual cross, not yet-another-alt-power), so we might prefer going by the author in this case to avoid an overly long disambiguation.

Also, when did the policy change from "same namespace and title" to "same title"?

I imagine it was probably to avoid subpage confusion.

As I said in my post, subpage confusion is not an issue if we just mark what subpage material is related to which work by header or folder. I know my post is long, but please, at least consider it (and I know it wasn't posted before the split, I just don't want it to be ignored). Also, RB 2's question is valid, plus fanfics are indeed often split by source work (see Fanfic.Angels Egg MHA and Fanfic.Game Theory Lyrical Nanoha for examples), though by author can also be done (like Fanfic.Avengers Endgame Dragonis Prime, though this one was unnecessary as it's same title but different namespaces).

It's confusing regardless. This policy was adopted years ago.

So, move WesternAnimation.Primal to Main?

I agree with Piterpicher. What's the point of the namespace system if works with the same name have to be at different titles anyway?

Ask a moderator to move it to Main/, at least for now, although I think Fighteer is trying to avoid my arguments in my previous posts. I explained that moving pages in the same namespace but different title is bad because it devalues the different namespaces for media (we could have just made a Work/ namespace if we're going to always move the title) and that subpage collision would be a nonexistent issue if only people used headers or folders which I think are fairly solid reasons for supporting not overly disambiguating things. Unfortunately, I feel he doesn't want to address the issue, simply by saying that it's "confusing" and stating there's a policy that was "adopted years ago", even though he doesn't link to it (the closest thing to a policy about same titles in different works is the part on How to Create a Work's Page "Note that we require usage of the official name of the work, not Fan Nicknames. In the case of Recycled Titles, append the year of release to later entries (e.g.: the 7th-gen reboot of the Tomb Raider series would go in VideoGame/TombRaider2013, to differentiate it from the first game, which is on VideoGame/TombRaider).", although even that doesn't address same title but different namespace). Of course, if there's a need for a policy, I could discuss making Administrivia.Page Title Collision.

I don't want to be rude or anything and I understand you're a moderator, but please, try to use arguments why you think that always splitting media is better. I do, and I've seen you justify your reasoning elsewhere, so I want to have a regular discussion for this. Plus, Rjd agrees with me, which is why I want other tropers to weigh in as well.

By the way, the reason I didn't reply for so long was because I kinda wanted the Uwe Boll debacle to end (it unfortunately just petered out) and was busy with a TLP draft. Another wall of text, but thank you if you read it.

Bumping for OP change.