Overview
Background
The event content type is used extensively in EdWeb. However using the event content type without some sort of dynamic mechanism to display events creates a large manual overhead. Events also need to be archived manually which is time consuming and can result in out of date information being displayed on the website.
Events often need to be entered in to more than one system e.g. entered into EdWeb to advertise the event and then the same information being added to the event booking system to allow people to book on to the event. This duplication is obviously time consuming.
There are 2 main areas that could be enhanced that would have a big impact on event management:
- A way of dynamically displaying events
- Being able to consume and display a feed of events from other systems.
Scope
The scope of this project is to implement the Request for Change (c1709-149_event_enhancements_-_design_evaluation.docx) approved by the EdWeb CAB. The project will comprise of 2 development iterations between October- November 2017. The user stories will be prepared by UWP and CAHSS and estimated.
The deliverables are prioritised using the MoSCoW prioritisation method:
M=Must Have; S=Should Have; C=Could Have; W=Want
- (M= has to be satisfied for the final solution to be acceptable in terms of delivery dates, compliance, viability etc.
- S= high-priority requirement that should be included if possible -workarounds may be available
- C= a nice-to-have requirement
- W= want but will not be part of this project)
Objectives, Deliverables, Success Criteria and Priority
| Nr. | Objective/Deliverable | Success Criteria | Priority |
| O1 | The objective is to meet the business expectation that we should be able to promote events to support all potential audiences. University events will be promoted better and reach more channels used by our target audiences. | This functionality will improve our content leading to a more current, accurate and relevant website. | |
| D1 | Automatically display a group of events based on defined criteria. | New content type is available to group events. | Must have |
| D2 | Be able to display groups of merged events that have been entered in EdWeb or from a feed from external systems. (University Event Booking system and the Talks seminar system as well other external products). | External events can be consumed in EdWeb, showing a defined list of fields. | Must have |
| D3 | Events to be grouped by methods such as child pages of a particular page but also by other tagging methods (such as Groups Audience, University hierarchy, (keyword tagging-should have)) to allow other events to be displayed. | Events can be selected from one or more groups audience. | Must have |
| D4 | Events to be displayed in either a calendar view or in a list/summary format. These would have links through to the full event detail or to the external system. | Events that have been added to EdWeb can be dynamically displayed a calendar view or list view. | Must have |
| D5 | Call to actions would lead to the standalone event pages or to specific actions, e.g. "Book Now", "More information". These could also be to external systems (could have). | CTA functionality can be added when creating events. | Must have |
| D6 | Events can be presented as single events or as part of a larger programme | Events can be flagged as stand alone or as part of a larger group of events. | Must have |
| D7 | Only active or live events need be displayed unless part of a larger programme. | Flexibility to display events in according to their status and programme affiliation/membership. | Must have |
| D8 | A facility to view previous events. | Archived EdWeb events are available for browsing and sharing through a calendar or list view. | Should have |
Benefits
- The enhancements would reduce effort and avoid duplication. For example events would be displayed dynamically rather than manually creating lists of events and old events would be archived automatically.
- Easier for event organisers to be able to draw attention to upcoming events for promotion purposes.
- Current staff/students/visitors able to see what's coming up soon within their area of interest.
- All site users be able to see an archive of past events.
- Prospective staff/students able to use events as a way of assessing how active Edinburgh is within their field of interest.
Project Milestones
Target Date |
Title | Stage |
|---|---|---|
| 09-Oct-2017 | Planning Review | Plan |
| 27-Oct-2017 | End of Foundation Iteration | Execute |
| 16-Nov-2017 | End of Iteration 1 | Plan |
| 21-Dec-2017 | End of Iteration 2 | Execute |
| 25-Jan-2018 | End of Iteration 3 | Execute |
| 08-Feb-2018 | Deployment to LIVE | Deliver |
| 22-Feb-2018 | Deployment Review | Deliver |
| 08-Mar-2018 | Closure Review | Close |