feat(central): when creating a new schema from a template I should see progress analogous to when uploading a schema via zipfile

[BrendaHijmans]

What version of EMX2 are you using (see footer) 10.5.2

Describe the bug While creating a new schema with catalogue test data, the 'Create database' window does not disappear. The schema with data is made though.

To Reproduce Steps to reproduce the behavior:

1. Go to https://emx2.dev.molgenis.org/apps/central/#/
2. Sign in
3. Click on + to create a new schema
4. Give schema a name, at template choose: DATA_CATAOGUE, load example data = True
5. Window of creating the schema gets stuck

Expected behavior A clear and concise description of what you expected to happen.

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Add any other context about the problem here.

[mswertz]

I conclude this is a server issue, see

Can you check with 'ops'?

[BrendaHijmans]

The issue also occurs when making a CohortStaging schema without data (template = DATA_CATALOGUE_COHORT_STAGING). Sometimes the request gets through. Sometimes it does not, because it takes t long to make the schema. It does not occur when making a Network staging schema (template = DATA_CATALOGUE_NETWORK_STAGING), which is not incorporated in the profiles yet. Maybe the profiles are slow?

[dtroelofsprins]

I'm experiencing the same issue after adjusting the BBMRI-ERIC Disease Types table's datamodel:

• changed a one-to-many to many-to-many (within the table itself)
• add more data (not rows, but added data to a column).

Create database window with spinner keeps showing, although the database is created.

[esthervanenckevort]

Probably a different time-out in the frontend HTTP server on Azure than on OpenStack?

[esthervanenckevort]

We should change the code to run the import in a job and give regular updates, just like when using the upload functionality.