Bug 334654

Summary:	Similarly named Google Calendars cannot be distinguished
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Cristian Klein <cristiklein>
Component:	Google Resource	Assignee:	Daniel Vrátil <dvratil>
Status:	CONFIRMED ---
Severity:	wishlist	CC:	kdepim-bugs, smartins
Priority:	NOR
Version:	4.13
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Cristian Klein 2014-05-12 11:57:24 UTC

In Google Calendar I have two calendars named Personal and Work. A friend of mine, who shares her calendars with me, has other two calendars named Personal and Work. When adding a Google Calendar to Kontact, I am shown two "Personal" calendars and two "Work" calendars, which I am unable to distinguish.

Reproducible: Always

Steps to Reproduce:
1. On GMail, create a calendar called "Personal".
2. Ask a friend to create a calendar called "Personal" that s/he can share with you.
3. Add your Google Calendar to Kontact
Actual Results:  
Kontact presents two "Personal" calendars, that cannot be distinguished.

Expected Results:  
Kontact should present two easily distinguishable calendars:
- "Personal"
- "Personal (of <friend's name>)" or "<friend's name> (Personal)"

Comment 1 Daniel Vrátil 2014-06-02 09:59:20 UTC

Unfortunately Google does not expose information about calendar owner. The only information we get is  accessRole, which is either "owner", "reader" or "writer", so we can only tell whether the calendar is ours or someone else's.

I'll move this bug to a wish, so that we can implement this once (if ever) Google will expose this information via their API, or when we find some workaround how to get this information.

In the meanwhile, we could add "(Shared)" to each calendar that we don't have "owner" role for, if that would help you at least a little.

Comment 2 Cristian Klein 2014-06-02 12:32:37 UTC

How about using the "summaryOverride" field if it exists? This way, the user can at least edit the names of the calendars from the web to make sure they do not overlap.

Comment 3 Justin Zobel 2021-03-09 05:47:01 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.