Ticket #840 (assigned Task)

Opened 4 years ago

Last modified 4 years ago

Allow reference to already described components/grid components

Reported by: gerry Owned by: gerry
Priority: critical Milestone: V1.2 Questionnaire release
Component: WP6 - CMIP5 Questionnaire Version:
Keywords: Cc: rupert, charlotte, phil, marke
Requirement: http://metaforclimate.eu/Work-Package-2/Developing-the-CIM/Project-Requirements-summary.htm


A useful usability feature would be to allow the user within the questionnaire page to reference a previously described component (or grid component) from another model (within the same centre) instaed of having to reenter information. This is in addition to the 'copy model' button already in existance which may not always solve the issue. One proposed solution is that at each realm level component (or horiz/vertical level in grid), there is a select box to say 'using already described component' with a dropdown box that lists currently available model/components for that particular centre. On choosing this, the empty form fields for new information would subsequently be removed from the page.

Change History

comment:1 Changed 4 years ago by gerry

  • Status changed from new to assigned

comment:2 Changed 4 years ago by rupert

Hi Gerry,

1: is there any reason why we should limit the option to realm level components? Perhaps this is all users will want? Perhaps Mark E. has a view on this.

2: should we only allow matching with components of the same type? (I would say yes)

2: What would you do with the tree view at that point? I would suggest the easiest solution would be to prune the view to that level so child components disappear, although that might be confusing.


-- Rupert

comment:3 Changed 4 years ago by gerry

Hi Rupert,

Perhaps a better idea here would be that instead of pruning the tree is that in the case whereby a user 'refers' to a component (at any level) it's chld components (i.e. references to each of it's child components) are automatically filtered downwards onto the respective child component pages (with the form field boxes greyed out/removed as with the original page). In this way, a user can refer to a high level component but also have the ability to still modify a low-level parameter deep down within that component. The navigation tree could also therefore remain in this case. Is this something though that can be managed in writing through to xml?

comment:4 Changed 4 years ago by gerry

.....not sure if that would break though in the sense that I've referred to a component at a high level, but actually have differences low down within that component. This hurts my head :-).

comment:5 Changed 4 years ago by gerry

.....so I actually think that in the case of referring to another component then your first idea of pruning the navigation tree is probably best. In the example I gave where you may want to pull in a previously described component but make minor changes to that, then I think we need to add a 'copy from other component' type button.

comment:6 Changed 4 years ago by gerry

  • Component changed from WP1 - Project Management to WP6 - CMIP5 Questionnaire

comment:7 Changed 4 years ago by rupert

Yes, I agree with your last comments. The simplest solution is for refer to mean you are referring to a component and all of its siblings. If you want to make changes at any level of the tree c.f. the reference version then you need to make a copy.

We could allow references (or not) for each component in the hierarchy if there is a strong use case for it. It would not be different to modify the translator to support this and the CIM already does. However, it is an interesting scientific question whether two components with the same properties, but with different siblings, can be considered to be the same or not. I would naturally think that a component is the sum of its parts.

It would be good to know whether Mark E. and Phil think this is a good idea or not. Phil certainly mentioned it for grids and I Mark has mentioned the problem of keeping multiple copies up to date. It is good for the CIM output too as we can reference the same instance (i.e. use the same ID) so any comparison tools will know that any such components are the same.

Note: See TracTickets for help on using tickets.