geolexica / geolexica-server

Generalized backend for Geolexica sites
2 stars 1 forks source link

Term's normative status (formerly classification) is not localized #56

Open skalee opened 4 years ago

skalee commented 4 years ago

We need to find a way of displaying term's (designation's) normative status (formerly classification) in a localized way, taking into account that there may be more than one term per language.

This is best illustrated on https://isotc211-staging.geolexica.org/concepts/150 of TC211 glossary, which is defined as follows (some entries removed for clarity):

---
term: ellipsoidal height
termid: 150
eng:
  id: 150
  term: ellipsoidal height
  language_code: eng
  classification: preferred
rus:
  id: 150
  term: эллипсоидальная высота
  language_code: rus
  classification: admitted

Rendered HTML is as follows (again, some elements removed):

<article
  class="localized-term field lang-eng status-valid classification-preferred"
  id="entry-lang-eng">

  <p class="field-name">eng</p>

  <div class="field-value">    
      <h3 class="localized">ellipsoidal height</h3>
  </div>
</article>

<article
  class="localized-term field lang-rus status-valid classification-preferred"
  id="entry-lang-rus">

  <p class="field-name">rus</p>

  <div class="field-value">
      <h3 class="localized">эллипсоидальная высота</h3>
  </div>
</article>

<section class="field info">
  <p class="field-name">info</p>
  <div class="field-value">
    <ul class="labels">
      <li>status: valid</li>
      <li>classification: preferred</li>
      <li>date accepted: 2003-02-15</li>
    </ul>
  </div>
</section>

Problems:

Also RDFs are broken. However they will undergo overhaul anyway, and the way forward has been discussed already. Indeed this issue was addressed in format described in #2, also what to do with the new data models has been already discussed. Hence, this issue is related to HTMLs only.

NOTE: iev-demo site is affected by this issue as well.