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

custom sort for components in annotation #49

Open
kabikaj opened this issue Sep 12, 2020 · 2 comments
Open

custom sort for components in annotation #49

kabikaj opened this issue Sep 12, 2020 · 2 comments

Comments

@kabikaj
Copy link

kabikaj commented Sep 12, 2020

Hi! I would like to know if there is a way to create a custom sort for the components in the annotation interface, so that we could place the most relevant components on top and the least at the bottom. I am thinking of the possibility to add numbers to the components (01, 02, ...) to force the order we want, but I would like to know if there is a cleaner way to do this. Thanks!

@kabikaj
Copy link
Author

kabikaj commented Sep 15, 2020

I have been working more on this and the problem is more complex. Let me explain: we have a very complex structure of components. This is because the point of our research is to understand better how the elements we defined work. This makes them also very important to us. The problem is that, as the classification is complex, we would befenit a lot from having a nested structure. In this way we will have a few parents componenets and only when we click on one of them, then a second level of componen children is expanded, and so on. We would need actually three levels of components in order to organise everything in a nice way. Are there any chances that this is possible? thank you!

@pastokes
Copy link
Contributor

Thanks for your input. Yes, we often discussed this idea of sub-components, and yes it would be great to implement but it wouldn't be very straightforward, I fear, and at the moment we have no resources at all for development. At a minimum, I could imagine keeping flat annotations in the back end but adding a layer to the search interface for what you want.

Still, we've tried to keep the search interface relatively simple as we assume that every project will need different features, and so the search is relatively customisable if you're familiar with Django. There are some hints in the wiki at Search Page (customisations).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants