You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Dataverse Users Community
We are importing data from another system, which has provided mappings of its internal fields to DDI Lifecycle with the version number unspecified. Are there any restrictions on the DDI schema or version when using DDI import with the Native API? Is anyone aware of significant differences between the schema that may require attention when using the Dataverse DDI mappings as a bridge between the fields in the other system and Dataverse? Thanks. Youn
Victoria Lubitch
unread,
Mar 6, 2025, 2:53:40 PMMar 6
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to Dataverse Users Community
As far as I know Dataverse using DDI Codebook 2.5 and not LifeCycle. DDI import api only works for codebooks.
It maybe possible to create custom metadata block to mimic lifecycle.
And do import using json import api but then one will need crosswalk between json with custom metadata and existing xml. It is also possible to write custom exporter. Custom exporters now can be created outside of dataverse and be integrated with dataverse. https://github.com/gdcc/dataverse-exporters