The latter script should better be moved to jskos-tools anyway.
Labels are ignored but may later be used for error checking.
Because import is error-prone, the import may first go into a local staging storage to let users accept/abort the import (e.g. "detected 12 mappings between 12 concepts from RVK to 10 concepts from BK. Import to local mappings yes/no?"). Most common errors to detect and give feedback during import:
missing column labels fromNotation, toNotation
unknown column labels (can be ignored but better give a warning)
invalid notations (requires information about syntax of valid notations)
This requires additional information about the CSV table such as which concept schemes the concepts belong to and how to build URIs from notations.
The conversion step has already been implemented here in Perl:
and to some degree in JavaScript:
The latter script should better be moved to jskos-tools anyway.
Labels are ignored but may later be used for error checking.
Because import is error-prone, the import may first go into a local staging storage to let users accept/abort the import (e.g. "detected 12 mappings between 12 concepts from RVK to 10 concepts from BK. Import to local mappings yes/no?"). Most common errors to detect and give feedback during import:
fromNotation
,toNotation