cohort pathway - unable to import from existing pathway's json code

[jhardin29]

Expected behavior

Select json code from existing cohort pathway (17 in production) and open new cohort pathway in beta, navigate to utilities and select existing json code delete it and use ctrl c to import it to new cohort pathway; expectation is that cohort pathway will be populated.

Actual behavior

Cohort pathway is not populated.

Steps to reproduce behavior

Select json code from existing cohort pathway (17 in production) and open new cohort pathway in beta, navigate to utilities and select existing json code delete it and use ctrl c to import it to new cohort pathway.

###Enhancement Request
Can a utility be added to copy the cohort pathway similarly to how an existing cohort is copied.

[anthonysena]

Thanks for the time earlier to review this @jhardin29. After stepping through this, there does not appear to be a problem with the pathways import. However, there is an opportunity to improve the usability of the import/export functionality overall since it is not very clear what a user should do when exporting/importing into the system.

The workflow is currently:

• Navigate to a pathway analysis, click the Utilities tab. Next, click the export pill tab and copy the big JSON blob from the text display to the clipboard.
• Next, create a new pathway analysis. Again, navigate to the Utilities tab. Click the import pill tab. Paste in the JSON blob to the text box and click the Import button:

The fact that the "Import" button (that does the work) is located directly below another screen element labelled "Import" does not make it very clear that one is to navigate and the other is to perform an action. Noting this here so that we an address it for 2.8

[jhardin29]

Can we also please apply this enhancement request to the characterization import feature?

[pbr6cornell]

In ATLAS 3.0, we need to make all import/export features clear and consistent across all functions.