Add Data Type to Mapping screen so it can be set at the time of data import

[RDmitchell]

SHA: 294626cbd

Right now, when importing data, there is not a way to specify the data type. That has to be defined after the data is imported in the Column Settings screen.

It would be much better for users if those could be set at the time of file import, ie, in the Mapping screen, as well as keeping those definitions in the Column Settings screen so they could always be changed after the import.

Right now, in Column Settings, the Type can be defined. If it is left blank, the program defaults to types that may or may not be appropriate. Here are the current types:

The Type cannot be changed for canonical fields, but needs to be set for extra data fields.

Type should be added to the Mapping screen.

• Type for canonical fields would be displayed, but presumably not editable, and the units would also be displayed in the Measurement Units column, as happens now
• For extra data fields, the pulldown list would be available to set the Type and the units associated with that type would be displayed in the Measurement Units column as happens now

These Type settings would get saved with the Column Mapping Profile.

Question

• Should the user be able to change/set the units for extra data fields?

[RDmitchell]

@anchapin -- great, thanks for making that connection !

[RDmitchell]

@isalanglois / @nllong -- It would be nice if this could get some sort of priority, although I know there are a ton of things that need to be done.

I just discovered that unless you define the data type you can select the fields in the Insights world. I think this makes sense, but the user doesn't know that. In general, most of what users are importing go into Extra Data and so those fields definitely need to have a data type assigned before they can be used in Insights.

[isalanglois]

@RDmitchell We'll flag this for group discussion on our next dev call this week

[RDmitchell]

Great, Thanks !

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity within 60 days. It will be closed if no further activity occurs. Thank you for your contributions.