Description |
|---|
Migrate a record and its related data from one project (source) to another project (destination). Primary use case: A study team expects to recruit and screen many more participants than they will enroll - The team create 2 REDCap projects - one for for storing all for all interested persons and one for storing data for all persons who screen and enroll as participants.
- When a participant screens in, the participant's record and a subset of their data can be migrated from the screening project (the source) to the enrolled project (the destination)
Set up notes: - The module is activated in the source project.
- There can be multiple destination projects.
|
Feature Type |
| External module (EM) |
Fees |
Minimum of $500 initiation fee, to cover the cost of help with set up and training. |
Eligible Projects/Project Status Dependency |
- Project Status at Request = Development
- Request to enable Auto Record Generation while building and testing the project.
- Because of the complexity of configuring and validating the tool, setting up the Auto Record Generation EM in a project in production is not supported.
- Support Track = Standard Service for Research
|
Request Process |
- Eligible Requestor: Project point person
- Point Person Submits Request
- Initiate request via
Project > Lefthand Nav Menu > External Modules link > View available modules button > Auto Record Generation > Request Activation button - Follow up with an email to the REDCap Team at redcap@ohsu.edu to describe the use case for the external module.
- REDCap Team Processes Request
- Gathers details via email and/or web ex meeting
- Sends estimate to point person and PI
|
REDCap Skills |
- Form building experience.
- Codebook or Data Dictionary familiarity.
|
Installation, Configuration and Implementation |
- Installation
- Study Team provides billing information.
- REDCap Team approves requests and activates module.
- The module is activated in the source project.
- There can be multiple destination projects.
- User Rights
- REDCap Admin assigns user permission to the module to the point person.
- The point person must be also be assigned to both the source and the destination projects.
- Configuration
- REDCap Team trains project builder how to configure the module for their project.
- Review if user rights should be granted to a back-up point person.
- Implementation Notes
- To migrate data, a field in source project must match with a corresponding field in the destination project that has same variable name and is the same field type.
- Only migrate from the source project the data that absolutely required to create the record in the destination project.
- For data quality reasons, do not enable the setting to "Overwrite data in destination project record every time data is saved in this project."
- For data quality reasons, make modifications to the migrated data in the destination project.
- "Name for New Record" should be the variable name of the record id field in the destination project, enclosed in brackets [var_name_for_record_id]
- Variable name in the source of field used to trigger record generation in the destination project should match the variable name of the record id field in the destination project.
- If the matching DAG already exists, then the record will be assigned to the existing DAG.
|
