You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @RVA2869, could you please confirm whether you want users to search agencies directly from the navigation bar, instead of first selecting a country and then navigating to the agencies section as an additional feature?
Hi @yash5749,
If you look at the screenshot, under ‘Germany' (English) it says the official name in its native language of the country: Bundesrepublik Deutschland.
Just to confirm my understanding: for agencies, should the UI display the agency name in English along with its official/native-language name underneath it, similar to the country example shown for Germany?
Yes, this issue is about adding the official name (we're not changing the header). Please also use the same logic for selecting the language the name is displayed in as the countries do (because it happens that countries have more than one official language).
@Ainali
While working on this, I noticed that agency data is generated through separate country-specific SPARQL generator queries rather than a shared reusable query.
Since the native/official label logic would need to be added individually across these generators, I wanted to clarify the expected scope for this issue:
should the PR update all country generator queries,
or would a smaller scoped implementation for the affected/example countries be acceptable initially?
No, that's not where the data is generated. It is in queries/organization-optional.rq and it is that (and templates/org.html ) that needs to be changed.
@Ainali
I've added the feature, but full builds are intermittently failing due to Wikidata SPARQL endpoint 502 responses (currently failing from different queries like organization-optional.rq and account-data.rq during page generation).
Is there a recommended way to do smaller/localized builds for testing template/query changes during development?
@RVA2869
Yes, that's the approach I followed. I added the native label rendering below the primary organization label using the same pattern as the country page:
Activity
yash5749 commentedon May 27, 2026
Hi @RVA2869, could you please confirm whether you want users to search agencies directly from the navigation bar, instead of first selecting a country and then navigating to the agencies section as an additional feature?
I wanted to confirm this before creating the PR.
Ainali commentedon May 27, 2026
@yash5749 No, this issue is only about the official name. We try to avoid scope creep and keep issues and PRs small.
RVA2869 commentedon May 27, 2026
Hi @yash5749,
If you look at the screenshot, under ‘Germany' (English) it says the official name in its native language of the country: Bundesrepublik Deutschland.
yash5749 commentedon May 27, 2026
Thank you for the clarification, @Ainali and @RVA2869.
Just to confirm my understanding: for agencies, should the UI display the agency name in English along with its official/native-language name underneath it, similar to the country example shown for Germany?
Something like this:
Once confirmed, I will raise a PR.
Ainali commentedon May 27, 2026
Yes, this issue is about adding the official name (we're not changing the header). Please also use the same logic for selecting the language the name is displayed in as the countries do (because it happens that countries have more than one official language).
yash5749 commentedon May 27, 2026
@Ainali
While working on this, I noticed that agency data is generated through separate country-specific SPARQL generator queries rather than a shared reusable query.
Since the native/official label logic would need to be added individually across these generators, I wanted to clarify the expected scope for this issue:
Ainali commentedon May 27, 2026
No, that's not where the data is generated. It is in queries/organization-optional.rq and it is that (and templates/org.html ) that needs to be changed.
yash5749 commentedon May 27, 2026
@Ainali
I've added the feature, but full builds are intermittently failing due to Wikidata SPARQL endpoint 502 responses (currently failing from different queries like
organization-optional.rqandaccount-data.rqduring page generation).Is there a recommended way to do smaller/localized builds for testing template/query changes during development?
RVA2869 commentedon Jun 5, 2026
Something like this?
<p lang="{{ .nativeLabel.Lang }}">{{ .nativeLabel }}</p>Source - #244
yash5749 commentedon Jun 6, 2026
@RVA2869
Yes, that's the approach I followed. I added the native label rendering below the primary organization label using the same pattern as the country page:
Please let me know if you'd prefer any changes to how
nativeLabelis populated or displayed.check the PR - #658