omeka / Omeka

A flexible web publishing platform for the display of library, museum and scholarly collections, archives and exhibitions.
http://omeka.org
GNU General Public License v3.0
487 stars 194 forks source link

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

Open mw0000 opened 9 months ago

mw0000 commented 9 months ago

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: https://github.com/omeka/Omeka/blob/cd661c35fcbe1563eb880927635afa972c5a07fd/application/languages/pl.po#L94

zerocrates commented 9 months ago

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.