Localized item’s `entry_status` is “Standard”

[strogonoff]

While migrating IEV data to register glossary format, I noticed that items have entry_status: Standard.

Our registry schema uses the following statuses, in accordance with ISO 19135-1 (see 6.2 and 7.5.2):

const ITEM_STATUSES = [
  'submitted',
  'valid',
  'superseded',
  'retired',
  'invalid',
] as const;

Example:

pol:
  id: 904-03-14
  terms:
  - type: expression
    normative_status: preferred
    usage_info: systemu
    designation: tryb czuwania
    gender: m
    plurality: singular
  - type: expression
    designation: tryb nieaktywny
    gender: m
    plurality: singular
  language_code: pol
  notes: []
  examples: []
  entry_status: Standard
  review_decision_event: published

(cc @ronaldtse)

[strogonoff]

If entry_status: Standard maps to register item status valid, we can map that value at the “Glossarist Desktop YAML -> Glossarist registry YAML” conversion stage.

[skalee]

@ronaldtse Could you clarify on this one? Looks like every row in the spreadsheet has "Standard" in the STATUS column. There are no other values, I've checked that already.

[ronaldtse]

Yes. Entry status “standard” maps to “valid”. In “Status” we only see the value “Standard” because the IEV export we are given only contains published content — behind there are other status values — I suspect they include the “in-process” and retired statuses. The full database is probably twice as large.

[skalee]

@strogonoff I can make another release if you want it fixed right now.

[skalee]

If entry_status: Standard maps to register item status valid, we can map that value at the “Glossarist Desktop YAML -> Glossarist registry YAML” conversion stage.

I guess I can simply replace "standard" with "valid" in our export tool, unless @ronaldtse says we need to keep "standard" in these YAMLs.

[ronaldtse]

I guess I can simply replace "standard" with "valid" in our export tool

This is totally fine with me 👍 We just need to document this somewhere so we know the status mapping.

[skalee]

I'm not familiar with Glossarist internals so I'll do whatever you guys prefer. Fixing it in the export tool is trivial.

[ronaldtse]

@skalee right, can we have this change done so @strogonoff can prepare for his demo this Friday? Thanks!

[skalee]

@ronaldtse Pull request created. I will make a new release when I merge it.

[skalee]

@strogonoff v0.23.20201217 released in this repo. Soon concepts.zip will be generated by GHA.

[ronaldtse]

Thanks @skalee !

[strogonoff]

@strogonoff v0.23.20201217 released in this repo. Soon concepts.zip will be generated by GHA.

Awesome, thank you!