-
Notifications
You must be signed in to change notification settings - Fork 4
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
Change dataset id naming in ECV export #192
Comments
An example of this is the following: Perhaps we should use an id like 'dataset1', which could be composed from 'dataset' + id/pk Before doing anything, check with annotators! Because I don't know yet what would happen if you change this value. |
Alright, we can just use dataset.id for this instead of the name. |
…N files (.eaf) manually to accomodate these changes, make sure you backup those files before editing. - Using 'signbank-dataset-<id>' instead of dataset.name (eg. "VKK_FinSL"), because if someone would change the name of the dataset, it would mess up the ELAN files.
Currently the name of the dataset is tied to Elan ECV export. Changing the dataset name might therefore be problematic.
So I think we need to create a new field for datasets, one that will be used as an ID in ELAN. One that can't be edited. We could use the id from the database, but that would limit our options if we ever want to move to another database, the ID's might change then and break the ELAN connectivity.
Also we might want to use this new dataset ID for the elan export's url too.
The text was updated successfully, but these errors were encountered: