The SP Event Manager uses a number of SharePoint lists to store its data. All of these lists are hosted directly in the App Web, so the app does not alter any content in the host web.
Event Programmes List (Lists/EventProgrammes)
This list stores all primary information for events and sub-events. Any changes made to events in the UI will automatically update this list. From a content type perspective, this list consists of only free-text and people fields. All additional complexity is handled via the UI.
Event Stakeholders (Lists/EventStakeholders)
Stakeholder information in the SP Event Manager follows a tag-style architecture. Users can select a pre-existing tag as they type, or they can choose to add a new tag. These stakeholder tags are stored as individual entries in the Event Stakeholders list.
Event Attendees (Lists/EventAttendees)
This list stores attendees for events. When attendees are added to an event, they are added to this list. Once in this list, they will be available to select via the type and select box in the event form. If deleted from an event, the attendees are deleted from this list.
Event Types (Lists/EventTypes)
Each event is assigned a type, and these types are stored in the Event Types list. Unlike the prior 2 lists, this list needs some manual intervention, as users will need to input their desired event types into the list before they will show up in the UI. This list also has an ImageURL field, which allows users to assign an image to an event type, which will show up in the event index and in search results. If no image is found, a default image is shown. Images are capped at 293x195px, so for consistency's sake I recommend this ratio is maintained for all images.
The Settings list stores global app settings, dictating how the app functions behind the scenes. At present, there are only 2 settings that can be configured via this list:
- FromEmail - set this to a valid email address from your organisation. This will be the From address for any correspondence the event manager sends.
RefreshInterval - By default, all events are fetched on initial load and cached for use in the system. This however is not useful for extended periods as other users may have added content. To counter this, the system will re-fetch events from SP according to this refresh interval, in minutes.