Module talk:European and national party data Source: en.wikipedia.org/wiki/Module_talk:European_and_national_party_data

Text and/or other creative content from this version of Module:Wd was copied or moved into Module:European and national party data/Wd with this edit on 22 May 2025. The former page's history now serves to provide attribution for that content in the latter page, and it must not be deleted as long as the latter page exists.

Archives

Archive 1

Archive 2

Archive 3

Roadmap: translation

Next steps:

create template data political parties in es-wiki main space, and start deploying it to national parties
create eu seats template and use it for PACE seats
add date foundation age


Task	Completion								Comments
Task	EN	FR	DE	NL	IT	ES	PT	SL	Comments
Tests	N/A	Utilisateur	Community not interested	Gebruiker	Utente	Usuario	Usuário	Uporabnik
Create module, config file	✅ module config	✅ module config		✅ module config	✅ module config	✅ module config	✅ module config	✅ module config
Create sandbox and testcases	✅ sandbox testcases comp bar	✅ sandbox testcases comp bar		✅ sandbox testcases comp bar	✅ sandbox testcases comp bar	✅ sandbox testcases comp bar	✅ sandbox testcases comp bar	✅ sandbox
Create Wd module	✅ Wd i18n	✅ Wd i18n		✅ Wd i18n	✅ Wd i18n	✅ Wd i18n	✅ Wd i18n	✅ Wd i18n
Add module testcases	✅ testcases comp bar	✅ testcases comp bar		⚠️	✅ testcases comp bar	✅ testcases comp bar	✅ testcases comp bar	✅ testcases comp bar	NL: testcases not working?
Translate config file	N/A	✅		✅	✅	✅	✅	Done locally
Validate module	✅	✅		✅	✅	✅	✅	✅
Add untranslated documentation to module	N/A	✅		✅	✅	✅	✅	Done locally
Translate module documentation	N/A	✅		✅	✅	✅	✅	Done locally
Create three templates	✅ EUPP data PP data Inst. seats	✅ EUPP data PP data Inst. seats		✅ EUPP data PP data Inst. seats	✅ EUPP data PP data Inst. seats	⚠️ EUPP data PP data Inst. seats	✅ EUPP data PP data Inst. seats	✅ EUPP data PP data Inst. seats	⚠️ ES - templates currently in user space
Add untranslated documentation to templates	N/A	✅		✅	✅	⚠️	✅	Done locally
Translate template documentation	N/A	✅		✅	✅	⚠️	✅	Done locally
Validate templates	✅	✅		✅	✅	⚠️	✅	✅
Deploy templates to EUPPs/EUPAs	✅	✅		✅	✅	✅	✅	✅
Deploy templates to national parties	✅	✅		⚠️ Discussion here and here to propose change	⚠️ Discussion to propose change	⚠️ Discussion to use templates	⚠️ Discussion to propose change	Done locally
	🏆	🏆		🏆	🏆	⚠️	🏆	🏆

Roadmap: deployment


Task	Completion								Comments
Task	EN	FR	DE	NL	IT	ES	PT	SL	Comments
EUPP article	✅	✅	N/A	✅	✅	✅	✅	✅	Incl. for tables
Funding EUPP article	✅	✅	N/A	N/A	N/A	N/A	N/A	N/A
EUPA article	✅	✅	N/A	N/A	N/A	N/A	N/A	N/A
European political parties -- incl. tables of members	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	N/A	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES	✅ ALDE ✅ ECPP ✅ ECR ✅ EDP ✅ EGP ✅ EFA ✅ EL ✅ ELA ✅ EPP ✅ ESN ✅ Patriots ✅ PES
European political alliances -- incl. tables of members	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	N/A	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt	✅ APEU ✅ ECA ✅ DIEM25 ✅ PPEU ✅ Volt
National political parties	✅ AT ✅ BE ✅ BG ✅ HR ✅ CY ✅ CZ ✅ DK ✅ EE ✅ FI ✅ FR ✅ DE ✅ GR ✅ HU ✅ IE ✅ IT ✅ LV ✅ LT ✅ LU ✅ MT ✅ NL ✅ PL ✅ PT ✅ RO ✅ SK ✅ SI ✅ ES ✅ SE	✅ AT ✅ BE ✅ BG ✅ HR ✅ CY ✅ CZ ✅ DK ✅ EE ✅ FI ✅ FR ✅ DE ✅ GR ✅ HU ✅ IE ✅ IT ✅ LV ✅ LT ✅ LU ✅ MT ✅ NL ✅ PL ✅ PT ✅ RO ✅ SK ✅ SI ✅ ES ✅ SE	N/A	❌ AT ❌ BE ❌ BG ❌ HR ❌ CY ❌ CZ ❌ DK ❌ EE ❌ FI ✅ FR ❌ DE ❌ GR ❌ HU ❌ IE ✅ IT ❌ LV ❌ LT ❌ LU ❌ MT ✅ NL ❌ PL ✅ PT ❌ RO ❌ SK ❌ SI ❌ ES ❌ SE	❌ AT ❌ BE ❌ BG ❌ HR ❌ CY ❌ CZ ❌ DK ❌ EE ❌ FI ✅ FR ❌ DE ❌ GR ❌ HU ❌ IE ✅ IT ❌ LV ❌ LT ❌ LU ❌ MT ✅ NL ❌ PL ✅ PT ❌ RO ❌ SK ❌ SI ❌ ES ❌ SE	❌ AT ❌ BE ❌ BG ❌ HR ❌ CY ❌ CZ ❌ DK ❌ EE ❌ FI ❌ FR ❌ DE ❌ GR ❌ HU ❌ IE ❌ IT ❌ LV ❌ LT ❌ LU ❌ MT ❌ NL ❌ PL ❌ PT ❌ RO ❌ SK ❌ SI ❌ ES ❌ SE	❌ AT ❌ BE ❌ BG ❌ HR ❌ CY ❌ CZ ❌ DK ❌ EE ❌ FI ✅ FR ❌ DE ❌ GR ❌ HU ❌ IE ✅ IT ❌ LV ❌ LT ❌ LU ❌ MT ✅ NL ❌ PL ✅ PT ❌ RO ❌ SK ❌ SI ❌ ES ❌ SE	❌ AT ❌ BE ❌ BG ❌ HR ❌ CY ❌ CZ ❌ DK ❌ EE ❌ FI ❌ FR ❌ DE ❌ GR ❌ HU ❌ IE ❌ IT ❌ LV ❌ LT ❌ LU ❌ MT ❌ NL ❌ PL ❌ PT ❌ RO ❌ SK ❌ SI ❌ ES ❌ SE
Other articles	✅ European Council		N/A
	🏆	🏆	N/A	⚠️	⚠️	⚠️	⚠️	🏆

Reference files

Synchronizer: Synchronizer (Q133503746)
Module
Module sandbox
Templates
Wikidata items
Other
- Table mapping national parties to their European party of membership (also used to link a party or member state to its lower and upper houses)
- Module config file

Issues with national party seats in national legislatures

Hey @Trappist the monk, how are you? I am working on the translation of the module to use it across various Wikis, wanna help? I think key will be to find a way to localise the calls to Wikidata.

But a lower-hanging fruit is the case of Portugal, where the calls to wikidata and the composition bar are quite compatible with the English version. As you can see here and here, most tests work. The ones that don't seem to only concern the number of seats of national parties (called with their qIDs in the tests) in national legislatures, which would concern the function npp_seats_and_seat_share_in_national_institutions. However, I am not quite seeing what could be breaking it. Any ideas? Julius Schwarz (talk) 08:57, 24 April 2025 (UTC)[reply]

Ok, I am thinking that the member state name may be translated. I am going to try and move from using the member state's name to its qID. Julius Schwarz (talk) 09:13, 24 April 2025 (UTC)[reply]

Yes, that was it and I added european_party_qid and member_state_qid to the online table, in order to run checks on qIDs instead of on names. Julius Schwarz (talk) 13:06, 24 April 2025 (UTC)[reply]

A quick look at de:Modul:Wikidata, es:Módulo:Wikidata, fr:Module:Wikidata, it:Modulo:Wikidata, nl:Module:Wikidata, pt:Módulo:Wikidata seems to show that while there may be similarities among them, they do not appear to be the same as en:Module:Wikidata. I suspect that the politics necessary to unify these modules would be a daunting task. Perhaps the better solution is to roll-your-own access to wikidata using the mw.wikibase library. Such documentation as there is for that is at https://doc.wikimedia.org/Wikibase/master/php/docs_topics_lua.html.

Similarly, you might also create a custom lua version of {{composition bar}} so that you avoid anomalous variations that might crop up at the various wiki language editions.

—Trappist the monk (talk) 22:18, 24 April 2025 (UTC)[reply]

Thanks @Trappist the monk, I can look into that, but that seems daunting too. I was kind of hoping that with a nice if conditionality on the language, we could spread the arguments as needed based on per-Wiki structures. But I will check your link.

The composition bar point is probably less feasible, since this template would most likely be sitting next to other composition bars and would therefore really need to look the exact same. Julius Schwarz (talk) 11:31, 25 April 2025 (UTC)[reply]

Preventing error message inside composition bar

Hi @Trappist the monk, I have made some good progress on the translation of arguments and parameters, and that should pretty much be ready. Doesn't solve the wikidata/composition bar template implementation issue just yet, but at least I can test deploy to Portuguese Wikipedia (which so far seems to work, see testcases composition bar).

One separate issue that I have is as follows (in the sandbox): when I ask for the number of seats of a party where Wikidata does not have that information, the function returns an error message, as it should. For instance (note: maybe no longer the best error message, but that's a separate issue):

* {{#invoke:European and national party data|main|national_party|seats|Q173152|ep}} -> Error: {{European and national party data}}: institution EP has unknown party: Q173152 (help)

However, when I call the same function to retrieve that number for the purpose of a composition bar, then I should not have that error message returned, and instead just have the composition bar function itself return an error. I have tried to make this work, but no to avail. Any ideas?

{{#invoke:European and national party data/sandbox|main|national_party|seat composition bar|Q173152|ep}} -> Error: {{European and national party data}}: institution EP has unknown party: Q173152 (help)

Julius Schwarz (talk) 12:47, 29 April 2025 (UTC)[reply]

You can have the code that returns the error messages from allpp_seats_in_eu_institutions() return a second value (a boolean) so, at line 457 this (line 459 similar):

return make_error_msg (substitute (cfg.error_messages_t.party_req_share)), true;

Then, change line 740 to this:

local has_error;
party_seats, has_error = allpp_seats_in_eu_institutions (frame, party, institution, cfg.body_prop_t[institution]);
if has_error then
	return party_seats;												-- <party_seats> has an error message
end

—Trappist the monk (talk) 13:46, 29 April 2025 (UTC)[reply]

Thanks for the quick feedback, @Trappist the monk. However, I am not sure this is working. I made the changes, but I am not seeing a change in the testcases page. Did I not do it right? Julius Schwarz (talk) 14:00, 29 April 2025 (UTC)[reply]

I changed your example above to remove the <nowiki>...</nowiki> tags and to use the sandbox. Looks like it's working correctly – shows the module's error message, not the MediaWiki error messages. But, your testcases page is calling the live version of the module not the sandbox.

—Trappist the monk (talk) 14:20, 29 April 2025 (UTC)[reply]

Ah yes, indeed. Thanks a lot! Julius Schwarz (talk) 14:30, 29 April 2025 (UTC)[reply]

Translation of calls to wd/wikidata and composition_bar templates

Hi @Trappist the monk, so the translation of parameters and arguments now works, and I am just getting to the translation of the calls to wd/wikidata and composition_bar templates. I wrote a xlate_wikidata function in the sandbox and will test it early next week. Would you mind having a quick look to see whether this at least has the possibility of working? That would be helpful. Thanks a lot! Note: the idea is to develop the function in the English wikipedia, to make sure that it does not break anything with the current module, and then to move it to the French Wikipedia to work on adding another language. Julius Schwarz (talk) 14:31, 2 May 2025 (UTC)[reply]

At line 145, you create args_t. Are you saying that {{wikidata}} takes a lua sequence as its options positional parameter? Are you sure about that?

Is it your intention to duplicate lines 146–160 for each language?

At line 144, you fetch the local wiki's language tag. That happens 9 other times in the module. Perhaps the best way to do that is to do it only once as an export from the ~/config module. line 146 then becomes:

if 'en' == cfg.this_project_language then

and line 144 goes away. The other calls to set this_project_language also go away.

—Trappist the monk (talk) 18:51, 2 May 2025 (UTC)[reply]

Hey, thanks for the reply! Let me try and address your points in order. 1/ Maybe not, you are right. I was hoping that returning args_t would be akin to return the options one after the other. 2/ Yes, duplicating the lines for each language was kind of my plan. I realise that if we went for an own implementation of the call to Wikidata, as you suggested, we would not need that, but I have no real idea of how to do that (and I still think that wouldn't really work in the case of the composition_bar template, which would still need to look like what the template looks like in each local version). 3/ That's a really good point, I will give that a try. Julius Schwarz (talk) 20:55, 2 May 2025 (UTC)[reply]

Hey @Trappist the monk, I implemented the changes you suggested and went ahead with replacing the use of "frame:expandTemplate" with calls to the new "xlate_wikidata" function, and it just "kinda" works. If you check the regular testcases (not the ones for the composition bar yet), some values work, but some are off. I am having the feeling that the xlate_wikidata function returns the first preferred value for the right entity/property, regardless of the qualifier, which is odd. For instance:

{{#invoke:European and national party data/sandbox|main|european_entity|seats|EPP|EC}} returns 11, which is right, but it is also the first preferred value for seats here;
{{#invoke:European and national party data/sandbox|main|european_entity|seats|PES|EP}} returns 4, which is false, but it is the first preferred value here, under a different qualifier;
same thing when asking about ALDE and the EFA returning 5 and 8, respectively.

This is surprising because these are rather straightforward calls. Any ideas? Julius Schwarz (talk) 07:33, 6 May 2025 (UTC)[reply]

When you write:

{{#invoke:European and national party data/sandbox|main|european_entity|seats|EPP|EC}}

xlate_wikidata() takes that and, at line 154 creates a table for args that (to lua) looks like this:

args = {
[1] = "property",
[2] = "Q208242",
[3] = "P1410",
["qualifier_id"] = "Q8880",
}

I suspect that args["qualifier_id"] is not what you wanted. Rather, did you not want:

args = {
[1] = "property",
[2] = "Q208242",
[3] = "P1410",
["P208"] = "Q8880",
}

Perhaps, at line 154, you meant to write:

return frame:expandTemplate ({title='wikidata', args = {data_requested, qid, property_id, [qualifier_id] = value_of_qualifier}});

—Trappist the monk (talk) 13:58, 6 May 2025 (UTC)[reply]

I guess I did mean to write that, yes indeed :) Thanks! I will continue trying to address the following issues. Julius Schwarz (talk) 14:39, 6 May 2025 (UTC)[reply]

Say @Trappist the monk, you have shown how to call a template with frame:expandTemplate ({title='wikidata', args = {....}});, but how does one call a module? Julius Schwarz (talk) 14:25, 7 May 2025 (UTC)[reply]

The module must be callable from another module. For years and years, Module:Citation/CS1 (the engine that renders {{cite book}}, {{cite web}}, etc) has not been callable from another module. At its most recent update, Module:Citation/CS1 became callable. {{cite tweet}} is a template that wraps {{cite web}} by way of Module:Cite tweet which now calls Module:Citation/CS1.

At the very bottom of Module:Citation/CS1 there are two exported functions. citation is the entry point for the {{#invoke:}} in {{cite book}} and the other native cs1|2 templates. _citation is the entry point for use by other modules.

{{cite tweet}} calls main() in Module:Cite tweet at line line 103. The code fiddles about collecting and formatting parameter values and stuff until at line 146 it calls _citation in Module:Citation/CS1 to get a rendered citation.

Does that answer your question?

—Trappist the monk (talk) 17:07, 7 May 2025 (UTC)[reply]

Kind of, yes. Does this mean that Module:Wd is therefore not callable because is does not have that module entry point? Julius Schwarz (talk) 08:40, 8 May 2025 (UTC)[reply]

Actually, if you have a second to have a look at the xlate_wikidata function in the French sandbox (see testcases), that would be great! Julius Schwarz (talk) 14:57, 7 May 2025 (UTC)[reply]

Did you remember to export this_project_language from fr:Module:European and national party data/config? Should the fr.wiki version of that module be the same as the en.wiki version?

—Trappist the monk (talk) 18:58, 7 May 2025 (UTC)[reply]

Ahah, damnit, the export again. I should copy/pasted the config from pt instead of just adding bits that were missing. Thanks. As for the module itself, I copied the en-wiki/sandbox version to fr-wiki/sandbox, and am now working there to add the part for fr-wiki. Once that is done, I will move it back to en-wiki and, indeed, all modules will be the same -- just the config file will be different. Julius Schwarz (talk) 20:49, 7 May 2025 (UTC)[reply]

Quick follow-up questions, @Trappist the monk:

Function test2 calls xlate_wikidata; it takes a party_qid and a property and should return the qID of the response. On fr:Utilisateur:Julius Schwarz/Brouillon, you see that the template gives out the right output, but test2 does not. Instead it display "displayformat = raw", which should just be sent to the {{Wikidata}} template. Any idea why?
In xlate_wikidata, we do a check to see whether value_of_qualifier is nil or not. However, even when it is nil (as, for instance, it is in the test2 function), it still seem considered as not nil (like if you change the return value in the if nil ~= value_of_qualifier case, this is what will be returned by test2). Any idea why?

Julius Schwarz (talk) 11:49, 8 May 2025 (UTC)[reply]

The call in test2() looks like this:

return xlate_wikidata (frame, 'property', qid, property, '', '', 'reference=no', 'preferred=no', 'raw=yes', 'linked=no');

Replace line 181 with:

if local_raw == 'raw=yes' then local_raw = 'raw' else local_raw = '' end; (same as line 162)

Then, in line 186, replace local_raw with ['displayformat'] = local_raw; similar replacements in the other template expansions.

Empty string is not the same as nil. In the call in test2(), the sixth parameter, value_of_qualifier, is set to empty string. If you want that value to be nil, you must explicitly set it to nil:

return xlate_wikidata (frame, 'property', qid, property, '', nil, 'reference=no', 'preferred=no', 'raw=yes', 'linked=no');

—Trappist the monk (talk) 14:58, 8 May 2025 (UTC)[reply]

Own implementation

Hey @Trappist the monk, I just finished rolling out the French version, and am starting the Italian one, so things are moving forward. Say, in a previous question, you had opined that, since templates were different from wiki to wiki, maybe the better solution would be to roll-our-own access to wikidata using the mw.wikibase library.

While I continue to think that this should not apply to the composition_bar templates (so that we keep wikis' respective look and feel) and that doing this for the wikidata templates is above my competencies, I do agree that this would make things easier in the longer run -- for instance, the different implementation in fr-wiki means that several options (reference, width, bar-color, etc.) are not available, which is unfortunate. So I was wondering: is this something that you might consider doing? I would be really useful help! Julius Schwarz (talk) 15:12, 13 May 2025 (UTC)[reply]

Yep, I did, but I think that I meant that suggestion as something for you to do; I don't think that I was volunteering to do it. I don't know much about wikidata and, for me, wikidata isn't all that interesting because it isn't used in my normal areas of interest (with the exception of {{cite q}} which I will tweak when I have to but otherwise prefer to ignore).

—Trappist the monk (talk) 19:09, 15 May 2025 (UTC)[reply]

Ahah, don't worry, I did understand that that was a suggestion for me to do -- I was just wondering whether you actually might consider making an exception and volunteerting in the end. I just realise that the obstacles to fully implementing the module are too numerous for the translation system (it does work, but I have to leave some functionalities aside, which is a shame), but I wouldn't even know where to begin with this.. Julius Schwarz (talk) 06:51, 16 May 2025 (UTC)[reply]

so what do you think, @Trappist the monk, is that something we could work on in the end? Or would you happy to know someone with the skill/time to help out on this? Julius Schwarz (talk) 10:17, 19 May 2025 (UTC)[reply]

Thanks a lot for your help, @Ahecht, this is really appreciated. From what I see, your change greatly simplifies the code of the xlate_wikidata function.

However, it currently does not work for non-English versions of Wikipedia, which is why we had the "if" test on the wiki's local language in the xlate_wikidata function.

With your solution, can we make Module:European and national party data/Wd available to other wikis as well? Because of course, as things stand, the module is broken when used in other languages -- see here for example.

As indicated, the goal is really to make the module available "as is" to other wikis, so that we only need to update/improve one version and then just synchronize it across wikis. Julius Schwarz (talk) 07:20, 23 May 2025 (UTC)[reply]

The error message is telling you that you must have a copy of Module:European_and_national_party_data/Wd at pt:Module:European_and_national_party_data/Wd. It is not possible, alas, to interwiki require() modules.

—Trappist the monk (talk) 13:08, 23 May 2025 (UTC)[reply]

Thanks @Trappist the monk, that's what I feared. Not a major issue, I guess, but just one more thing to keep track of. Something we'd avoid with mw.wikibase, correct? Julius Schwarz (talk) 13:17, 23 May 2025 (UTC)[reply]

No necessarily. It can be argued that segregating code that interfaces to wikidata is beneficial.

—Trappist the monk (talk) 13:34, 23 May 2025 (UTC)[reply]

Hmm, ok. Can you help me understand that last point? Julius Schwarz (talk) 07:37, 26 May 2025 (UTC)[reply]

Organization, mostly.

—Trappist the monk (talk) 11:41, 27 May 2025 (UTC)[reply]

New translation system

Hi @Ahecht, thanks again for the help; I am just getting to this now. Following @Trappist the monk's message above, I created "/Wd" modules across all relevant wikis. Once that was done, I got an error saying that a "/Wd/i18n" module was also needed, which I understand is for translation. So I went ahead and created those in all relevant wikis (and I will have to localise them).

Now the testcases for en-wiki are working. However, when I try the pt-wiki testcases, for instance, i am told "module 'Module:European_and_national_party_data/Wd/i18n' not found", which is somewhat normal since a module in Portuguese is called "modúlo".

However, it would seem, from the code of the /Wd module that "/i18n" is just slapped at the end of whatever the current module is called (in the loadI18n function), which should get the Portuguese name, shouldn't it?

Finally, I note that, in the testcases, line 6 says that it does not recognise the local version of "lower house" ("camara baixa"), which seems to indicate that the translated version doesn't get picked in the /config file; is that what is happening?

Thanks a lot in advance for your help as I get my bearings on the new system :) Julius Schwarz (talk) 07:51, 26 May 2025 (UTC)[reply]

@Julius Schwarz Looks like a caching issue. I did a null-edit on pt:Módulo Discussão:European and national party data/sandbox/testcases and the errors went away. --Ahecht (TALK
PAGE) 14:14, 27 May 2025 (UTC)[reply]

@Ahecht point taken, thank you. That does solve the first issue. The second one is a little strange, as "PE" which is the Portuguese acronym for the European Parliament (different from the English acronym) does get recognised (same for the European Commission, for instance), but not the Portuguese for lower-house and upper-house. Julius Schwarz (talk) 14:28, 27 May 2025 (UTC)[reply]

PS: since the error message is in Portuguese, the config file is definitely used. Julius Schwarz (talk) 14:29, 27 May 2025 (UTC)[reply]

Never mind, it's a hyphen issue. Julius Schwarz (talk) 14:31, 27 May 2025 (UTC)[reply]

Individual members date

Hi @Trappist the monk @Ahecht, very small issue: I think the call to get the "individual members date" no longer works since the move to the own implementation of the calls to Wikidata. I made a test here and it is not showing up, neither is it showing up on pages such as here, while I think it did. Any idea why? It's defined around line 324 in the module.

Actually, I was trying to find a way to only return the year (by adding something like "individual members year"; how would one do that? Julius Schwarz (talk) 21:14, 29 May 2025 (UTC)[reply]

Any ideas, @Trappist the monk, @Ahecht? Julius Schwarz (talk) 09:24, 3 June 2025 (UTC)[reply]

In the debug console, this appears to be able to fetch the date/timestamp for European People's Party (Q208242):

=mw.dumpObject (mw.wikibase.getEntity ('Q208242').claims.P2124[1].qualifiers.P585[1].datavalue.value.time) → +2022-12-31T00:00:00Z

—Trappist the monk (talk) 13:17, 3 June 2025 (UTC)[reply]

Thanks @Trappist the monk; I think that what we need to do, once the date part is fixed, is simply to decrease the precision, no? If we have a precision level of 11 (down to the day), there should be a way to move that to a precision of 9 (year). Would you know anything about this? Julius Schwarz (talk) 13:50, 3 June 2025 (UTC)[reply]

I don't know where you are getting you precision levels 9 and 11. If you want only the year portion of the date/timestamp returned from the call above:

string.match ('+2022-12-31T00:00:00Z', '%d%d%d%d')

—Trappist the monk (talk) 14:08, 3 June 2025 (UTC)[reply]

Thanks @Trappist the monk. I guess I am just not really sure how to square that with the results grabbed by the xlate_wikidata/Wd function, which does not have this format, but maybe I can also try and extract a four-digit string from the result. It just feels a bit hacky, when Wikidata has a date/time system that includes levels of precision, which would feel cleaner. Julius Schwarz (talk) 14:32, 3 June 2025 (UTC)[reply]

That actually seems to work! Thanks @Trappist the monk! Julius Schwarz (talk) 07:19, 4 June 2025 (UTC)[reply]

@Julius Schwarz It doesn't look like it worked in the May 16th version of the main template either, before my changes were implemented. I inserted some debugging statements into the code, and it looks like the "individual members date" line is calling xlate_wikidata("qualifier", "Q208242", "P2124", "P585", "", "reference=no", "preferred=yes", "raw=no", "linked=no"), which in turn calls require('Module:European_and_national_party_data/Wd')['qualifier']({"", "preferred", "", "", "Q208242", "P2124"}). Since value_of_qualifier is "", the qualifier ID is not being sent to Wd, and therefore nothing is being returned. --Ahecht (TALK
PAGE) 15:30, 3 June 2025 (UTC)[reply]

@Julius Schwarz Special:Diff/1293776278 fixes that test case, but I don't know enough about the module to say whether that will break anything else. --Ahecht (TALK
PAGE) 16:18, 3 June 2025 (UTC)[reply]

Thanks a lot for this, @Ahecht! I really appreciate. I will have a close look tomorrow, but it should not break anything. As for the reason why it may not have worked before either, it might be because there was an error in the code; I fixed one just earlier today -- even if it didn't actually solve the issue in the present code. In the code you quote, how come "P585" disappears between the two lines? I mean, it makes sense for there not to be a value_of_qualifier, since this is what we are trying to grab. Julius Schwarz (talk) 20:17, 3 June 2025 (UTC)[reply]

@Julius Schwarz The way the code was written originally (even before my changes) was to not include the qualifier if value_of_qualifier was blank. Since the fifth parameter is "", it didn't include P585. --Ahecht (TALK
PAGE) 20:33, 3 June 2025 (UTC)[reply]

Maybe I am not understanding but, to me, P585 is not the value of the qualifier, it is the qualifier_id, the value would be the date itself. In some cases we already know the value of the qualifier, but here we ask for it. Don't know whether this is clear. I guess what I am trying to say is that if it works, then wonderful, but I am not sure I understand what changed just yet :) Julius Schwarz (talk) 20:37, 3 June 2025 (UTC)[reply]