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 own categories, delete default ones #1644

Open
Hundhausen opened this issue Nov 9, 2019 · 20 comments
Open

Add own categories, delete default ones #1644

Hundhausen opened this issue Nov 9, 2019 · 20 comments
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request Feature: Categories

Comments

@Hundhausen
Copy link

Hundhausen commented Nov 9, 2019

Describe the solution you'd like
It would be nice if you could add own categories and delete default ones.

Additional context
With v2.0.0-beta2 and Issue #107 categories got added and so far it works. Categories from Thunderbird get shown in the web calendar and vice versa but it would be nice to delete unwanted default categories and add own categories for direct selection for the web calendar. I've looked into the files if there is an easy way to change this but as it looks, it isn't.


Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

@Hundhausen Hundhausen added 0. to triage Pending approval or rejection enhancement-proposed labels Nov 9, 2019
@Malspherus
Copy link

You can add own categories in 2.0.1 (and probably also in some earlier versions). Deleting the defaults seems to not be possible at the moment, self-created categories don't show up in the list. Also see #71

@Hundhausen
Copy link
Author

You miss understood me or I wasn't specific enough. Adding a own Category to one event works but also assigning this category to an other event needs to be done manually (I talk about the Web Interface). When multiply users have access to this Calendar, this would be an issue.

My idea is that an admin can add own categories that should be used as default and others not. When everyone needs to retype a category, small differences can occur and would mess things up.
You can color code every category to show how important something is. For example blue for a in house event, purple for external events, green for holidays, red for very important event and so on. It would be a mess if someone would messes up one category by slipping on the keyboard and adding a character and so messing up the color and people not noticing it.

For a single user, this won't be an issue, because in Thunderbird I can add my own categories and just using them but this isn't possible for the web client.

@Malspherus
Copy link

So in addition to what is available now:

  • Shareable list of categories for every calendar, prefilled with current defaults
  • Ability to add, remove and edit all categories in this list (which would probably mean updates to all events using them the way they are implemented at the moment)
  • Some kind of permission system. In your case not everyone who can add events should be able to add new categories but they should still be able to use existing ones
  • Sync of the whole list of categories to Thunderbird and other clients. I don't think that's possible right now, especially considering permissions

I could also imagine the Flow-App to integrate with this somehow, also kind of related to #1540 (Comment) for viewing categories easily I guess

@Hundhausen
Copy link
Author

Sync/Download with other clients would be a nice to have but not really mandatory. I don't know if the Clients or the Protocol would support this. Also it's not so hard to add the Categories once in the clients.

Using the Permission System would be nice too but I don't know how hard it would be. I mean a calendar isn't something that strangers would have access to and I would expect that people would intentionally mess things up.

The core feature would be No. 1 and No. 2 just inside a Nextcloud for all Users.

A more complicated calendar for big company use would require a more in depth permission system and more automation. I think this would be too much to ask for.

@MysticJay
Copy link

MysticJay commented Mar 23, 2020

I very much appreciate that calendar categories are now visible from the webinterface as well. But please refrain from syncing categories across clients. Esp when you share a calendar with others you do not want to see all their categories in your dropdown list nor would you like to use their colors.
In fact I share a calendar with colleagues and if an entry is assigned to a specific person we add that person's category. In the client (Thunderbird) I have only changed MY category to red the others are the same default color.
I have even removed all the default categories from TB as they can not be localized and you soon have "Privat", "private", "privé", as three categories instead of one.

But I recommend to
add all used categories to the list when a calendar gets imported
add new categories when used
but not re-add them when the user deleted a category manually.

M.

@Gerhard386
Copy link

Hi,
we are a group of twenty people, who would like to use the nextcloud to organize our internal and external work. We are part of a larger organization, which provides the nextcloud for a lot of people with different interest/work.
But: We will have a restricted group and we need a calendar with our internal/external events.
Tor this the standard categories like "travelling" are not really useful. The typing and assigning of colours to them, will differenate even with probably 5 persons maintaining the calendar.
Therefore we would like to :

  • add fixed categories
  • add may later on more categories, when the need arise
  • remove the default
  • the group members should still have the possiblilty to "add" a new category, if it is more suitable for the purpose.
    As a closed group, we do not care about the outerspace - neither other groups nor exchange with calendars in other systems/tools.
    We would need no translation, just the text we enter at our defaults.
    For the permission - I guess something like the "groupowner" - would be fine.
    May be a first step would be an extension only for restricted/closed groups.
    kind regards
    Gerhard

@amette
Copy link

amette commented May 26, 2020

Not sure, if I understand @MysticJay correctly, but imho syncing categories across clients is absolutely necessary. I definitely want to have the same categories that I have in the web interface on my phone as well as in my desktop application.

Importing a shared calendar is probably a different thing. It would make sense to allow for 'do not import categories' or something similar.

@georgehrke
Copy link
Member

, but imho syncing categories across clients is absolutely necessary.

Well, please start an initiative for an RFC, but right now there is no standard for it.

@Treora
Copy link

Treora commented Nov 24, 2020

Here another user that would really appreciate creating a custom list of categories. As a workaround, I guess I could just change the default list in the source code of the instance? (I found a list in src/defaults/defaultCategories.js)


And regarding syncing the list of categories:

, but imho syncing categories across clients is absolutely necessary.

Well, please start an initiative for an RFC, but right now there is no standard for it.

Possibly of interest is RFC 7986 “New Properties for iCalendar”, which extends (see section 5.6) the CATEGORIES property to also be usable on the whole iCalendar object:

This specification modifies the definition of the "CATEGORIES"
property to allow it to be defined in an iCalendar object. The
following additions are made to the definition of this property,
originally specified in Section 3.8.1.2 of [RFC5545].

Purpose: This property defines the categories for an entire
calendar.

I have no idea if/which other software supports this, but it sounds like it may be suitable for this purpose. However one could also interpret the purpose as ‘listing the categories this calendar belongs to’, rather than ‘listing the categories its events can have’; I honestly do not know which meaning is intended.

@mklemme1
Copy link

mklemme1 commented Apr 6, 2021

We have an events calendar of our club.
It is edited by multiple persons.
We want to use categories to publish meetings to different parts of our website.
Therefore configurable categories would be a real benefit.

Proposing again categories that were used before would already help.

@mklemme1
Copy link

I have a similar request #3735.

@WNYmathGuy
Copy link

I'm a bit surprised this is open. I thought the Add a category to Calendar entries was implemented. Today I tried adding "Deadline" to one of my two NC instances and it did not work. Tried it via Ubuntu and Windows 11.

@Gaming4LifeDE
Copy link

Will this ever happen?

Nextcloud calendar in it's current state is completely unusable for a lot of people because the categories are a mess. Also I think the month view should show the color of the category but i guess that's a topic for a separate ticket.

@Kayoku
Copy link

Kayoku commented Nov 29, 2022

Hi,

This feature is really really needed for use Nextcloud Calendar for a lot of people... Any news ?

@vncntwbr
Copy link

vncntwbr commented Dec 5, 2022

Would really love an update on this! Waiting 3 years for a simple modification to a dropdown menu does not seem appropriate...

@ChristophWurst
Copy link
Member

@diabolicvincent-git you're probably right. Wanna give this a go? I can provide you with some pointers.

@Kayoku
Copy link

Kayoku commented Jan 16, 2023

If you can provide some advice to help anyone who can add this on the plugin, it'll be really helpfull I think. In fact I would love to do it but I'm not really confortable with the language used here :D

rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
…egories.

This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
…egories.

This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 25, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
@ChristophWurst ChristophWurst added 1. to develop Accepted and waiting to be taken care of enhancement New feature request labels Jun 1, 2023
@fuco809
Copy link

fuco809 commented Jun 5, 2023

are there configuration parameters for options like
*) disallow adding own categories (read only mode, use just existing/predefined ones)
*) disable default categories

rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jun 16, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>

WIP
@ChristophWurst ChristophWurst added 3. to review Waiting for reviews and removed 1. to develop Accepted and waiting to be taken care of labels Jun 28, 2023
ChristophWurst pushed a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jun 28, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Co-authored-by: Anna <anna@nextcloud.com>
Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jul 11, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>

WIP
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 3, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>

WIP
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 8, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>

WIP
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Sep 10, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>

WIP
@ChristophWurst ChristophWurst added 1. to develop Accepted and waiting to be taken care of and removed 3. to review Waiting for reviews labels Sep 28, 2023
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Nov 24, 2023
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jan 6, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Feb 23, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
@uchiit
Copy link

uchiit commented Feb 26, 2024

Hi team!

Category visualization with colored tag in the year/month/week/day event view is a crucial feature, for example, to see past and future changes/features of events (remote or local event, event is completely closed or there is some documents left, etc.).

Will it be added in future releases?

@petrarca-arezzo
Copy link

One more voice here - being able to manage categories is crucial and a must (in my view) to be implemented (hopefully sooner than later)...

rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 8, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 8, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 28, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue May 1, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.

Signed-off-by: Claus-Justus Heine <himself@claus-justus-heine.de>
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue May 15, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue May 21, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
@joshtrichards joshtrichards changed the title [Feature Request] Add own categories, delete default ones Add own categories, delete default ones Aug 7, 2024
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 17, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 26, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 28, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 29, 2024
This commit add all available "collaborative tags" and all already used
categories into option groups of the tags-menu of the side-bar editor.

Determining the set of already used categories is a little bit ugly: it
used the oc_calendarobject_props table which might be considered
"internal". However, this is the Nextcloud calendar app which only talks
to the Nextcloud calendar server. So using this "internal ingredient"
might be acceptable.

This commit addresses and is a related to a couple of open issues:

nextcloud#3735 Calendar Categories: Propose Categories already used

- this should be fixed by this commit

nextcloud#1644 Add own categories, delete default ones

- this is partly fixed in the sense that collaboritive tags are now also
  proposed as calendar categories.
- still default categories cannot be deleted
- however, using option groups one at least has some sort of overview
  about the origin of the proposed category

nextcloud/server#29950 Save VEVENT CATEGORIES as vcategory

- this issue is totally "ignored" by this commit as the proposed
  solution there is not needed (the categories are already there in the
  oc_calendarobject_props table)
- that would have to be discussed there: but my impression that the
  tables and classed mentioned there are obsolete and no longer used.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request Feature: Categories
Projects
None yet
Development

No branches or pull requests