...
- Formalized design and content standards for LibGuides
- Recommendation for delivery of standards to guide authors (e.g. a LibGuide, other internal staff tool, etc.)
- internal LibGuide or Gitbook? JS prefers not LibGuides
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 might fit in
- 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.)
...