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

Allow 'inheriting' distribution map query from higher taxa #340

Open
m-r-c opened this issue Apr 28, 2016 · 5 comments
Open

Allow 'inheriting' distribution map query from higher taxa #340

m-r-c opened this issue Apr 28, 2016 · 5 comments
Assignees

Comments

@m-r-c
Copy link
Contributor

m-r-c commented Apr 28, 2016

#339 will give editors greater control over the query used to produce the map. This will, however, become tedious when defining the map for multiple profiles.

It should be possible to provide an option to copy the query for a higher taxa (e.g. the genus when editing a species profile) and change the LSID to the one for the profile being edited.

@m-r-c
Copy link
Contributor Author

m-r-c commented Apr 28, 2016

#339, #156, #340, #222, #221 are all related

@m-r-c
Copy link
Contributor Author

m-r-c commented Apr 29, 2016

Question: should the inheritance be 'on the fly' or persistent?

@m-r-c
Copy link
Contributor Author

m-r-c commented May 13, 2016

Taking this out of the sprint, as I'm not sure it's actually useful.

Chances are the facet options between the higher taxa and the subordinate are going to be quite different, so copying the query string as a template may not achieve anything.

To be confirmed.

@m-r-c m-r-c added the question label May 13, 2016
@m-r-c
Copy link
Contributor Author

m-r-c commented May 23, 2016

Discussed with Michael: there are a number of facets that would be very useful to be able to inherit, such as location, attribution, etc.

As long the inerited facet list is visible on the edit page so the editor can remove inappropriate facets then this feature would be useful.

@m-r-c m-r-c removed the question label May 23, 2016
@m-r-c
Copy link
Contributor Author

m-r-c commented Jun 29, 2016

This should work something like the following:

  • the user configures the map for a higher taxa (e.g. the genus)
  • the user then goes to the map config for the lower taxa (e.g. species) and selects an option to inherit the config (perhaps this could be default behaviour, or configured at the collection level?)
  • the system fetches the custom query string for the genus and:
    • changes the q= from the genus to the species;
    • compares the list of facets in the query with the list available for the species and drops any that are not available
    • likewise for the colour by option: remove it if that option is not applicable for the species
  • applies the modified query to the species

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

2 participants