Import

you can import assets directly from various source formats, you can import from a local file or import from a third party integration, such as veeva vault to import content from another standard or study in ryze, see docid\ ya frrumnj2agy2vjomk4 source files in edc formats (such as, rave als or veeva) are converted and merged automatically there are different import options so that you can partially update existing assets or make incremental changes, such as updating nci terminology with a new version imported assets can retain links to standards and ryze specific properties, preserving asset relationship links and metadata integrity supported assets/properties the import option supports odm/define xml and fdx data formats by default all odm/define based asset types are supported supported assets/properties means that ryze specific properties (for example, properties such as alias, maps to, maps from, therapeutic area) are preserved during external file imports the importer ensures that these properties are not lost when files are re uploaded from systems like rave or veeva best practice create a new version it is recommended that you create a new version of your standard/study before importing assets you may have to transition the lifecycle state to create a new version use comparison reports comparison reports can be used to compare versions, so you can see a list of changes between the previous asset group and the new version import options remove all existing assets assets all existing assets are removed this replaces previous upload functionality relationships existing relationship links are replaced use case you want the asset group to match the imported file exactly you want to overwrite all existing content remove all assets not present in the import assets delete any assets that are not included in the import file assets that do exist are updated with the imported content relationships for assets not present in the import, relationship links are removed for assets that already exist in ryze, relationships are retained use case a you have a form that has new questions, you want to update the existing form in ryze to include the new questions use case b making partial updates, for example, you have a new version of nci terminology which has new terms for a terminology do not remove any assets assets no assets are deleted existing assets that match (based on identifier) are updated, unmatched assets remain unchanged relationships existing relationship links are not affected use case you want to import a file with new terminologies remove all supported assets that become unreferenced during the import assets add all new assets from the import file delete supported assets that are no longer referenced after the import update all existing matching assets where differences exist relationships if an asset is referenced, for example by another asset group, the asset is retained use case use this option if you want to synchronise updates from edc systems but also preserve ryze properties for example, annotations or aliases notifications all import tasks are displayed in the imports tab this screen lists all imports a user has run, along with their status and any validation issues you can review validation issues, choose whether to continue if issues occur, and manually remove completed or failed imports imports include details such as file name, type, start time, asset group location, and import type