The current index list page can grow quite long and chaotic, especially since you sometimes want to create separate indices that logically belong together because they use different fields.
Maybe we should create some way to group indices into projecs/folders? Simplest option would be to add a field in the system index that lists to 'project' or 'folder' for each index, and use that to create either a nested or a fixed 2-level (projects -> indices) structure in the index list page.
Possible additional features could be
Do we want nesting, or just one level? If just one level, should every index live in a project?
authorization per project. I'm not a fan of this because it would be quite an overhaul and also has downsides when e.g. moving indices, and would almost force a fixed two level structure. But maybe this does make more sense for most users?
extra information on ownership, provenance, links to project pages etc?
The current index list page can grow quite long and chaotic, especially since you sometimes want to create separate indices that logically belong together because they use different fields.
Maybe we should create some way to group indices into projecs/folders? Simplest option would be to add a field in the system index that lists to 'project' or 'folder' for each index, and use that to create either a nested or a fixed 2-level (projects -> indices) structure in the index list page.
Possible additional features could be