You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Attendees

  • Eveline Ferretti, Karl Rozyn, Jenny Leijonhufvud, E. Lynette Rayle

ACTION ITEMS:

 

  • Eveline will create PDF documentation of the two requests made since last spring to serve as a basis for beginning to form a policy.
  • Eveline will flesh the policy out from Mann's perspective.
  • Lynette will check in with Darcy about the formation of a policy group and stakeholders group
  • Lynette will check in with Darcy about CUL-IT policy on commitment to content in Spotlight
  • Lynette will check in with Kevin on the status of the accessibility review for Spotlight app and content of exhibits

Notes:

Community Groups

  • It was suggested that there be 2 groups: 
    • policy group - internal library staff only that creates policies around copy rights, acceptance criteria for new exhibits, etc.
    • stakeholders group - larger group of exhibit curators interested in providing feedback to the policy group and helping to prioritize new features and bugs.
  • Eveline was wondering when this would be formed as it would be the group. From her perspective, ideal timing is to identify participants of the policy group soon and plan for the  first meeting late October or early November.

Outside requests for exhibits

These include requests from faculty for exhibits created in a class, requests from students, etc.  These are tentatively being evaluated using a similar process to that used for the Gallery exhibits space at Mann.  There is a need to develop a policy for these requests.

ACTION: Eveline will create PDF documentation of the two requests made since last spring to serve as a basis for beginning to form a policy.

Tentatively, the policy will require:

  • Sponsorship
    • Library Sponsor - someone in the host library who will work with the outside requester to answer questions, provide resources, connect them to technical staff if needed, and provide final approval before an exhibit is published
    • Faculty Sponsor - student exhibits require a faculty sponsor to guide the students work, ensure that copyright requirements are met and documented, and sign off on the final exhibit before it can be published
  • Commitment from the library
    • Establish up front how long the exhibit will remain published.  Convey how an exhibit will be handled when it is no longer published.
    • Establish the commitment by the library to exhibits that are identified as remaining up "forever" once published.
      • Will there be resources to migrate the content to a new platform if spotlight is retired? 
      • Will exhibits be archived as static exhibits?
      • Will exhibits be retired and no longer have a web presence?
      • Will exhibits be reviewed to determine which of the above strategies should be used?
  • Content requirements
    • All exhibit content must have documented copyright.
    • How will images with restricted copyright be handled on the site to prevent unapproved usage?  (e.g. watermark)

ACTION: Eveline will flesh this out further.  This can be used as a starting point for the policy group discussions.

Documentation

Documentation exists now in the Exhibits Knowledge Base.  There was a suggestion to look into Lib Guides as a potential location for documentation.  The current documentation needs improvement to fill out the coverage of topics.  It would be good to connect the documentation to the Stanford videos.

Accessibility

Were accessibility tools run?

  • Is there a report?
  • Are these for spotlight as an application, for exhibit content, or both?
  • Do we have recommendations for exhibit curators to make sure their exhibits are compliant?
  • Based on this, are there ways to force people to enter exhibit content in a way that makes exhibits compliant?
  • Do we need to run the tool on exhibits before they can be published to insure that content is compliant?
  • Do we need to periodically run the tool on published exhibits to insure content remains compliant?

 

Top 3 Issues to Address

They would most like to see the following 3 issues addressed...

  • BUG: 502 bad gateway error (still happening very regularly)
  • BUG: disappearing links & images for page widgets
  • accessibility compliance

 

 

  • No labels