occ tool to export/import calendars and addressbooks

[schiessle]

Would be good to have a occ tool to export all calendars and addressbook into a standard format and import them again, either for the whole system or on a per user basis. Especially for large installations this helps to avoid running into timeouts, etc.

[Faldon]

For export/import calendar events of a single user, we could export a single .ics file. Drawback is, we would have to specify the calendar to import to.
For migrations of a user or whole systems, we need to export the current structure too, so we can import the events into the right calendar (or create it, if it not exists yet).

[klawdhfzasjhaa]

Would be a great feature. Can't access my Nextcloud through the browser, but OCC stills works.

[georgehrke]

Some common work with: #2864

[sphakka]

I sorely need this! Please, if it's not too late, consider the following additional requirements:

• CLI: extending the dav interface looks cumbersome. I'd prefer to see app-specific interfaces like:

occ calendar:<command> <uid> <calendar-name> <ICS-file>
occ contacts:<command> <uid> <addressbook-name> <VCF-file>

Where <command> := {export,import} (possibly with aliases, like dump,restore)

• Import (restore) should be able to merge into an existing calendar/addressbook, otherwise abort or handle transparently name collisions by renaming the old calendar.

[georgehrke]

@sphakka if you need this feature, please consider contributing a pull-request! :)
If you are interested, I'd be happy to give pointers.

[skorpions2000]

Do you have any solution for this problem?

[szaimen]

I guess it will be handled in nextcloud/user_migration#94

[Pytal]

Closed by nextcloud/user_migration#167

[MaksonHerson]

I recursively checked al linked issues. And primary issue of import calendars and addressbooks steel actual and unresolved.
@sphakka suggested an interesting way of modernisation occ calendar:
It would be too useful for processing and import huge amount of users .ics files via occ tool by server administrator (instead of manual calendar import of every personal user).

[c33s]

@Pytal can we reopen this please? mass/batch import is not solved by the linked ticket nextcloud/user_migration#167

we need a bridge to the existing gui import tool from the cli so we can automate things.

i just imported 10 calendars to new calendars only to notice that all imported calendars result in a calendar name in the url prefixed by imported- https://localhost/remote.php/dav/calendars/username/imported-personalics/

so delete all again and first create 10 empty calendars and then import the right calendar file in the right calendar. this is really a terrible UX.

[Pytal]

The linked PR imports each ics file into a new calendar by design to avoid data loss if overwritten by accident when importing to the same calendar URI

If more granular control over the way data is imported is desired please open a new issue @c33s

[c33s]

@Pytal i am not sure i understand, the linked PR is only about export and is not related to import. so i don't understand that it can close a ticket that is about import AND export

i am looking for something like:

ncc dav:create-calendar username calendarname --import my-file.ics --color=ffff00

should i open a new ticket or can we reopen this, so the subscribed persons don't have to resubscribe the issue again?

[Pytal]

Right, sorry @c33s I misremembered and thought that selective import was already possible

This would indeed be a new feature so please open a new issue for import and more granular control