Dataset description migration to different profile
Administrators and users should be able to migrate dataset descriptions to other profiles and other profile versions.
Fields that can be mapped easily should be automatically proposed. Not mapped fields should be presented to the user for further action (e.g. manual mapping or removal).
Migration should be done on the basis of
- exact field properties matching
- field semantic description (perhaps and type)
- field name and type
- assumption ("by content", i.e. using type, source)
Users should be able to enforce other transitions.
Users should be able to store the model for migration under a "migration model" associated with the target profile (and optionally a source profile) for future reference and reuse.