mirror of
https://github.com/werkraum-media/events.git
synced 2024-09-20 06:16:10 +02:00
Daniel Siepmann
7b3bbf6d9d
The usual use cases right now would involve a new file with a new URL. That way we don't need to download existing files again. That reduced network traffic, execution time and resource usage.
28 lines
910 B
ReStructuredText
28 lines
910 B
ReStructuredText
.. index:: single: import; DestinationOne
|
|
single: DestinationOne
|
|
.. _importDestinationOne:
|
|
|
|
Import Destination One
|
|
======================
|
|
|
|
The extension provides out of the box to import events from Destination Data One.
|
|
|
|
The import can fetch events, dates, categories and images.
|
|
Multiple imports can be defined, e.g. one per experience.
|
|
Imports are configured as database entries "Import Configuration".
|
|
|
|
The import can be triggered via scheduler tasks as well as commands.
|
|
A single import as well as all imports at once can be triggered.
|
|
|
|
The import will:
|
|
|
|
* Add and update events
|
|
|
|
* Flush all dates for updated events and re-create all dates.
|
|
|
|
* Add and update all images for updated and added events.
|
|
Existing image files won't be downloaded again, only information and position are updated.
|
|
|
|
The import will not:
|
|
|
|
* Remove outdated data. Use cleanup command :ref:`eventsRemovePast` instead.
|