You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For #10404, we'll need a UI tool that'll allow the construction of arbitrarily nested trees. For example, we might support a 4-level tree:
Subject
Mathematics
Calculus
Integral Calculus
Differential Calculus
Geometry
Trigonometry
Non-Euclidean Geometry
Discrete Mathematics
Logic
Set Theory
Physics
...
Biology
...
Funder
Agency A
Agency B
Agency C
Thematic Area
Adaptation to Climate Change
Environmental Sustainability
At the simplest, we could just require a tool that supports the presentation of the tree, and leave editing (and rearrangement and deletion confirmation) to modals.
We may need fine-grained server-side control over how the tree can be re-arranged -- for example, control over "Mathematics" and its contents could belong to User A, and "Geometry" to User B, so while it's tempting to permit drag-and-drop rearrangement, that might complicate things unnecessarily. Rearranging the tree should be an uncommon task.
The text was updated successfully, but these errors were encountered:
We already have similar functionality in our new navigation, so implementing this should be straightforward. It will work like the PrimeVue panel menu component found here: https://primevue.org/panelmenu/
The "Add Category" option will only allow the addition of main categories, removing the form field for the parent component.
To add subcategories, you can click "More Options" and add child items below the main categories. The table will keep expanding with nested categories unless a limit is set.
Also I think we should only allow ordering of main categories i.e. the first level and nothing below that
If an editor/section editor is assigned to a category no matter the level we display them in the table
For #10404, we'll need a UI tool that'll allow the construction of arbitrarily nested trees. For example, we might support a 4-level tree:
At the simplest, we could just require a tool that supports the presentation of the tree, and leave editing (and rearrangement and deletion confirmation) to modals.
We may need fine-grained server-side control over how the tree can be re-arranged -- for example, control over "Mathematics" and its contents could belong to User A, and "Geometry" to User B, so while it's tempting to permit drag-and-drop rearrangement, that might complicate things unnecessarily. Rearranging the tree should be an uncommon task.
The text was updated successfully, but these errors were encountered: