Itineraries: Difference between revisions
Created page with "An Itinerary is a collection of Activities, spanning a time period in a location. EventR uses itineraries to group users to tasks, and they are core to the Event Model." |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
An Itinerary is a collection of Activities, spanning a time period in a location. | An Itinerary is a collection of Activities, spanning a time period in a location. | ||
This is the basic unit of organisation in day to day operations in EventR. | |||
Itineraries are made up of the following: | |||
* Members - people doing the collaborative task | |||
* Activities | |||
* Flights and Transport | |||
* Accommodation | |||
They have many properties: | |||
* A date time range - this is used as a guide for all date times in the event | |||
* The Itinerary location - this is used to anchor the itinerary for activity searches. Note an itinerary does not need to have a specific location, but it generally helps the system if one can be provided, as all timezones and locations will default to around these details | |||
* A timezone - this is used as the default. If an itinerary is copied to a new timezone, everything in it will inherit the new timezone default as a base. | |||
* An Additional information field, used for extra information for everyone. This can be [[Markdown and Hyperlink Support|markdown]] so can be quite rich in content. | |||
They can be duplicated using the Copy from Existing Itinerary feature. | |||
They can be [[Excel Itinerary import/export|imported]] from an <code>.xlsx</code> workbook or a <code>.zip</code> archive to create a new itinerary. | |||
They can also be tagged into groups for organisation. | |||
EventR uses itineraries to group users to tasks, and they are core to the Event Model. | EventR uses itineraries to group users to tasks, and they are core to the Event Model. | ||
In the EventR Team App they can be hidden on a personal basis using the Bin icon. | |||
[[Category:Core]] | |||
Latest revision as of 12:50, 25 September 2026
An Itinerary is a collection of Activities, spanning a time period in a location.
This is the basic unit of organisation in day to day operations in EventR.
Itineraries are made up of the following:
- Members - people doing the collaborative task
- Activities
- Flights and Transport
- Accommodation
They have many properties:
- A date time range - this is used as a guide for all date times in the event
- The Itinerary location - this is used to anchor the itinerary for activity searches. Note an itinerary does not need to have a specific location, but it generally helps the system if one can be provided, as all timezones and locations will default to around these details
- A timezone - this is used as the default. If an itinerary is copied to a new timezone, everything in it will inherit the new timezone default as a base.
- An Additional information field, used for extra information for everyone. This can be markdown so can be quite rich in content.
They can be duplicated using the Copy from Existing Itinerary feature.
They can be imported from an .xlsx workbook or a .zip archive to create a new itinerary.
They can also be tagged into groups for organisation.
EventR uses itineraries to group users to tasks, and they are core to the Event Model.
In the EventR Team App they can be hidden on a personal basis using the Bin icon.