Skip to content
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

Improvements to the sub-selection parameters #85

Open
lmika-bom opened this issue Aug 13, 2015 · 3 comments
Open

Improvements to the sub-selection parameters #85

lmika-bom opened this issue Aug 13, 2015 · 3 comments
Milestone

Comments

@lmika-bom
Copy link
Contributor

OpenWIS allows for the creation of a sub-selection parameter UI for a DCPC by calling a SOAP method on a harness (the sub-selection parameter harness). Although this is helpful, it has a few limitations. Before the adaptation of the GeoNetwork 2.11, it might be worth looking into making some of the following improvements:

  1. Selecting geographic region that crosses the anti-meridian: the sub-selection parameter harness can show a map for the user to select a geographical region. At the moment, the user is unable to declare a region that crosses the anti-meridian. In certain cases, it might be necessary for users to do so, particularly users near the anti-meridian, so it would be nice to allow for this.
  2. Lat/Long entry boxes for the map field: instead of (or in addition to) item 1, it would be nice to include some entry boxes with map fields which will allow the user to specify the N, S, E and W point of the selected geographic region. That way, if the user knows the exact boundaries of the region they wish to extract, they could simply enter the boundary as decimal degrees (for example) instead of zoom and pan the map to the region of interest before selecting it by dragging the mouse.
  3. Full support for cross field validation: (this might be a hard one to do and will probably involve some changes to the harness API). At the moment, the sub-selection parameter harness can define a limited form of validation in which the valid choices for a particular field are dictated by the choices made in the field immediately above it. In cases where a more sophisticate validation scheme is required, it would be nice for fields to use any other sub-selection field when running validation checks.
@lmika-bom
Copy link
Contributor Author

Not worth doing for v3 but maybe worth considering when the sub-selection parameter feature is ported to v4.

@rogers492
Copy link
Contributor

This issue was moved to OpenWIS/openwis4#45

@woollattd
Copy link

reopened since OpenWIS v3.x is in maintenance mode for next 6 years so this still applies

@woollattd woollattd reopened this Jun 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants