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

Version 1 Next »

Date

Attendees

Goals

  • Prioritize reading list application requirements

Discussion items

TimeItemWhoNotes
55minPrioritize reading list
application requirements
David
  • Easy way for faculty to add (or request) resources to be added
  • Existing models
    • Primo is a good starting point (export to LMS)
    • Leganto is probably a better model
    • Alma's reading list is kind of clunky
  • 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)
    • Librarian
    • Students
      • Can comment
      • Mark progress
  • Sharing
    • With people in a course
    • With anyone outside the course
    • Other people can copy your list and make one for themselves
      • Ability to make your list public
    • Integrate the same list into multiple courses 
  • Search the metadata of lists
    • Mapping of course names to some standard vocabulary
    • Grab course lists from all campuses to make this

Finding and uploading resources

  • Books, articles through a search (= Primo)
  • Entering a resource manually (= form)
    • Including websites
    • Highlight cases where user has entered non-persistent library database URLs
  • Databases (= Primo/Alma search)
  • History of what has been added
    • Picking individual resources that have previously been added to other courses
  • Recommendations
    • Based on previous things you've added
    • Items from otherreading lists
    • Librarian provide recommendations
  • Digitized instructor-owned material
    • Asset could be stored by the application or in a repository?
    • Link or text in Blackboard/Moodle?
    • We don't have it? Request to purchase it
    • Copyright management (something we can check?)
      • Check Alma digitization request for example of the type of data we would need here
        • Find physical item
        • Creates work order
        • Check copyright
  • Physical items
    • Creates a request to put the book on reserves
  • Links
    • 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
    • Moodle, Blackboard, Canvas has something like this
  • Add comments/descriptions to the reading list and for the items
    • Text, links, etc.

Usage / reporting

  • How many people viewed the item
  • Time spent on an item
  • Sense of who used the item (unique users)
  • Customized reports based on the data
    • Aggregated data across all courses, by major, etc.
  • Export reports in CSV
  • Better idea of what to track here once we know what is possible
  • Accessing things we own versus things we don't
    • Is this external versus internal
  • Stats for non-instructor, librarians

Book store / AL$ type projects

  • Get a list of ISBNs from book store and compare that to library's e-book collection to show already owned books.
  • Maybe push those to the LMS in some way

Action items

David Walker will send out brainstorm list to group to begin shaping it into phases or requirements  

  • No labels