Closed kaskranenburgQ closed 4 months ago
I wonder whether these scenarios are still relevant enough to keep them as featured scenarios.
To add to my previous comment, these scenario likely refer to the region code RGNB01
(see the Dataset Manager). This region is still maintained on ETLocal but no longer available on ETSource (see the datasets).
Writing a migration therefore will likely have no effect, since the region is no longer available. The two options are then:
Finally, notifying @noracato, it would be useful at some point to add some error routing for this. Something like: "The region modelled in this scenario is no longer available in the model, contact Quintel for questions". What do you think?
After the discussion on the general channel I would go for option 1. Specifically, I would only "un"feature the scenario and not remove the scenario altogether. Additionally, I would write a mechanical turk test that runs a single query for each featured scenario, just so we know that each featured scenario can be opened. Can you pick this up @kaskranenburgQ?
it would be useful at some point to add some error routing for this
For the featured scenarios that would be a great idea. To keep the featured page, but without the open button.
Also handy because currently we run into the problem that, without being able to view the scenario's featured page, there is no way to press the 'unfeature' button anymore. I have to go manually into the database now to unfeature it...
I have to go manually into the database now to unfeature it...
Could you pick this up at some point @noracato?
On the website we have 2 featured scenario's for West-midden Brabant.
If you click on one of them, nothing happens. Since no introduction page for the featured scenario opens, it is not possible to remove them.
After a short consultation from the @noracato we discovered that this is possibly broken since the area code of the scenario does no longer exist.
A migration thus needs to be written which replaces the area code for all scenario's.
Notifing @mabijkerk, will pick this up myself.