{"action":"opened","issue":{"url":"https://api.github.com/repos/nextcloud/calendar/issues/589","repository_url":"https://api.github.com/repos/nextcloud/calendar","labels_url":"https://api.github.com/repos/nextcloud/calendar/issues/589/labels{/name}","comments_url":"https://api.github.com/repos/nextcloud/calendar/issues/589/comments","events_url":"https://api.github.com/repos/nextcloud/calendar/issues/589/events","html_url":"https://github.com/nextcloud/calendar/issues/589","id":255521279,"number":589,"title":"Fetaure: Import only events whose UID does not already exist","user":{"login":"brunt82","id":26540488,"avatar_url":"https://avatars3.githubusercontent.com/u/26540488?v=4","gravatar_id":"","url":"https://api.github.com/users/brunt82","html_url":"https://github.com/brunt82","followers_url":"https://api.github.com/users/brunt82/followers","following_url":"https://api.github.com/users/brunt82/following{/other_user}","gists_url":"https://api.github.com/users/brunt82/gists{/gist_id}","starred_url":"https://api.github.com/users/brunt82/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/brunt82/subscriptions","organizations_url":"https://api.github.com/users/brunt82/orgs","repos_url":"https://api.github.com/users/brunt82/repos","events_url":"https://api.github.com/users/brunt82/events{/privacy}","received_events_url":"https://api.github.com/users/brunt82/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-09-06T08:28:18Z","updated_at":"2017-09-06T08:28:18Z","closed_at":null,"author_association":"NONE","body":"### Steps to reproduce\r\n1. Import ics.\r\n2. Import same ics again.\r\n\r\n### Expected behaviour\r\nIt will be only imported events, whose UID does not already exist in calender for the user.\r\n\r\n### Actual behaviour\r\nEvery event is imported regardless if it already exist or not. Therefore it exists events with the same UID in the same calender, which is not allowed by CalDAV specification: https://tools.ietf.org/html/rfc4791.\r\n\r\nI already found #53, which was closed earlier this year. However I confirm that it makes no sense to import already existing events. Therefore I would not ask the user about replacing / adding the event. Instead, the item to be imported should be ignored if another one already exists with the same UID in the calendar.\r\n\r\nIndependent of the CalDAV specification, here is an use case:\r\n\r\nUser deletes an event and needs to restore a backup. The backup does not contain all events of the current calendar but the event, which was deleted by accident. Therefore I cannot delete the whole calendar (because I would delete events, which are not in the backup), but I also cannot import the ics because of the duplicated events."}}
{"actor":{"display_login":"brunt82"}}