Skip to content

Export an icalendar file from a listing search #235

@stevepiercy

Description

@stevepiercy

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

After resolving #226, we now have the ability to download a single event's icalendar file.

The next step would be to export a single icalendar file of a collection of events. Examples of collections include:

  • Future events only
  • Future sprint events
  • Future Volto Team events EDIT: open to Volto Team members only due to disruptive GSoC aspirants crashing the event and asking for technical support. This collection is not needed.
  • Future events with a virtual or remote participation component

Such a collection would have its own unique URL to download the icalendar file. This would allow visitors to import a complete icalendar file into their personal calendar applications.

Describe the solution you'd like

@acsr put together a proof of concept that does that.

The steps included the following.

  • Go to Classic UI and enable Collections as implicitly addable in ZMI portal types.
  • Make sure you can add a Collection and configure it to collect what you need.
  • Append /ics_view to the regular, non-Classic UI URL, and you get an iCalendar file with all events.
  • If you ask yourself why reccuring events are not explicitly listed as separate events, read this: Don't include occurrences in ical exports of containers and event_listing plone.app.event#103
  • Fun Fact: You can still use the configurable Table view to export the list as CSV.

Describe alternatives you've considered

Another option would be to allow users to first search for events, then export the search results into a single or individual icalendar files, but I don't think there's much demand for this use case.

Additional context

This idea came about from the relaunch of Open Tech Calendar, a demo of Open Web Calendar, and @stevepiercy's ongoing documentation project on icalendar.

Further discussion took place in Discord in the ploneorg-marketing Discord channel discussion.

This issue description may be revised, depending on further comments, including the steps that Armin took to make the demo successful.

Metadata

Metadata

Assignees

Labels

Projects

Status

Ready

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions