Skip to content

Add official name(P1448) for agencies #654

Description

@RVA2869

The feature

We already have this feature for countries; it would be logical for it to be available for agencies as well.
Image

Why?

Currently, 14,297 official names have already been added for agencies.
Image

Examples and inspiration

No response

Activity

  1. added theissue type on May 18, 2026
  2. yash5749 commented on May 27, 2026

    @yash5749

    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.

    Image
  3. Ainali commented on May 27, 2026

    @Ainali
    Member

    @yash5749 No, this issue is only about the official name. We try to avoid scope creep and keep issues and PRs small.

  4. RVA2869 commented on May 27, 2026

    @RVA2869
    CollaboratorAuthor

    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.

  5. yash5749 commented on May 27, 2026

    @yash5749

    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:

    Image

    Once confirmed, I will raise a PR.

  6. Ainali commented on May 27, 2026

    @Ainali
    Member

    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).

  7. yash5749 commented on May 27, 2026

    @yash5749

    @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?
  8. Ainali commented on May 27, 2026

    @Ainali
    Member

    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.

  9. yash5749 commented on May 27, 2026

    @yash5749

    @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?

  10. RVA2869 commented on Jun 5, 2026

    @RVA2869
    CollaboratorAuthor

    Something like this? <p lang="{{ .nativeLabel.Lang }}">{{ .nativeLabel }}</p>
    Source - #244

  11. yash5749 commented on Jun 6, 2026

    @yash5749

    @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:

    <p lang="{{ .nativeLabel.Lang }}">{{ .nativeLabel }}</p>

    Please let me know if you'd prefer any changes to how nativeLabel is populated or displayed.

    check the PR - #658

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions