queen’s events calendar information services and technology - student advisory committee queen’s...

8
Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Upload: jemimah-gilmore

Post on 18-Jan-2018

217 views

Category:

Documents


0 download

DESCRIPTION

Background – Usage Statistics In 2015: 87,217 sessions (337,286 pageviews) 57.65% sessions from the Kingston area approx. 4 pages/session average session duration ~8.5 min Compared to 2014: sessions, users and pageviews increased over 20% average session duration increased ~8%

TRANSCRIPT

Page 1: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Queen’s Events CalendarInformation Services and Technology - Student Advisory Committee

Queen’s University MarketingJanuary 4, 2016

Page 3: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Background – Usage Statistics

In 2015: • 87,217 sessions (337,286 pageviews)• 57.65% sessions from the Kingston area• approx. 4 pages/session • average session duration ~8.5 min

Compared to 2014: • sessions, users and pageviews increased over 20% • average session duration increased ~8%

Page 4: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Why it's time for a new calendar…

• Older technology does not integrate with those currently in use at Queen’s (WebPublish, social media, etc.)

• Excessive administrative overhead• over 200 calendars, or “layers” - many are no longer used• user administration through multiple applications• users cannot manage their own credentials• lacking in flexibility (locations & contacts)

• Recently relaunched Queen's website (queensu.ca), also Gazette Online, Alumni Review, MyQueen’sU + WebPublish II

• 175th anniversary celebrations in 2016

Page 5: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Features & Functionality

• Single Sign-On (SSO) - anyone at Queen’s with an active NetID should be able to post events• Calendar and events will be publically viewable - no special

restrictions or need to log in to view events • Drupal website - will allow tags and better integration with

other sites• RSS support - syndication to other websites (event lists)• Social media sharing• Responsive, meets AODA standards for accessibility• Import/export capabilities (under investigation)

Page 6: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Some Challenges…

• Potential for abuse• SSO would allow anyone to post anything• Need to define “university sanctioned” events • “Community policing” - members can report events • Event contact will default to the person who submits it

• Possibility of having too many events?• Limit number of categories (tags) - very general• Need to communicate the types of events that qualify

Page 7: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Event Tags

Event Type• 175th anniversary• Alumni event• Arts, culture and entertainment• Athletics• Ceremony, celebration• Club event• Conference• Health and wellness• International• Lecture, seminar, academic presentation• Research• Town hall, fair, showcase• Workshop, training, professional

development

Faculty/School• Faculty of Arts and Science• Faculty of Education• Faculty of Engineering and Applied Science• Faculty of Health Sciences• Faculty of Law• School of Business• School of Graduate Studies

Other• Support services and resources

Special• Faith Dates• University closures (and statutory holidays)

Page 8: Queen’s Events Calendar Information Services and Technology - Student Advisory Committee Queen’s University Marketing January 4, 2016

Next Steps…

• Input on requirements and development

• User testing as development continues (beta site)

• Communications and promotions for launch

• And continued feedback in the future…