Remaining Tasks as of Aug 15
| Category | Task | Description | Who | Notes | Status |
|---|---|---|---|---|---|
| Standards | Review standards document | Review full document and note issues regarding readability/usability, consistency in tone and voice, need for more justification, need for directional info | All | Complete by - is more time needed? | In progress |
| Standards | Review suggestions/comments for sections you wrote | Review suggestions and comments made by other team members for your sections. Approve/reject suggestions and revise any sections necessary. | All | Complete by | |
| Standards | Review outline | Review standards outline for heading and section names and overall order | All | Complete by | |
| Standards | Submit to external reader | Colleague outside of group read standards and 1) note anything confusing 2) test instructions to make sure process works when creating and editing actual guides; Create explicit instructions for what they should look for | Jackie, Emily (for sending to Cynthia) | possibly Urooj and Sarah - ask Adam & Steven about having this include key questions and things that we would like them to look for Emily would like to have Cynthia look at it as well by , they return by (talk to Steven about this re extending general deadline) | |
| Standards | Finalize standards document | Finishing touches after group and external reviewer have completed review | 1-2 people | How do we want to submit this with our report? As a document (it's current format) or should we go ahead and create the LibGuide? JS thinks LibGuides admins should review before we create Guide. | |
| Review Process | Draft document of review process | Nancy | Complete by end of day monday | In progress | |
| Review Process | Review and comment on review doc | All | Complete by
| In progress | |
| Review Process | Create tool for request to author (google form) | Nancy | Drafted Google form for submission by author | In progress | |
| Review Process | Create publication checklist | Create and finalize publication checklist for guide authors. | Nancy | Drafted Google form that can be shared between author and review committee. ; could this form be incorporated into the LibGuide workflow? | In progress |
| Review Process | Investigate and recommend tools to facilitate review process | 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?)
| Emily | Complete by communication between guide author and group - could be an email submit to a listserv with a link to a guide: point person to do initial review (assignment to who does it) is a guide assigned to a person on the review team (who makes this decision)
| |
| Review process | Create/setup tool that author uses to submit guide for review | Could be through the LG system, google form, an email to the review team, etc., we just have to be clear about how this happens. | Complete by | ||
| Review process | Create/setup tool for providing feedback on guide to author | Mechanism through which review team provides feedback. Could be a simple document like K-State's or form. | Complete by | ||
| Implementation | Describe process for implementing standards and review process. | Discuss at a meeting (8/23) to ensure that we are all on the same page. | Ideas
| ||
| Final report | Create final report | be explicit about how the standards and review process descriptions will be setup in the LibGuide that we create | |||
| Final report | Review final report | Review final document (all parts except standards which should have been thoroughly reviewed at this point) | All |
OLD Notes/Tasks - Design and content standards
Tasks
- Review current LibGuides best practices
- Review other examples of LibGuides standards
- 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
- Create template(s) for guides
- Make decision about the role of LibGuides within our larger site ecosystem (what content goes into LibGuides vs Drupal, etc.)
- Share draft of template(s) with RIS and LibGuides Administrators group
- Agree on template and "Guide Page and Layout" standards
- Re-read and comment on standards document (note issues regarding readability/usability, consistency in tone and voice, need for more justification, need for directional info)
- Agree on and finalize publication checklist
- Finalize templates and Guide Page and Layout sections after group agrees
- Choose tool for standards
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?)
- LibGuide was decided on at 8/9 meeting
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"
- Create Google Form for request to author
- Create tool that author uses to submit guide for review
- Create tool for providing feedback on guide to author
- Make recommendation for composition and training of the review team (number of members, duration, etc.)
- Make recommendation for authoring a course guide (no need to 'request to author' and can publish without review, but must be reviewed within 24 hours)
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
Implementation Process (including revision of existing guides, on-going maintenance schedule, and first review team)
- Recommend 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?)
- Recommend that the first review team make note of how the review process is working, what changes may be needed, etc. and submit a brief report to administration after the first semester or year