Date
Attendees
Goals
- Prioritize reading list application requirements
Discussion items
Time | Item | Who | Notes |
---|
55min | Prioritize reading list application requirements | David | Workflow - Start from the the reading list
- Start from Primo, service menu includes link to add item to list
- Can be restricted to faculty/staff
Users - Multiple co-authors
- List owner, can invite co-authors
- Recommender role (= librarian)
Sharing - Ability to make your list public
- Other people can copy your list and make it their own
- Integrate the same list into multiple courses
Finding and linking to resources - Books, articles through a search (= Primo)
- Entering a resource manually (= form)
- Free things on the web
- Items the instructor has digitized and uploaded into the LMS or some other place
- Highlight cases where user has entered non-persistent library database URLs
- Databases (= specialized Primo/Alma search)
- History of what has been added
- Picking individual resources that have previously been added to other courses
- Recommendations
- Librarian provide recommendations (for now)
- Physical items
- Creates a request to put the book on reserves
- Links, how to handle them
- To OpenURL
- If we don't own it, request the item
- If it's physical, put it on reserve
Management and organization - Organize by type
- Organize by week or part of the course
- Make available only a limited time or for specific people
- Add comments/descriptions to the reading list and for the items
Usage / reporting - How many people viewed the item
- Time spent on an item
- Sense of who used the item (unique users)
- Export reports in CSV
- Is this external versus internal
- Stats for non-instructor, librarians
|
Action items
David Walker will reformulate list in more formal requirements document Â