Repository navigation
Rework of collaborative tags #4699
Description
Activity
Would it be possible to get tag colors like the labels on github?
Reacted by Kai, sunjam, Kilian Pfeiffer, berho, Aaron Lawson, André, Daniel Langbein, Michael Pfaff, jay armstrong, Roland Häder and 1 moreHi,
As referenced here:https://help.nextcloud.com/t/how-to-tag-multiple-files/21769
I would like to add the request for an option to apply tags when multiple files are selected. That is a very useful feature if you have/add multiple files.
Reacted by Alistair Marshall, berho, Aaron Lawson, Anton Karliner, Lars Becker, Z S, Tim Mundt and OutofMem+1
Something like this would be nice
- tag option on the toolbar next to download link:
- if clicked, expand the tag input form on horizontally (or maybe add it on a new line below as it is its current function in the details pane?)
Reacted by Jonas Sulzer, Arnie97, Anton Karliner, Lars Becker and michaeldelgado1- a listing of all tags for a file in the overview.
@gradinaruvasile we will only have a listing of the tags in the row, comparable to Gmail. Adding and removing tags in the row would be too much and too noisy. That’s done via the sidebar.
@disaster123 that’s what we want to add, as said.
@jancborchardt great - multiple colors or colors for tags would be great as well. If you have a lot of tags it gets very difficult to recognize them.
@disaster123 that's a different topic, you could open a separate issue for that. :)
@jancborchardt thanks added: #6778
41 remaining items
At school we have the problem that pupils can use and delete tags even if they do not have writing rights in that folder. So first step should be that the collaborative tags should respect given rights (write, delete) for every group.
Hello to all,
I agree with the summary above by @rickyelopez .
Just discovered this feature and this thread, and I think the topics discussed above can be split into two general categories:
1. Privacy/Security * Configure tag visibility for different users and groups * Configure tag modifiability for different users and groupsIn my views, the main functionality that tags are meant to perform is to give a fast and easy access to very diverse content. This fast and easy access happens because you can search by using:
- a limited number of tags (ideally: one only);
- tags belonging to different ways of looking at that diverse content (in our case: per topic, per geography, per readiness level...).
Hence, the most important feature among those neatly summarised by @rickyelopez is, in my views, that an option should be given that the modification of tags be restricted to administrators (or to a small group). If not, you end up with a myriad of slightly misspelled tags, which results in a helpless fragmentation of the category of content that you intend to create. This becomes nightmarish to administer and ultimately kills the function of tags as I described above.
Example: A taxonomy per geographic locations, with one tag per EU Member State, in a multilingual community. In the absence of this restriction to the edition of tags, you will rapidly end up having, for the concept of "Germany", and an initial official tag such as "
DE - Germany", a flurry of alternatives such asDEU - Germany,DE. Germany,Deutschland,DE - Alemania, ...
After a short while, it becomes impossible to search for content related to Germany because the list of tags to search for is (1) too large and (2) registered nowhere.@SergioArbarviro
Why should tags be owned by only admin or fixed group of users? I think there could be two types of tags. Private and public (collaborative). Public tags only live inside a group. This means tags should only exist in conjunction with their owner.Owner is a user or group:
userXY:tagXY; groupXZ:tagXW; groupXV:tagXTThe admin can add tags with empty owner and by this everyone on the server can see it (default tags).
Modification should be driven by admin of either server or group. Those that manage the server are able to edit everything, and group admins can change group tags.
As a consequence, tags with same name from different groups exist in parallel. But thats okay, if one group is deleted the tag with same name from other group will survive.
Reacted by Joda Stößer@godfuture
I agree with you that the persons defining the tags could be a broader group than the administrators, and that one could imagine that the administrator of a group manages the tags relevant for that group.My concern relates to the pollution of these public tags (= editable by a restricted set of administrators only, for the server or for each group) by private tags. In the current version of NextCloud, anybody can start typing a tag and can create his/her own private tag that is "close" to the public tag (= with one or several typo errors, truncated), but not identical, just by typing "enter" (willingly or not) when the tag starts appearing on the tag search window. This new, private, "contaminated" tag is then proposed to other users that, without knowing it, use the "contaminated" version instead of the official one... and you end up with tens of slight variations of the same chain of characters to describe the same concept... making the tagging system useless.
I understand that some use cases may want to leave complete freedom of the definition of tags by anyone. This is legitimate when the centres of interst are extremely diverse.
In more professional use cases where the universe of issues to handle is finite and there is an interest in navigating fast to the content of interest, I believe that the option should be given that the ordinary users are not given the possibility to create their own "private" tags.
@SergioArbarviro
I do not entirely agree. If users create a tag, by default it is shared with others. This is bad and needs to be prevented. I agree with you in this point.But I dont agree that users shall not be able to create their own and private tags which are not shared to others. If a user is polluting his tags with poo, then this poo is only in his user account. As drafted above, public and shared tags in a group would exist in parallel. Your own poo will not stink in other user accounts.
So again, you are free to mess up your account, but you will not be able to mess with default tags on whole server or group tags, if you do not have permission.
This way I dont understand your fear of tags going messed up. The messing up today is created because all tags are by default public.
Reacted by Joda Stößer, Daniel Scharon and SergioArbarviro@godfuture
I thank you for your clarification and agree with your opinion. Indeed, if the tags produced by a user are "private" and hence visible to that user only, then indeed s/he can do whatever s/he wants, it has no consequence on the broader community.Folks, please open a dedicated issue for the user tags (if there isn't one already)
Tags are calledCollaborative tagsfor a reason :)We do have some API for user tags already, this is how we store favorites for example.
But it wasn't pushed further than that.Regarding that issue, most of the work is done now (31)
Last part missing is #2143, which I quggest people follow that on the issue directly :)
Metadata
Metadata
Assignees
Type
Projects
- Status
cc @jancborchardt @nickvergessen