2018-03-14 Strategic Partners

Owned by Emily Toner
Last updated: Mar 19, 2018

Date

Attendees

Agenda

  • Blacklight: Review plan for contributing to Blacklight development process, including quality assurance testing.
  • Website: Begin to outline web content policies and procedures that need to be put into place and discuss the approach to developing those policies and procedures.

Meeting Notes

Blacklight (Emily): Review plan for contributing to Blacklight development process, including quality assurance testing

  • Please review the list of upcoming tasks/goals for the Blacklight project this spring and add your name if you would like to volunteer in providing support for one or more of these: https://tulibdev.atlassian.net/wiki/x/CIA-Hg.  
  • By volunteering, you will be asked to refine requirements for individual issues and conduct quality assurance (QA) testing for developed features. Some of this will be mediated by Emily, though you will also be communicating directly with one of the developers and/or Chad.
    • Emily will be sending out more specific instructions as this collaborative work begins.  

Website (Cynthia): Begin to outline web content policies and procedures that need to be put into place and discuss the approach to developing those policies and procedures.

Goals for Spring 2018

  • Strategic Partners will begin working on the policies and procedures for the web content
  • Site Editors and content contributors will begin reviewing web content for services on the website, focusing primarily on that one content type
  • Web Advisory group will focus on outlining content for the following content types -- Persons, Groups, Buildings, and Spaces -- which are more administrative in nature.

Discuss ideas for policies, procedures, and guidelines that we want right now, especially for writing content, and how to develop and share those

  • Existing editorial guidelines for the LibGuides Review Process -- we can use this as a starting point.
    • Beckie and/or the communications team will be doing a final review of any guidelines created (she will also likely be involved Web Admin group).
    • Whatever we come up with in terms of guidelines would be used by the Web Admin group
  • What else could we be doing? What should we be focusing on?
    • Standardization of web buttons and links
    • Requirements for search engine optimization (ex. titles) and accessibility (ex. alt tag text)
    • How services relate to one another -- ex. services that affect one building/space versus services that affect multiple buildings/spaces
      • Should site editors be making these decisions, or do the Strategic Partners get involved in this?
    • We need to distinguish two separate tasks: how we’re describing vs. what we’re describing. Cynthia would like this team to be involved in building guidelines for both
      • It is important to consider the layout of the descriptive content, including aggregated information (ex. hours page, public computing)
      • Content contributors and site editors can gather/provide the raw content, and the strategic partners can determine formatting/layout guidelines based on that (such as sentence/paragraph limit).
      • In April, there will be a meeting in Paley Lecture Hall with strategic partners, content contributors/site editors, and everyone involved in the web redesign to start sharing and discussing work in progress.
      • Structure/layout will vary based on the content type for web pages, esp. for aggregated pages with partial views of individual services. 
      • Cynthia has already begun working on entity wireframes. Will we need to address changes in content with move to new building? David says to not focus on this for now. 
  • How do we go about this?
    • A lot of this happens off-line, and it’s easier to do this in small groups rather than with the group as a whole.
    • Jackie and Jasmine would like to be involved.
    • Emily/Cynthia will post a breakdown of the basics involved with these tasks for potential sub-groups on Confluence.