Module that allows for a new record to be generated in another project (or the same project) on a flagging field being saved. Allows for data fields to be transferred to the new record as well.
MIT License
4
stars
3
forks
source link
Feature request: user-customisable field mapping #5
I have just discovered this module and am assisting a researcher that could benefit from it. The study has a recruitment project and a main project, with records needing to be imported from recruitment to main. This module is ideal except that it doesn't allow for recruited participants to be imported into different arms.
The recruitment project has two arms: one for cancer patients and one for healthy control. The main project has three, cancer + intervention, cancer control and healthy control. I was hoping that I could create a field in the recruitment project that allowed the user to set which arm the participant should be imported into, and that this module would set that by taking the value of a field in the source project like [target_arm] and assigning it to the [redcap_event_name] field in the destination.
One way to facilitate this and not override existing behaviour would be to have a checkbox 'auto-map all fields', and then a number of user-customisable mappings with a dropdown menu for source fields and a text box to type in the destination field (or a dropdown, since the module needs to have permission on both projects).
I have just discovered this module and am assisting a researcher that could benefit from it. The study has a recruitment project and a main project, with records needing to be imported from recruitment to main. This module is ideal except that it doesn't allow for recruited participants to be imported into different arms.
The recruitment project has two arms: one for cancer patients and one for healthy control. The main project has three, cancer + intervention, cancer control and healthy control. I was hoping that I could create a field in the recruitment project that allowed the user to set which arm the participant should be imported into, and that this module would set that by taking the value of a field in the source project like [target_arm] and assigning it to the [redcap_event_name] field in the destination.
One way to facilitate this and not override existing behaviour would be to have a checkbox 'auto-map all fields', and then a number of user-customisable mappings with a dropdown menu for source fields and a text box to type in the destination field (or a dropdown, since the module needs to have permission on both projects).