Displaying images and embedding external media

• Chrissi Dean (Unlicensed) to identify who, if any, staff from CSU we sholder tap to join either of these groups.I think yes to Communications, as they publish content, but over to you.
  
• David Archibald (Unlicensed) to identify who, if any, staff from CSU we sholder tap to join either of these groups.I think yes to Communications, as they publish content, but over to you.

Display Images (WIP-228) and Embed external media (WIP-230)

Content for email

The WIPII team have almost completed the initial workshops with faculties and schools (one to go). While still synthesising the observations and preparing our report-back, a few themes have already emerged that have been requested in every workshop to date. Without concluding that these are the only areas (of course there will be many more) we know that we need more detailed requirements for these following two areas:

1. Displaying images: Users require a (small) number of well-developed and supported methods to display still images (i.e. photos) and often associated text/actions. These include a single main image, tiled images, a carousel or gallery for collections, a listing style). Users have also mentioned specific requirements (that might or might not be in scope) around image resizing, automating manual tasks, and simplifying the editing work for frequently performed tasks.
2. Embedding external media: Both staff and students use many different external content sources, be it marketing/recruitment collateral or the course work and research outputs, embedded in to VUW web pages. There are benefits to displaying some of this on our website, even when the University is not best suited to host/stream. Examples include media streaming, collaborative work spaces, digital object repositories, etc. Users have also mentioned some general requirements such as guidelines on embedding that would reducing risk and increasing the quality, and even possible policy/rules on the terms of use and locations of different hosting and streaming services.

I am seeking your input to identify a small number of staff (ideally one or at most two per faculty) to form a working group to draft (or at least provide me and I do the drafting of) the detailed requirements for these two themes. The nominated people would need to:

• Be familiar with this area/topic
• Be responsible for pages that need this content/functionality
• Have an interest in specifying how this works in future
• Can make themselves available for a few discussion/workshops over the next few weeks.

I expect that some faculties will have the same person(s) for each group and others will have a different representation at each. And it is also perfectly acceptable to trust that your requirements will be catered for by the contributions of others and place nominate nobody.

Table of participants

Not all workshops will require representatives from all the following categories, but the table serves as a check list of who to consider.