-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Which fields do we need in a template? #93
Comments
btw, I have cleaned up "Edit as template" a bit. See e.g. https://csis.myclimateservice.eu/node/add/gl_step/template |
We need them in RA/IA. I wouldn't touch them now! Maybe we need some more. MCDA app implementation is currently on hold until we have have real impact results and adaptation scenarios to compare. |
Scenario Analysis App doesn't work anyore:
Did you remove any of the mcda fields or their default values? |
No, I didn't remove anything. At least not from the groups as they are today. I also didn't change anything in the "old" way of adding groups as far as I can remember, but I can double-check. I'm trying to make the new adding of a group work, but everything I do is limited to a group 17 and only done on group updates. And it doesn't work yet, sorry. |
FYI: i asked which fields we need just to know which ones to have pre-filled in the templates. I haven't changed the data model of GL-step |
Nothing to do here at the moment. If we ever want to change the data model, rules will not mind. |
Related to the work I just reported under #90 , it's important to know what template should contain. And which fields should be set.
The way I understand it, this is what needs to be in a template:
I'm not sure about the "MCDA *" fields. Do we need them in all steps? Just in one step?
Since we are going to work with "real" templates, we could clean this up and leave the MCDA fields only in the steps where it's needed. And if that's only one step, maybe it should be moved to the group (I don't really care, but having clean templates would be good IMO).
The text was updated successfully, but these errors were encountered: