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 |
||
| 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 | |||
They can be duplicated using the Copy from Existing Itinerary feature. | |||
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. | ||