Currently records migration do not consider non-required fields.
In this issue we should migrate them. if possible. In case any field can't be migrated now, we should open an issue and tackle it separately.
Note on vocabularies
Some fields are values from controlled vocabularies (e.g. licenses). Since both zenodo-rdm and inveniordm have vocabularies, its values should be resolved and validated. Moreover, in Zenodo we have "aliases" for some of these vocabularies (e.g. licenses).
Therefore, we must migrate the vocabularies themselves before migrating records and provide some kind of compatibility for the aliases.
This issue is out of scope from this task, for now, and should be tackled separately. That said, in this issue we can assume that the vocabularies are already migrated (e.g. no resolving nor validation is needed for now)
Currently records migration do not consider non-required fields.
In this issue we should migrate them. if possible. In case any field can't be migrated now, we should open an issue and tackle it separately.
Note on vocabularies
Some fields are values from controlled vocabularies (e.g. licenses). Since both zenodo-rdm and inveniordm have vocabularies, its values should be resolved and validated. Moreover, in Zenodo we have "aliases" for some of these vocabularies (e.g. licenses).
Therefore, we must migrate the vocabularies themselves before migrating records and provide some kind of compatibility for the aliases.
This issue is out of scope from this task, for now, and should be tackled separately. That said, in this issue we can assume that the vocabularies are already migrated (e.g. no resolving nor validation is needed for now)