Module:Resolve category redirect

@Tom.Reding: should Module:Navseasoncats use Module:Resolve category redirect instead of function rtarget?

Module:Resolve category redirect is a fork (made by me) of the clever code you wrote in function rtarget. However, Module:Resolve category redirect has now diverged a little, with some tweaks I made to reject incompatible characters. Also, the code uses a list of redirects to ((Category redirect)), which may need maintenance.

Wouldn't it be better to have the code in just one place? I know it's a bit cheeky of me to suggest that my fork should usurp its parent, but I don't think that two versions of the same code is a great idea. Module:Resolve category redirect has kinda take off, and is no longer the wee niche tool I thought it would be. BrownHairedGirl (talk) • (contribs) 17:58, 18 June 2023 (UTC)[reply]

@BrownHairedGirl: yes, it should! I can do that soon. ~ Tom.Reding (talk ⋅dgaf) 13:23, 2 July 2023 (UTC)[reply]

@BrownHairedGirl: on closer inspection, function rtarget performs NSC-specific operations in its for-loop that are incompatible with Module:Resolve category redirect's current functionality - like evaluating ((Title year)) in ((Category redirect))'s parameter, and adding it to a NSC tracking category if that fails. Currently, there's no way to do this with Module:Resolve category redirect. RCR would have to return a pass/fail flag to be useful in this way, to tell the caller whether it's returning the passed cat because of a failure, or because there's no redirect to follow, and it would have to do this without interfering with RCR's current usage. ~ Tom.Reding (talk ⋅dgaf) 13:42, 3 July 2023 (UTC)[reply]

Thanks for the diligent scrutiny, @Tom.Reding. I hadn't considered that issue, and parts of it probably relate to functionality which I removed when creating Module:Resolve category redirect. So, my bad for not recalling that.

Also, I recently added to RCR some code to ignore titles with templates in them, so that's a further divergence.

Note that RCR doesn't handle ((title year)) and ((title decade)), causing problems kindly spotted by the wonderful @Fayenatic london. So I did an AWB run to replace them with actual numbers. Obviously, new uses of those templates will be created in good faith, so it might be helpful to add that functionality to RCR, if either of us ever has the energy.

Credit where credit's due – it was Frietjes. (here) – Fayenatic London 16:00, 3 July 2023 (UTC)[reply]

Ah. Sorry @Frietjes. And thanks to @Fayenatic london for the correction. BrownHairedGirl (talk) • (contribs) 19:49, 9 July 2023 (UTC)[reply]

However, one aspect that should always remain common to the two modules is the list of redirects to ((Category redirect)). Would it be a good idea to move that to a shared module, to a avoid having two copies of it? Or would it be better to just add a wee comment to each module noting that the two should always be in sync? BrownHairedGirl (talk) • (contribs) 14:05, 3 July 2023 (UTC)[reply]

@BrownHairedGirl: done! I created a shard module, Module:Template redirect regex, as a general repository for redirect regexes, should it be useful for other templates, and updated the NSC & RCR sandboxes to use it, for inspection/comment before publishing live. Both templates' testcases look good. ~ Tom.Reding (talk ⋅dgaf) 19:11, 9 July 2023 (UTC)[reply]

Great work yet again, @Tom.Reding. The testcases all look fine to me and I like the way that you have made it a general repository for redirect regexes.

Please feel free to go live. BrownHairedGirl (talk) • (contribs) 20:13, 9 July 2023 (UTC)[reply]

Done! ~ Tom.Reding (talk ⋅dgaf) 14:56, 16 July 2023 (UTC)[reply]

Displaying only the next and previous year

((2021 wildfires)) includes two links to the next and previous year, without the current year:

◀ 2020 2022 ▶

Can ((navseasoncats)) display links in this format, or is there another template that does this? Jarble (talk) 17:20, 11 October 2023 (UTC)[reply]

Why would you only want two links in a cat as opposed to the current work which shows multiple other years? Also, I have removed the links to the templates - we should not link other templates in templates - and have replaced them with article links. Primefac (talk) 08:49, 12 October 2023 (UTC)[reply]

Requested move 22 October 2023

The following is a closed discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. Editors desiring to contest the closing decision should consider a move review after discussing it on the closer's talk page. No further edits should be made to this discussion.

The result of the move request was: moved to Template:Category series navigation. This option has at least some level of support from most participants here and is the clear consensus choice. (closed by non-admin page mover) Elli (talk | contribs) 03:37, 31 October 2023 (UTC)[reply]

Template:Navseasoncats → Template:Sequential chronology category navigation
Module:Navseasoncats → Module:Sequential chronology category navigation

– The current name for this category is too specific. Its documentation says it "is intended to be a minimal-input, near-universal template for automatically navigating most sequential categories", and only two of the 15 examples immediately following are are for seasons. Thus, the current name violates TMP, which says "[t]emplate function should be clear from the template name". Of course, the proposed name is longer, but we can use/create redirects as needed .

Two other notes. There is also the (current) name of Template:Irregular chronology category navigation, which was previously called Template:Irregular navseasoncats before a WP:BOLDMOVE. There was a previous discussion at Template talk:Navseasoncats/Archive 1#Requested move 25 May 2019, which resulted in no consensus. However, the proposed name at that discussion was overly broad which resulted in a smattering of different suggestions.

Pinging participants of that earlier discussion: @Amakuru, BD2412, Fayenatic london, Gonnym, Marcocapelle, Steel1943, and Tom.Reding.

House Blaster^talk 00:09, 22 October 2023 (UTC)[reply]

I also support ((Category series navigation)) or ((Category sequence navigation)). House Blaster^talk 02:31, 31 October 2023 (UTC)[reply]

Oppose - not all categories serviced are chronological. ~ Tom.Reding (talk ⋅dgaf) 02:14, 22 October 2023 (UTC)[reply]
- Would "sequential category navigation" be more appropriate? I realize that this template is not the only one used for sequential navigation, but it is the "main" one (in the way that e.g. ((talk header)) is not the only banner that can be put at the top of a talk page, ((hat)) is not the only template to collapse content, etc.). House Blaster^talk 02:47, 22 October 2023 (UTC)[reply]
  - If it must change, then ((Category series navigation)) or ((Category sequence navigation)) are my preferences, in that order, since what ((Navseasoncats)) does is more accurately described by a series (mathematics) than by a sequence (mathematics). ~ Tom.Reding (talk ⋅dgaf) 15:38, 22 October 2023 (UTC)[reply]
    I'm good with these also. Gonnym (talk) 15:50, 22 October 2023 (UTC)[reply]
    
    I would think "sequence" would be a more accurate mathematical term than "series", no? We aren't taking the sum of, say, Category:1990s in Scotland and Category:2000s in Scotland. House Blaster^talk 15:56, 22 October 2023 (UTC)[reply]
    On the contrary, "series" is more applicable as a mathematical term than "sequence", as the numbers do not repeat and are in ascending order.
    
    There are a lot of tracking categories which presumably would also have to be renamed. Navseasoncats is in a class of its own, and I use it so frequently that I have accepted it as deserving a concise idiosyncratic name with its own etymology. However, I concede that an expanded and updated name would be consistent with other templates, and would be acceptable especially as the longer-named variants (e.g. ((navseasoncats with centuries below decade))) have been merged into it. – Fayenatic London 20:42, 23 October 2023 (UTC)[reply]
I agree that "sequential category navigation" would be a lot clearer. I wonder if for templates it really matters if the name isn't as clear as possible. Marcocapelle (talk) 06:02, 22 October 2023 (UTC)[reply]
Yes, it does. It's also in the guideline WP:TPN Template names are easiest to remember if they follow standard English spelling, spacing, and capitalization. Gonnym (talk) 09:33, 22 October 2023 (UTC)[reply]

I don't see why clarity shouldn't matter for template names. I have been meaning to do this RM for a while – when I first saw this template, I had to go to the template page to see why a template for "seasons" was on a page about terms in office. I can't imagine the name is helping the already steep learning curve needed to get involved with categories. House Blaster^talk 15:56, 22 October 2023 (UTC)[reply]
Support any name that isn't the awful "navseasoncats". I appreciate all the work Tom has done here but I really don't understand their persistent on keeping this horrible name that does not make sense in most of its usages. They argue that not all categories serviced are chronological yet they ignore the fact that most of them are not "season" which is in the article title. Gonnym (talk) 09:36, 22 October 2023 (UTC)[reply]
Since the proposal to change the name is based on naming accuracy, the new name should follow those same guidelines. ~ Tom.Reding (talk ⋅dgaf) 12:32, 22 October 2023 (UTC)[reply]
It follows it better than the current name. So imperfect name > horrible name. Gonnym (talk) 15:49, 22 October 2023 (UTC)[reply]

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.