-
Notifications
You must be signed in to change notification settings - Fork 7
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
Difficult to override lexeme ID
#262
Comments
I remember we decided to leave Local_ID for that purpose of the original
ID, as done in the dataset shared (this can also be in conflict with
lexibank ID format, if I understand properly and is not checked). Would
local_id be enough for you?
|
I just checked here:
https://github.com/intercontinental-dictionary-series/keypano/blob/main/lexibank_keypano.py
If ID is always created, we need indeed discuss that, as it means we
would also have to revise datasets like the keypano, where we want to
inherit IDS ids.
|
Yes -- I'm using Local_ID but this feels like a workaround. If someone is explicitly specifying an ID then we should respect that. At the very least silently replacing given ID's with a generated one is surprising and unexpected which could lead to glitches (I only spotted this when I was analysing the CLDF data sometime down the track and could not figure out why the list of lexemes I needed was wrong). It's worse because it's only the lexemes (add_form*) that do this and languages, parameters, etc are quite happy to have my manually curated IDs. |
I think I agree that the call to |
I'm creating a dataset at the moment from a relational database and I'd like the lexeme IDs to be the primary keys from the database. I assumed that if I specified
ID=x
in the add_forms* call, then the ID would be kept, however, the code always callsself.lexeme_id
:pylexibank/src/pylexibank/cldf.py
Lines 115 to 120 in 8ae170c
Can we make lexeme_id be ignored if
ID
is given?The text was updated successfully, but these errors were encountered: