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

Add tag support #165

Open
Apollo3zehn opened this issue Dec 17, 2024 · 1 comment
Open

Add tag support #165

Apollo3zehn opened this issue Dec 17, 2024 · 1 comment
Labels
enhancement New feature or request web UI

Comments

@Apollo3zehn
Copy link
Member

This solves the "in which folder to I sort my files" problem. In the long run we will have a large amount of catalogs and the folder concept will reach it limits. It would be nice to have tags to group catalogs into locations, projects, topics and other categories.

How does this work in combination with the new aliases?

Tagged catalogs still need a name. And sometimes (e.g. in case of the HLL), the name is ugly (e.g. an id) and we need a prettier one: the alias.

How does this work in combination with Nexus.Federation?

Aliases cannot be defined from within the sub Nexus to be displayed high in the hierarchy in the main Nexus because currently aliases must be absolute paths beginning with a forward slash.

But main Nexus could define a special plugin which provides all these aliases. Maybe via .json file or web page to let users configure it easily. But this is no important feature right now.

Tags, on the other hand, will work for the main Nexus as well. But a big problem with tags is that catalogs are being loaded lazily and so many catalogs will not appear when doing a tag search :-(

I currently don't know how to solve that (lazy loading vs tags which require eager loading). Maybe Nexus needs some kind of cache of catalogs seen so far which updates itself when trying to actually access that catalog.

@Apollo3zehn Apollo3zehn added enhancement New feature or request web UI labels Dec 17, 2024
This was referenced Dec 17, 2024
@Apollo3zehn
Copy link
Member Author

Maybe use that catalog cache in general to avoid catalog being loaded before their first access? But that requires the cache to be invalidated when something changes ... just an idea

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request web UI
Projects
None yet
Development

No branches or pull requests

1 participant