Allow users to select source vocabulary for automated mapping from the mapper interface

[erummas]

Is there an existing issue for this?

• I have searched the existing issues

Is your proposal related to a problem or functionality gap?

Currently we are required to upload the data dictionary, I think it would be more streamlined if this feature is added to the mapper for pre-existing vocabularies. This could be split into two parts.

1. Allow vocab selection at table level for fields (currently not available even via dictionary)
2. Allow vocab selection at field level for field values (currently available via dictionary) [High Priority]

Describe your proposal

1. Allow vocab selection at table level for fields (currently not available even via dictionary)

   • This could be added in the edit table feature (as an optional select).
   • Use case : Data with multiple tests with each test recorded as a code e.g. Read Code) with table structure as
     ID | Test Date | 1....00 | 1151.00 | 1226.00 |

2. Allow vocab selection at field level for field values (currently available via dictionary)

   • A drop down with each field to select vocab for the values

Describe alternatives you've considered

No response

I'm part of a Project Team

No response

Anything else?

No response

Are you willing to contribute to developing this feature?

None

[AndyRae]

Yes this feels useful, couple of questions.

1. What would be the desired impact on then adding mapping rules?

• Is the principal objective to restrict for the mapping reuse?
• And/or to restrict a user doing manual mappings?

2. Is it a multi-select?

• If it is - what is the desired default, as there are many vocabularies, are they all selected?
• And the user has to unselect them?
• Or is it blank and the user opts in?

Example when the page is loaded:

• JMDC
• KDC

Or

• JMDC
• KDC