Don't allow curators to publish data that doesn't fit the data shape we need on the front end

[heidimok]

Issue

We have run into a few issue recently that blocked deployment of CASEI from staging to production. It seems that a common thread is related to data in production that doesn't match the data shape we need in the frontend. When curators add to the MI, sometimes they may input data without knowing the data shape we need. Currently there isn't always much guidance or prevention so they have no idea they are causing the deployment to fail.

#621
#617 - spatial bounds input

Desired Outcome

• Must: Curators cannot publish data that doesn't fit the data shape we need on the MI
• Must: Curators get notified of which fields are incorrect
• Nice to have: Curators are provided with the correct shape/format to make the fix. This would be ideal but there is a workaround which is to review existing published data to see what is the correct input.

#620 - This related issue shows a mockup of what would be ideal from a user experience perspective

[Tammo-Feldmann]

@heidimok , just a quick note here that the most recent issue of deployment for CASEI had a different underlying issue. We ran into two Gateway Timeouts on the backend. The /doi and /instrument endpoints would time out on request. I have discussed with @willemarcel that we will likely need a caching solution for those endpoints in the backend. This doesn't change that we would generally want better validation for a match between frontend and backend types but the current issue ended up not being related.

[heidimok]

Oh, thanks for the update here, much appreciated. Do we have an idea of why this timeout issue suddenly happened now whereas it didn't before? I'm just curious from a future perspective.

[heidimok]

Update that the immediate issue of deploying from staging to production has been addressed so this issue isn't blocking anything.

But we will leave this issue in the backlog as it remains relevant. While data curators can use the Validate feature on the MI to check their inputs before saving data, there is no reason why the system should allow data to be saved if it's going to break the front end build.