Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Clarification needed on term's classification and designation's normative_status #191

Open
skalee opened this issue Jun 8, 2021 · 4 comments
Assignees
Labels
enhancement New feature or request

Comments

@skalee
Copy link
Contributor

skalee commented Jun 8, 2021

Following pseudo YAML illustrates the problem, only relevant fields included:

eng:
  terms:
    - type: expression
      normative_status: (always "preferred")
      designation: (taken from TERM column)
    - type: expression
      normative_status: (taken from SYNONYM1STATUS column)
      designation: (taken from SYNONYM1 column)
    - type: expression
      normative_status: (taken from SYNONYM3STATUS column)
      designation: (taken from SYNONYM2 column)
    - type: expression
      normative_status: (taken from SYNONYM3STATUS column)
      designation: (taken from SYNONYM3 column)
    - type: symbol
      designation: (taken from SYMBOLE column)
  classification: (taken from SYNONYM1STATUS column)
  entry_status: (taken from STATUS column, in fact always "valid")

(Only relevant fields are included. Of course some spreadsheet columns may contain more than one designation, but let's skip that for simplicity.)

What I want to say is that localized concept's classification and normative_status for the 2nd term are taken from the same SYNONYM1STATUS column, and that smells like a bug. There is no TERMSTATUS column or anything like that in the spreadsheet. There is STATUS column, but it always says "Standard" and is used for entry_status:

def extract_entry_status
case find_value_for("STATUS").downcase
when "standard" then "valid"
else nil
end
end


cc @ronaldtse

@skalee skalee added the question Further information is requested label Jun 8, 2021
@ronaldtse ronaldtse assigned HassanAkbar and unassigned ronaldtse May 24, 2022
@ronaldtse ronaldtse added enhancement New feature or request and removed question Further information is requested labels May 24, 2022
@ronaldtse
Copy link
Member

@HassanAkbar can you help address this issue? Thanks!

@HassanAkbar
Copy link
Member

@ronaldtse What should we do in this case? There is no column in the sheet for classification and currently, the classification value is obtained from the SYNONYM1STATUS column which is also used for the normative_status value.

Also currently there is no other value except Standard in the STATUS column and it is used for the entry_status value.

@ronaldtse
Copy link
Member

@HassanAkbar the full dataset (that contains historic information) will have other values in the STATUS column. Is the point to make these status values configurable per dataset?

@HassanAkbar
Copy link
Member

@ronaldtse There are actually 2 points

  1. There is no column in the sheet for classification and currently, the classification value is obtained from the SYNONYM1STATUS column which is also used for the normative_status value. According to skalee this seems like a bug or this might cause bugs in the future because the classification is for overall concept while SYNONYM1STATUS is for synonym 1.
  2. Also currently there is no other value except Standard in the STATUS column and it is used for the entry_status value. (You have answered this question in the last comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants