Describe the issue
This issue applies to titles and alternative titles on both series and item records in the system. See this series record for an example.
In an initial CSV for importing data into OCHRE, location data for this item appears as three different TGN identifiers: 7013596, 7005493, 1000639. On the website, this series has three different location links: "Chicago", "Guatemala", and "Huehuetenango, Departamento de".
We have a local copy of TGN data that provides human-readable place names for TGN identifiers. It may make more sense to store human-readable place names in OCHRE rather than to look them up dynamically from a front-end.
Expected behavior
Place names should be human-readable on front-end websites.
Describe the issue This issue applies to titles and alternative titles on both series and item records in the system. See this series record for an example.
In an initial CSV for importing data into OCHRE, location data for this item appears as three different TGN identifiers: 7013596, 7005493, 1000639. On the website, this series has three different location links: "Chicago", "Guatemala", and "Huehuetenango, Departamento de".
We have a local copy of TGN data that provides human-readable place names for TGN identifiers. It may make more sense to store human-readable place names in OCHRE rather than to look them up dynamically from a front-end.
Expected behavior Place names should be human-readable on front-end websites.