How it Fits into Workflow

• Gemini a less-moderated connection between users submitting feedback and the people with the power to address the issue
  • as a cooperative, collaborative organization with relatively few individuals dedicated to/paid by BHL directly, this is good
  • Also, we have a more direct route of communication with users
    • Does this closeness that almost mimic the one-to-one traditional library reference response?
    • It certainly allows us to integrate user contact into the workflow in a much more "traditional" way that users should expect, but rarely receive in a decentralized digital library model.

• Gemini streamlines and facilitates the assignment, monitoring, and completion of tasks.
• We have insight into the conduct and actions of our colleagues on tasks we share.
• Much more streamlined and easy-to-follow that endless strings of emails.
• Updates and comments facilitate communication and collaboration
• I think it is important to emphasize the wiki-like aspect.
  • It takes the toil of assigning and monitoring issues away from the small core of full time BHL staff, and "selectively crowdsources" it to the rest of the Staff group
  • The wiki-like aspect compels Staff to participate and observe
  • it's more like "demographic sourcing" not crowdsourcing...

• moderators determine staff to assign to issue
• issue assigned
• staff respond as needed

• Allows us to address user requests and gaps in holdings
  • in ways the traditional BHL scanning workflow does not.
  • While the bidding process remains similar, the titles and items to scan are now driven by Gemini requests.
    • No longer the subject-driven mass scanning model
      • allows newer members (who missed the subject-based scanning assignments) to participate in a very useful way
      • a planning-ahead concept instead of "just scan everything in the subject"
      • effective way to address gaps in titles/conservation issues/etc. left from the subject-based original scanning
  • There is a direct relationship between patron requests and the “acquisitions process”
    • Gemini helps us create/recreate a personal experience for the library user

• Increased level of user participation and interactivity between the content “creators” (contributors) and the user group.
• Streamlines user and priority requests
• Facilitates filling requests by making it easier for different institutions to assess/communicate/fulfill complicated requests (I have vol. 1-7 only, I have vols. 27 & 29, etc.)

• a one-stop-shop for Staff functions/assignments
• Gemini is different from email for division of labor
  • there is incentivization-- sense of "integrated responsibility"
  • there is a different sense of immediacy-- not "real time" so much as "real place"
    • ability- necessity- to use Gemini to track/follow issues
      • necessitates and facilitates an extra moment- time- to actually see/ingest what's going on before contributing.
        • complex questions/thoughtful answers
        • documented for all to see
    • creation of an almost physical-feeling space online for a decentralized staff to work in
• Anticipating needs (how?)

• Gemini fits with the open source integrative philosophy of BHL
  • collaborative, open, draws on varied expertise and strengths
  • division of labor-- no one "has it all"/ can do it all alone