View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0002966 | SOGo | Backend Calendar | public | 2014-10-23 14:14 | 2014-11-21 16:17 |
Reporter | Gunnar Weissmann | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | new | Resolution | open | ||
Platform | [Server] Linux | OS | Debian | OS Version | 7 (Wheezy) |
Product Version | 2.2.9a | ||||
Summary | 0002966: Import Problem with delegated calendars | ||||
Description | We encountered a problem when importing *.ics files. We imported the file to an delegated calendar. On events that are normally created with SOGo we have the following informations: ORGANIZER;PARTSTAT=ACCEPTED;ROLE=CHAIR;SENT-BY="mailto:mailto:delegate@mail.com";RSVP=TRUE;CN=calender:mailto:calender@doccheck.com We suggest, that SOGo always create the "SENT-BY" informations to specify the person who for example import the event for delegated calendars. Thank's for your support. Gunnar Weissmann | ||||
Tags | No tags attached. | ||||
I am not sure this is always a good idea. That's not what a user expects. |
|
Christian is right. Might be better to use a X-SOGo... tag. |
|
I have to correct me; this is not only a import problem. It is also possible to write a client with the behavior, that i am able to modify delegated calendars. In a multi user environment you need a evidence who modified a delegated calendar. I think in a multi user environment it is also not useful, that a user re-import events from the client side, because when he is not the organizer the event is duplicated on the server under some circumstances; backup/restore should only be made on server side. Is it possible to set a configuration option on server side to enable this behavior? @Christian: could you please explain the X-SOGo proposal? Thank you. Gunnar Weissmann |
|
In the calDAV standard there are defined attributes like "ORGANIZER", "DTSTART" etc. So Ludovic is suggesting to add an additional attribute for this "event last changed by" information starting with X-SOGo-. With that normal behaviour of the "SENT-BY" is guaranteed to still exist. |
|
Thank you very much for your explanation Christian and sorry for the late reply. So how can we support you to implement the X-SOGo tag into the server? Thank you. Gunnar Weissmann |
|
The header is not relevant for us. It doesn't have to be the sent-by tag. We would suggest, that the SOGo Server writes the identity who has modified the event in the new created "tag-field". It is important that it's guaranteed, that this is always the same. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2014-10-23 14:14 | Gunnar Weissmann | New Issue | |
2014-10-27 09:30 | Christian Mack | Note Added: 0007626 | |
2014-10-29 20:14 | ludovic | Note Added: 0007636 | |
2014-10-29 20:14 | ludovic | Severity | minor => feature |
2014-10-30 11:46 | Gunnar Weissmann | Note Added: 0007638 | |
2014-10-30 13:00 | Christian Mack | Note Added: 0007640 | |
2014-10-30 13:01 | Christian Mack | Note Edited: 0007640 | |
2014-11-19 11:56 | Gunnar Weissmann | Note Added: 0007704 | |
2014-11-21 16:17 | Gunnar Weissmann | Note Added: 0007719 |