subject (dv5 db field) is a new field in dv4, and a required field. It is additional to the existing fields keyword and topicClassification, but, unlike those fields, does not originate from the DDI schema.
Given that none of the migrated studies will have a value for this required field, what impact will a lack of value have on database integrity and DDI export in dv4?
We expect that users who edit their existing metadata after migration will be prompted to supply a value. But many users will not edit their metadata and so will not be prompted. Should we ask all users to supply a Subject value for each study/dataset after migration?
Issue sp5
subject (dv5 db field) is a new field in dv4, and a required field. It is additional to the existing fields keyword and topicClassification, but, unlike those fields, does not originate from the DDI schema.
Given that none of the migrated studies will have a value for this required field, what impact will a lack of value have on database integrity and DDI export in dv4?
We expect that users who edit their existing metadata after migration will be prompted to supply a value. But many users will not edit their metadata and so will not be prompted. Should we ask all users to supply a Subject value for each study/dataset after migration?