Template talk:Infobox Indian constituency

parl_name probably not needed as a param

Assuming state exists and it is a State Legislative Constituency, we can just put $state Legislative Assembly. -MPGuy2824 (talk) 03:30, 22 April 2023 (UTC)

Hello again! I just wanted to clarify something about the proposed changes. If I understand correctly, you're suggesting we replace "parl_name" and "constituency_no" with "State Legislative Assembly". If that's the case, then I have no objections to that. Thank you for bringing this up. Prarambh20 (talk) 10:56, 22 April 2023 (UTC)

I didn't say anything about constituency_no. Also, I meant that if the state was set to "Delhi", then we can show that the assembly is the Delhi Legislative Assembly without needing a separate parl_name parameter. -MPGuy2824 (talk) 11:55, 22 April 2023 (UTC)

OK, I understand. I will implement the changes ( as soon as I can ) . Thank you very much for your sunggestions. Prarambh20 (talk) 14:03, 22 April 2023 (UTC)

 Done - Implemented, is it works? Prarambh20 (talk) 20:19, 22 April 2023 (UTC)

It's mostly working, but not always. e.g. see this sparsely populated test case. If we addd any info to the mla param then the Assembly name shows properly. -MPGuy2824 (talk) 03:08, 23 April 2023 (UTC)

I think that in order to differentiate between Lok Sabha and State constituencies, at least one parameter needs to be added. Without a parameter, no data will be displayed by default. I'll do my best to see if I can find a solution and differentiate between Lok Sabha and State constituencies. I really appreciate your input and can see how we can work together to find a solution. Thank you for helping to improve this template. Prarambh20 (talk) 08:59, 23 April 2023 (UTC)

Completion of Merger between Infobox Indian State Legislative Assembly Constituency and Infobox Lok Sabha Constituency

Dear editors, the merger between "{{Infobox Indian state legislative assembly constituency}}" and "{{Infobox Lok Sabha Constituency}}" has been successfully completed. As a result, both templates have been redirected to this page. Thank you for your patience and understanding throughout this process. Please let us know if you have any further questions or concerns. Prarambh20 (talk) 21:12, 22 April 2023 (UTC)

Turning the duel Parameters into one without affecting the drop-in structure.Prarambh20 (talk) 18:32, 26 April 2023 (UTC)

Call for Contributions: Replacing Infobox Templates for Indian Constituencies.

Dear aspiring editors,

As per the merger discussion, it has been decided that {{Infobox Lok Sabha Constituency}} and {{Infobox Indian state legislative assembly constituency}} will be replaced with this Infobox. We kindly request interested editors to contribute to the replacement process.

When replacing transclusions of {{Infobox Lok Sabha Constituency}}, it is necessary to replace its parameters with the parameters described in the empty syntax list, along with the type mention.

 Visit, Shimla Lok Sabha constituency, Mumbai North West Lok Sabha constituency, or Kangra Lok Sabha constituency to check out some examples of replacing parameters.

Conversely, when replacing uses of {{Infobox Indian state legislative assembly constituency}}, it is not necessary to change its parameters. Instead, you only need to change the Infobox name and mention the type.

After making the replacement, please ensure that the progress bar is updated accordingly to reflect the changes made.

We appreciate your dedication and valuable contribution to this project. Thank you for participating. Prarambh20 (talk) 20:51, 26 April 2023 (UTC)

 Done.The process of replacing {{Infobox Lok Sabha Constituency}} with {{Infobox Indian constituency}} has been completed. Presently, Infobox Lok Sabha Constituency has mostly no transclusions. It is advised not to use the old Infobox Lok Sabha Constituency with its previous parameters, as this will soon be converted from a dual-parameters structure to a single-parameters structure. It is crucial to ensure that the old parameters are not being used, as they will not display any data and will not function. Prarambh20 (talk) 21:27, 28 April 2023 (UTC)

Changes requested

Here are some changes I'd recommend:

1. Change image to map_image. Makes it more obvious what the template is asking for. Change alt to map_alt and caption to map_caption at the same time.
2. Remove image_size. Let the template auto choose the map size. Reduces pointless edit warring.
3. Change constituency to ls_constituency or loksabha_cons. Less confusing
4. Change year to latest_election_year. Less confusing. Hide this param if the constituency is abolished.
5. Ignore region if set in the template. Showing this can be automatic based on the state. Remove mention of region from the documentation.
6. Remove pre_constituency and next_constituency. There is (or should be) a nav template at the bottom of the article to go to a different constituency of the same state. Removing these would make the infobox less cluttered.
7. Remove category. I'm not sure what this is for, since there is no documentation for it. We already have a param for reservation.
8. Remove logo. I don't think constituencies have individual logos in India. You'll get editors trying to put the Legislative Assembly's logo in here, if this is kept.

@Prarambh20, thoughts? -MPGuy2824 (talk) 09:31, 1 May 2023 (UTC)

I have no problem with proposals 2, 5, 6, 7, and 8 - I fully support them. However, when it comes to proposals 1, 3, and 4, I have concerns about how the changes to the parameters will be implemented throughout more than four thousand pages. Manually updating each page is not feasible, and even using WP:AWBTASKS may not be accepted as of WP:COSMETIC, as has been the case with the current application.

If there is a less time-consuming process for implementing the parameter changes outlined in proposals 1, 3, and 4, I would not object to them. Thank you very much for your sunggestions and proposals. Prarambh20 (talk) 10:51, 1 May 2023 (UTC)

Let's give other editors a week to comment on any/all of these. If no one objects, we can implement those 5 atleast. Since you are in basic agreement about the logic of the other 3, let's think and see if we get any ideas to implement them. -MPGuy2824 (talk) 11:26, 1 May 2023 (UTC)

All right. Prarambh20 (talk) 12:30, 1 May 2023 (UTC)

 Partly done Since, no one objected, I've gone ahead with changes 2 and 5-8. -MPGuy2824 (talk) 03:07, 12 May 2023 (UTC)

Regarding changes 1, 3 and 4, we can do this for each of them:

1. Add the better-named param.
2. Make the template accept either param for now.
3. Mark the old param name as deprecated.

Acceptable? -MPGuy2824 (talk) 04:30, 13 May 2023 (UTC)

Sure, I don't have a problem with that. For now, we can keep both the current and proposed versions. Regarding the number 3, I would prefer the loksabha_cons parameter, as it can be better compatible with the 'assembly_cons' parameter. Prarambh20 (talk) 10:04, 13 May 2023 (UTC)

loksabha_cons is more consistent, yes. Let's go with that. -MPGuy2824 (talk) 10:04, 13 May 2023 (UTC)

Yapp! All right. Prarambh20 (talk) 10:06, 13 May 2023 (UTC)

 Done- but didn't mark these as deprecated on template data because it might cause confusion. Prarambh20 (talk) 21:00, 15 May 2023 (UTC)

Thanks Prarambh20. When do you suggest that these get marked as deprecated? Maybe after a good percentage of them shift to the new param name? I've changed the template data to show that some of the params are synonymous with others. -MPGuy2824 (talk) 03:04, 16 May 2023 (UTC)

Yeah! I guess that totally works for me. Prarambh20 (talk) 11:03, 16 May 2023 (UTC)