The label import should be rigged to allow arbitrary source databases (like WoRMS). Each label needs an external_id and external_db_id field and the DB needs a new label_databases table so each label has a unique reference back to its source database. There may be multiple labels with the same external_id (coordinate this with BiodataMiningGroup/dias-core#18).
Imported labels may get a custom name in Dias which may be different to the one of the source DB.
For each label database an "adapter" needs to be written that allows searching for labels (with a JS typeahead) and importing a label (recursively??) to a Dias label tree.
The label import should be rigged to allow arbitrary source databases (like WoRMS). Each label needs an
external_idandexternal_db_idfield and the DB needs a newlabel_databasestable so each label has a unique reference back to its source database. There may be multiple labels with the sameexternal_id(coordinate this with BiodataMiningGroup/dias-core#18).Imported labels may get a custom name in Dias which may be different to the one of the source DB.
For each label database an "adapter" needs to be written that allows searching for labels (with a JS typeahead) and importing a label (recursively??) to a Dias label tree.