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.

Sign up for GitHub

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

Jump to bottom

Propose Categories already used #3735

Open
mklemme1 opened this issue Nov 28, 2021 · 2 comments
Open

Propose Categories already used #3735

mklemme1 opened this issue Nov 28, 2021 · 2 comments
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request Feature: Categories

Comments

@mklemme1
Copy link

Is your feature request related to a problem? Please describe.

The current calendar supports categories.
The list of categories is hard-coded and cannot be modified (see #1644) . That's not helpful for many use cases.
We, for instance, have a calendar of events that many people maintain.
We use categories to distinguish different types of events, like internal and external events.

Describe the solution you'd like
In the categories selection list, list all the categories that were used in entries of the last two years and the future.

Describe alternatives you've considered
Configuring a list (see #1644) would also work.
This solution is probably easier to implement (no extra GUI)
@mklemme1 mklemme1 added 0. to triage Pending approval or rejection enhancement-proposed labels Nov 28, 2021
@mklemme1 mklemme1 mentioned this issue Nov 28, 2021
Open
@tcitworld
Copy link
Member

Requires : nextcloud/server#29950

Right now we can only suggest categories from the events currently loaded in the calendar, we don't have information for all categories.

@rotdrop
Copy link
Contributor

rotdrop commented Apr 22, 2023

Requires : nextcloud/server#29950

Right now we can only suggest categories from the events currently loaded in the calendar, we don't have information for all categories.

But the table oc_calendarobjects_props also already stores categories, so vcategory_to_object would be redundant ... and somehow appears to be completely unused.

rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
@rotdrop
Augment the category menu by all system tags and all already used cat…
8b37bad 
…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
@rotdrop
Augment the category menu by all system tags and all already used cat…
b6317be 
…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
@rotdrop
Augment the category menu by system tags and already used categories.
568a312 
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 rotdrop mentioned this issue Apr 24, 2023
Merged
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Apr 24, 2023
@rotdrop
Augment the category menu by system tags and already used categories.
648684b 
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
@rotdrop
Augment the category menu by system tags and already used categories.
25cdc17 
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
@rotdrop
Augment the category menu by system tags and already used categories.
347a744 
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
@rotdrop
Augment the category menu by system tags and already used categories.
20b6911 
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
@rotdrop
Augment the category menu by system tags and already used categories.
fc89c82 
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
@rotdrop
Augment the category menu by system tags and already used categories.
bc3e211 
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
@rotdrop
Augment the category menu by system tags and already used categories.
940c17a 
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
@rotdrop
Augment the category menu by system tags and already used categories.
7ae8560 
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
@rotdrop
Augment the category menu by system tags and already used categories.
93f13e5 
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
@rotdrop
Augment the category menu by system tags and already used categories.
f0b435d 
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
@rotdrop
Augment the category menu by system tags and already used categories.
d443623 
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 Apr 27, 2023
@rotdrop @miaulalala
Augment the category menu by system tags and already used categories.
f4ec5c6 
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.

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 May 10, 2023
@rotdrop @miaulalala
Augment the category menu by system tags and already used categories.
50e44f3 
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 May 14, 2023
@rotdrop @miaulalala
Augment the category menu by system tags and already used categories.
82fad05 
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>
@ChristophWurst ChristophWurst added 3. to review Waiting for reviews and removed 0. to triage Pending approval or rejection labels May 22, 2023
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jun 16, 2023
@rotdrop
Augment the category menu by system tags and already used categories.
557b07d 
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 pushed a commit to rotdrop/nextcloud-app-calendar that referenced this issue Jun 28, 2023
@rotdrop @miaulalala @ChristophWurst
Augment the category menu by system tags and already used categories.
b3af4c3 
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
@rotdrop
Augment the category menu by system tags and already used categories.
2b55918 
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
@rotdrop
Augment the category menu by system tags and already used categories.
4cd54ed 
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
@rotdrop
Augment the category menu by system tags and already used categories.
2ecf380 
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
@rotdrop
Augment the category menu by system tags and already used categories.
d38b120 
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
@rotdrop
Augment the category menu by system tags and already used categories.
a6d616f 
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
@rotdrop
Augment the category menu by system tags and already used categories.
9f0cde0 
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
@rotdrop
Augment the category menu by system tags and already used categories.
d79489d 
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
@rotdrop
Augment the category menu by system tags and already used categories.
0bf0812 
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
@rotdrop
Augment the category menu by system tags and already used categories.
054f0a5 
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
@rotdrop
Augment the category menu by system tags and already used categories.
9026ff4 
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
@rotdrop
Augment the category menu by system tags and already used categories.
542d521 
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
@rotdrop
Augment the category menu by system tags and already used categories.
2163cb8 
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
@rotdrop
Augment the category menu by system tags and already used categories.
3c0a922 
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 Calendar Categories: Propose Categories already used Propose Categories already used Aug 7, 2024
rotdrop added a commit to rotdrop/nextcloud-app-calendar that referenced this issue Aug 17, 2024
@rotdrop
Augment the category menu by system tags and already used categories.
748f4e2 
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
@rotdrop
Augment the category menu by system tags and already used categories.
12e4adb 
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
@rotdrop
Augment the category menu by system tags and already used categories.
feac11c 
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
@rotdrop
Augment the category menu by system tags and already used categories.
3cd9f40 
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
Assignees
No one assigned
Labels
1. to develop Accepted and waiting to be taken care of enhancement New feature request Feature: Categories
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@ChristophWurst @rotdrop @joshtrichards @tcitworld @mklemme1