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

Sorting Thesauri #7214

Closed
etj opened this issue Apr 2, 2021 · 0 comments · Fixed by #7225
Closed

Sorting Thesauri #7214

etj opened this issue Apr 2, 2021 · 0 comments · Fixed by #7225
Assignees
Milestone

Comments

@etj
Copy link
Contributor

etj commented Apr 2, 2021

Is your feature request related to a problem? Please describe.

Since GNIP 82 it is possibile to handle multiple thesauri.
Anyway they do not appear in any particolar order (creation order probably).
We want to be able to show them in a given sort order.

Describe the solution you'd like

  • Add a new field for sorting thesaurus at will. Integer, not null, default 0.
  • The few places where the thesauri are selected from the DB should order the selection by the sorting field, and then by id, so to preserve the exisiting ordering whereas this new field is kept at its default value.

Describe alternatives you've considered
N/A

Additional context
N/A

mattiagiupponi added a commit to mattiagiupponi/geonode that referenced this issue Apr 6, 2021
@afabiani afabiani added this to the 3.2 milestone Apr 6, 2021
afabiani pushed a commit that referenced this issue Apr 7, 2021
Co-authored-by: Alessio Fabiani <[email protected]>
afabiani pushed a commit that referenced this issue Apr 7, 2021
Co-authored-by: Alessio Fabiani <[email protected]>
(cherry picked from commit ebb4153)
afabiani pushed a commit that referenced this issue Apr 7, 2021
Co-authored-by: Alessio Fabiani <[email protected]>
(cherry picked from commit ebb4153)

Co-authored-by: mattiagiupponi <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants