Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 25 Next »

Design and content standards 

Tasks

  • Read "service design" model for LibGuides LGServDesign.pdf
  • Identify categories and structure of design and content standards 
  • Determine which group members will write standards for the different categories
  • Provide rationale for standards (for colleagues) 
  • Create template(s) for guides 
  • Create design and content standards for LibGuides  
  • Make decision about the role of LibGuides within our larger site ecosystem (what content goes into LibGuides vs Drupal, etc.)
  • Share draft of standards with RIS and LibGuides Administrators group 
  • Share draft of template(s) with RIS and LibGuides Administrators group 
  • Share scope section with Justin as he is working on project for moving some of the How Do Is to Drupal 

Deliverables:

  • Formalized design and content standards for LibGuides 
  • Guide publication checklist
  • Recommendation for delivery of standards to guide authors (e.g. a LibGuide, other internal staff tool, etc.) 
    • internal LibGuide or Gitbook? (discuss with web site group?)

Review process

Tasks

  • Review needs specific to Temple Libraries (see below) 
    • Are there any other concerns or issues we should keep in mind?
  • Consider how Rick's work on current best practices/audit might fit in (maybe related to plan for updating existing guides?)
  • Outline process of review and approval with thought to our specific needs
  • Investigate and test publishing workflow feature in LibGuides to see if meets our needs to  (can "groups" be set up so that HSL and Law could have their own workflow if needed?)
    • Determine to what extent the publishing workflow feature meets our needs
    • If publishing workflow does not meet our needs, recommend other mechanism/technology for guide review and approval 
  • Determine the mechanism and policy for requesting to create a new guide or "pre-authoring" 
  • Make recommendation for composition of the review team (number of members, duration, etc.)


Notes

LibGuides review process must include

  • A way for a guide author to request and receive approval to create a new guide
    • This is a way to review and determine if a guide is necessary, adequately differs from existing guides, and if the author is the appropriate person to produce that guide
    • Does this apply to course guides or just subject and topic guides?
  •  Accommodation of “last-minute guides” needed to satisfy requests for course-related instruction
  • Timeline for repeat reviews or general guide maintenance 

Deliverables:

  • Recommendations for the process and mechanism for
    • Member composition of review team 
    • Google form for "request to author" 
    • Description of process for submitting guides for review 
    • Description of process for notifying guide authors of guide approval, providing feedback to guide authors who need to make changes and resubmit

Revision of Existing Guides and On-going Maintenance Schedule 

  • Audit of existing LibGuides to identify those that fall beyond the established scope and need to be moved to Drupal/FAQs
  • Proposal for how/timeline to revise existing course and subject guides to meet standards
  • Proposal for maintaining guides going forward (How do we maintain guides going forward? Do they need to go through a "recertification" process that ensures they continue to meet standards?)
  • No labels