Ryerson Faculty Conference Keynote: Can Statistics Help Us Understand Student Engagement?

Presenter

  • Christopher Evans

National Survey of Student Engagement

While statistics don’t tell the whole story, it shows student perceptions, which are important because those are passed onto other current students and prospective students.

  • 1st + 4th year students, 4200+ at this university
  • from 146 countries

Commute

  • live with parents 69%
  • commute to campus 95%
  • >10 hrs/week commuting 38%

Student Employment

  • on campus 13.6%
  • off 54.7%
  • work 68.3%
  • work >10 hrs/week 45.3%

Campus Life

  • participate co-curricular 40%
  • attend campus events < 50%
  • < 10 hr/week (outside of class) 68%

Academic Life

  • significant time studying 79%
  • prepare >10hr/week for class 61%
  • unprepared for class 35%

Satisfaction with Education

  • good/excellent 79%
  • would attend again 81%
  • faculty available/helpful/sympathetic 66%
  • faculty make students aware of research activities by applying their research to teaching 62%

This last point is valuable experience for students and gives a little window to faculty life, which allows students to get to know faculty a little better.

Sense of Community

  • in class 56% – faculty crucial to student’s feeling at home at Ryerson
  • academic program 46%
  • study groups 29%
  • none 12% – realistically, no matter what, some students won’t feel at home, will never be zero

Contributions to Engagement

  • presentation 39%
  • project that integrated ideas from different sources 86%
  • worked with other student during class 46%
  • worked with classmates outside of class 70%
  • discussed ideas with faculty outside class 56%
  • received prompt written/oral feedback 50%

All instructors feel that they give prompt feedback, but perception might be skewed somewhat. For example, an instructor might return a quiz the next class, but when midterms are returned a week later, students may think faculty are being lazy. Faculty activities become important for student perception of engagement as well.

  • participated in community based project 34%
  • practicum/intership/co-op/etc 30%
  • worked with faculty members on activities other than coursework 38%
  • capstone/thesis/senior project (4th only) 23%
  • worked on research project with faculty member outside of program requirements 8% – skewed to lower side, because includes 1st and 4th year students

Obstacles

  • work/financial 83%
  • family
  • health/disability

What would Improve Learning Experience

These were very generic answers.

  • quality of instruction 34%
  • increase contact 21%
  • improve quality of academic support 24%
  • more opportunities to undertake research with faculty 25%
  • reduce class size 13% – large classes aren’t a big deal, but the subject matter and how it is presented

Teaching Chairs Report – Faculty Concerns

  • most common presentation forms: lecture, seminar/method course, lab/studio
  • motivating students 89%
  • evaluating students’ learning 65%
  • understanding learning differences 53%
  • understanding how students develop intellectually 59%
Faculty Express Concern About
  • students attitudes and behaviour – class attendance, participation
  • administrative and logistical challenges – scheduling, large class sizes

Faculty feel large class sizes are a problem, but students don’t.

What does the data tell us about engagement?

NSSE data gives us hints about academic and social interaction

  • academic integration: perception of faculty interest, academic resources, academic preparation
  • social integration: student’s perception of his/her ties to the post-secondary institution, which include extend to which student is involved in institution-related activities, perception of faculty and staff attitude, institutional sensitivity, institution events

Some faculty portray a kind of remote veneer that keeps them at arm’s length, which makes them unapproachable.

The data tells the what, but not the how or why, and only about student perception.

Levels of Engagement

While the NSSE focus on two types of levels of engagement, the data doesn’t give us much insight into any of the others.

  • mentoring – highlevel, multi-variant interaction (NSSE focus)
  • personal
  • functional interaction – contact for particular, institutional purposes (NSSE focus)
  • incidental
  • disengagement

Benefits of Increasing Faculty Student Engagement

  • higher grades
  • improved student confidence
  • increases student perception of being valued
  • increases persistence in higher education

Faculty may find it a bit of a balancing act for sure, but asking about a student concern at the time may help to save time later, should situation grow worse.

How to Increase Engagement

One slice does not fit all – some suggestions will not be for you.

  • provide opportunities for students to write = dialogue
  • attend student events, esp those at are purposeful (e.g. student colloquium)
  • encourage students to attend offices hours, and keep encouraging
  • have projects that encourage collaboration and continued feedback
  • pay close attention to student interactions – if socailly isolated, struggling
  • have faculty model their methods of engaging students to each other – some faculty members are known to be oustanding teachers and have the skills with engaging students, we can learn from them

The Downsides of a CMS in Keeping Up: WordPress & HTML5

As a web developer, I cringe at deprecated code and try my best to keep up to date, which right now means familiarizing myself with HTML5 and CSS3. In reflecting on how best to update our website, I realized that with a CMS, naturally some things are out of my control.

Giving Up Control & Relying on Developers

Whether it’s the core or plugins, users of a CMS are reliant on its developers to keep things up to date. Is that lost of control worth the benefits? Generally, I would say yes, but that doesn’t stop me from wishing that the technology that we use to adopt new specifications.

WordPress & HTML5

Image Tags & Properties

I think it’s interesting that in HTML5 there is now the figure and figcaption elements. If they are taken advantage of, I think it definitely helps to parse information in a webpage and to identify text that is directly related to images.

One thing that does bother me about WordPress (which actually has noting to do with HTML5) is that it forces users to have a title, and leaves alt text blank by default. I don’t know what the best solution may be, but I would propose to insert the title text into the alt text by default and then allowing the user to change it. If they want to leave it blank, then there should be a checkbox to mark it “intentionally left blank” or something. Perhaps this could be an admin option, but I would definitely want something like that since I would really like to force our users to have alt text, but I don’t want to touch the WP core obviously.

Text Formatting Tags

It’s a bit of a minor thing and while some may argue the usefulness of the different semantic tags, users of the rich text editor would have no notion that they’re using <strong> instead of <b> or <em> instead of <i>. While I admit that even I struggle on the appropriate use of each (I have to look it up every time I think about it), if we want to see widespread adoption, then we need to get users to think about their writing and what they intend to do when using any of strong, em, b, i.

Tables

While we avoid tables and it should never be used for layouts, users will still want to insert tables to display data without resorting to an image. I’ve always wondered that WordPress doesn’t have a table insertion button even under the kitchen sink. What worries me is that then users who have a basic knowledge of HTML will insert it themselves using the HTML view with improperly formed code.

Layout & Forms

You might wonder why I’d lump the two, and that’s because, other than (using the default) comment form, both of these are dependent on a WordPress setup.

Forms will generally depend on the plugin. Similarly, whether the layout is in HTML5 is very dependent on the theme, along with many elements of accessibility.

Unfortunately, while HTML5 themes are relatively easy to find, most form plugins do not tell you whether they are using HTML5 or how much of it.

Why Not Adopt HTML5

I do realize that while there are a number of advantages to HTML5, especially in terms of structure,  it’s still in development. Working in an educational institution, it’s also more work and sometimes difficult in some cases to ensure backwards compatibility.

In particular, screen readers do not necessarily support all the new HTML5 elements and will frequently ignore whole chunks of text or have difficulty with reading links, etc. Even the newest versions of screen readers do not necessarily recognize elements and properties designed to make webpages easier for screen readers to interpret.

I would like to think that since WordPress talks about trying to be accessible that anything in the WordPress core will be updated once there is widespread adoption not only among browsers, but also screen readers. Obviously, adoption will take time though. For example, many form input types have been adopted by most browsers, but has not been adopted by IE at all (will be in IE10).

One can only hope that adoption will pick up once various part of the HTML5 specifications are ‘cemented.’

TRY 2012: Drupal for Libraries at UTL

Just a warning that some of this gets fairly technical, especially with hardware setup, and without the related diagrams, it may be difficult to understand, but the basics are there.

Presenters

  • Marc Lalond
  • Andrew McAlorum
  • Graham Stewart

Evolution of the UTL Website

  • recognized need for CMS back in 2003
  • 2005 – used Plone
  • 2008 – had to move frontpage out of CMS, which meant more maintenance
  • 2010 – took another look at new CMS since current CMS needed a lot of Python knowledge and decided on Drupal
  • 2011 – launched new site in Drupal

Drupal

  • little coding work
  • modules (much like WordPress plugins) that are available
  • steep learning curve, but coding not necessary

Drupal Related Additions

  • Drupal Commons – community distribution, pre-configured package
  • Islandora – digital asset management, Fedora database backend
  • Solr – well integrated into Drupal, especially for faceted searching

Implementation

  • multi-site drupal allows multiple instances
  • especially useful for simpler sites with little custom code and modules that are updated
  • built custom Drupal distribution for UTL with all modules, theme, settings
  • theme built on LayoutStudio starter theme
  • next: responsive version

Training

  • regularly schedule training, about once a month
  • covers setup and config, users, content, etc.

Performance

  • 2000 visits per hour
  • single page load = 279 MySQL queries
  • initial loads for 2000 page loads = 558,000 MySQL queries
  • Drupal on one box: User <-> Apache Web Services <-> PHP <-> MySQL
  • problem occurs when there is a bottle neck with a single point of failure
  • Solution: horizontal scaling with multiple servers with Drupal functions split into smaller boxes
    • very flexible
    • less expensive
    • more adaptive
    • fully redundant

Setup

  • individual servers are virtual machines, buil using KVM virtualization with Ubuntu Linux
  • High availability with Keepalived
  • Load balancing with HAProxy
  • Caching using Varnish and XCache
  • Storage on shared high performance disk
  • MySQL query caching with Memcached and Keepalived
  • MySQL master/slave replication + Keepalived

Results

  • 5 minute downtime (planned and unplanned) between Sept 2011 and April 2012
  • load time = < 2s on campus, 4.1 on simulated DSL in Virginia
  • 100% Open Source

As I posted on twitter, I’m quite glad we don’t take care of our own hardware, especially since we just don’t have the people and resources (including not having any server admin), but I was quite impressed with the setup of the UTL Drupal setup. Quite interesting to hear what they’re doing.

TRY 2012: Evolving Services with Technology

Angela Hamilton, U of T Scarborough, spoke about technologies that she has used particularly at a campus where many are commuter or distance education students.

Libguides: Customized tools

  • branding yourself for students to recognize you as their librarian: picture, meebo, contact info
  • info on what is an article, database, annotated bibliography, etc.
  • custom course guide
  • use the tools available to you
  • helps to build relationship with users

Online Meeting Software

  • e.g. Adobe Connect
  • for more advanced reference questions
  • share screen – the “show-er” needs to install a plugin, but viewer doesn’t need to
  • one-to-one, but also for teaching sessions

Screencapture Videos

  • check vendors for already made videos e.g. ISI for Web of Science
  • Jing (sp?) – free 5 min videos
  • answer longer questions
  • can also do it at the reference desk and e-mail it to them
  • esp useful for non-techsavvy and ESL students to review later
  • can also work for one-on-one session if have software for longer videos

I think some of the ideas presented here are great ways to give students further reference on how to do their research, especially on-the-spot screencasts for customized tutorials for them to review later.

TRY 2012: Digital Signage at the Robarts Library (UTL)

This presentation actually not only talks about digital signage itself, but also the work culture change that happened in the systems department at UTL.

Presenters

  • Sian Meikle
  • Bilal Khalid
  • Graham Stewart

Good Signs Can Make a Difference

  • brief
  • consistent
  • easily read

Writing the Message

  • simple
    • reduce: punctuation, pictures, words
    • headline: 22 characters
    • body: 10-18 words
    • short URLs
  • brief
    • 5 seconds per slide
    • 8-10 seconds total
    • usually less is more
  • clear
    • call to action e.g. Chat with a librarian
    • photographs can be powerful
    • coherent design

I don’t know that I agree with all of these, but then it was clear that it depends on the size and distance of the sign as well as where it is.

Presenting the Message

  • Chunking
    • group things together
  • Coding
    • add headings
  • position
    • prime spots on a list: first and last get noticed the most

What Makes Digital Signage Different?

  • easy to update
  • can differentiate content by
    • time of day
    • audience
    • viewing time

What Users Say

  1. Help me make better decisions
    • chat with a librarian, workshops
  2. Save me time
    • maps: library, stacks, workstations
    • directories: by floor, service, name, library
  3. Show me something relevant to me
    • news, community content
  4. Tell me something new and interesting
    • exhibitis, events, news
  5. Give me ideas
    • collection highlights

This is not what their actual users were saying. These ideas were based on a talk done by someone outside of the library and the list here is how those ideas might be applied in a library setting.

Touchscreen Kiosks

  • PHP – CodeIgniter
  • jQuery
  • MySQL
  • Closed Environment – not open to the Internet
  • Javascript Keyboard

Interaction

  • Most Frequent Pageviews
    • since May 2011
    • Libraries & Hours
    • Robarts Directory
    • Workstations
  • User Feedback
    • Let me find a book
    • Let me access this information from my phone

What’s Next

  • catalogue search
    • entire catalogue available
  • StackMap
    • map of physical item location, with directions
  • Responsible Design
    • designed to be used on any device

This is interesting, because we’re working on something similar at our library and we were considering how responsive to make the site. Obviously, we need to seriously consider designing from desktop down to mobile.

Overhead Signage

  • 4 vertical screens
  • PHP + AJAX
  • Media Commons
  • JavaScript video player
  • Fishers Rare Book
  • screensaver

Features

  • auto refresh
  • detection of new content
  • remote control
  • ability to have different slideshows
  • control to switch between slideshows
  • control through phone

What’s Next

  • Scala software across all overhead screens
    • content regions e.g. time at bottom of screen
    • RSS Feeds to Drupal based on another content type
    • Scheduling e.g. times of day

Building Directories

  • one PHP + JavaScript page per vertical pylon (two vertical screens)
  • alternating event feed display (from Drupal, via AJAX)

Development – Devops Movement

  • focus on increase collaboration and cooperation
  • agile methodology applied to system administration
  • agile development and teams (self organizing, cross functional, quick daily meetings, open environments, face to face meetings, encourage input)

On System Administration

  • timeframes all shrink
  • web presence critical
  • software is developed much faster and changes are more frequent
  • massive growth in automation tools
  • growth in OSS: sharing and collaboration

Devops Goals

  1. Eliminate stereotypes
    • developers are careless, arrogant while sysadmins always say no and work all night
  2. Increase communicatin between developers, operations, and management
  3. Continuous systems improvement
  4. Break down barriers and silos
  5. Develop methods to encourage all team members to see the organization’s goals

Advantages

  • all staff use all their skills
    • diversity
    • use knowledge outside defined roles
    • roles expand
    • cross pollination
    • creativity
    • “many minds”
  • enhanced mutual respect and communication
    • greater trust
    • shared responsibility
    • everyone feels a sense of ownership over the end product
    • greater commitment to the product
    • everyone focused on the organization’s end goal
  • happier, move productive staff

Implementing DevOps With Digital Signange

  • operations and development involved jointly from the start
  • weekly full meetings and as necessary (often daily) with quick interrupts/one-on-ones for specific issues
  • fast code releases: several times/week
  • “many minds”
  • two screen display: one browser? 2 PCs?
  • disabling right click
  • URL shortening
  • Planning and execution
    • browser choice
    • OS choice
    • development options
    • design decisions
  • New and experimental project
    • innovative methods required

I thought it was interesting that they spoke a lot about the more technical aspect as well as development methodology. I think it’s a good lesson for a lot of library IT departments that agile development with integrated back and front end staff can be very beneficial, particularly because it makes more development faster and more flexible.

One of the things that came up during the code4lib conference too is that developers should have a small amount of time to work on whatever seems interesting to develop new tools or services.