-
Notifications
You must be signed in to change notification settings - Fork 3
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
MLGT-General: Inconsistent behavior for "Entry Status" and "Term Classification" #1
Comments
The consequence of this is that the "Entry Status" and "Term Classification" fields are wrong for these 4 languages. We could fix the parsing, but the Excel sheet will still be inconsistent. |
these issues should be checked and fixed in the MLGT spreadsheet before
you try to modify the parser for any exceptions.
however if you just need testing data for the site just update what you
have to populate the db for the site.
Ronald Tse wrote:
… The consequence of this is that the "Entry Status" and "Term
Classification" fields are wrong for these 4 languages. We could fix the
parsing, but the Excel sheet will still be inconsistent.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1 (comment)>, or
mute the thread
<https://github.com/notifications/unsubscribe-auth/Ahdrv3iMg_2_2GkBmSBUMtEcGibxOzJDks5u6Ep5gaJpZM4ZW6LH>.
|
Agree, will wait for the outcome of the MLGT discussions! |
@ReesePlews is it possible to change the localized values (e.g. Spanish 'notválido' 'válido' 'superseded' 'retired') to English for these entries in the next issue of the MLGT? Thanks! |
I've found the following inconsistencies in the MLGT, and have updated the code to reflect to the best of my knowledge. ———— Russian действующий => valid ————— Finnish There’s no superseded or retired? Are these two terms equivalent? Spanish adminitido => “Administered”? What does this mean? |
In these languages, the operational language is used for these two fields:
In all other languages, English is used for the representation of these values.
e.g.
"Entry Status [OPERATING LANGUAGE]
Data Type:
Must be one of 'notválido' 'válido' 'superseded' 'retired'."
"Term Clasification [OPERATING LANGUAGE]
Data Type: Character String
Must be one of the following: 'preferente', 'admitido', 'deprecated'"
"
(And there's a typo for "Clasification" for all sheets).
Strongly suggest we only use English for these status values.
The text was updated successfully, but these errors were encountered: