List view

• Model catalog setup versioning

  Once a model setup is executed, we should make it "frozen" so when someone sees its execution, they are able to go to the original configuration. Otherwise if someone executes, edits the config and browses an old configuration they won't be seeing the original one. Solution: create a new version of a configuration setup if that setup has been executed.

  No due date
  0% complete0 open0 closed

• Update production client to use model catalog v1.7.0

  We are using v1.5 on the production site, we should update the portal to work with the model-catalog 1.7 and the graphql backend.

  No due date

  •1/3 issues closed
  33% complete2 open1 closed

• Connecting regions with Model Catalog

  No due date

  •0/5 issues closed
  0% complete5 open0 closed

• Link a new model in MINT

  We have polished the means to add a new model in MINT. However, there are problems when linking the model to the functionality of the system: - It is not clear what is required from the model uploader for the model to appear in MINT (execution) - It is not clear how the indices/indicators map to models

  No due date

  •6/8 issues closed
  75% complete2 open6 closed