Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

lack of translations for metadata field names in API responses #1019

Open
mw0000 opened this issue Feb 8, 2024 · 1 comment
Open

lack of translations for metadata field names in API responses #1019

mw0000 opened this issue Feb 8, 2024 · 1 comment

Comments

@mw0000
Copy link
Contributor

mw0000 commented Feb 8, 2024

Why are some Dublin Core field names translated in API responses while others are not, even though they have their translations in .po files?

{
    "id": 55,
    "url": "XXX",
    "order": 16,
    "name": "Miejsce urodzenia",
    "description": "",
    "comment": "",
    "element_set": {
        "id": 3,
        "url": "XXX",
        "resource": "element_sets"
    },
    "extended_resources": []
}

{
    "id": 37,
    "url": "XXX",
    "order": 100,
    "name": "Contributor",
    "description": "An entity responsible for making contributions to the resource",
    "comment": "",
    "element_set": {
        "id": 1,
        "url": "XXX",
        "resource": "element_sets"
    },
    "extended_resources": []
}

Element 37 has been translated:

#. Dublin Core: Contributor element name

@zerocrates
Copy link
Member

The one you're listing first isn't Dublin Core metadata: note that it says it's in item set number 3.

"Miejsce urodzenia" isn't being translated there, it's Item Type metadata that was created with that label. The elements API doesn't translate those names at all.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants