Memorandum of Understanding Workshop: Creating a Process for Successful Digital Collaboration
•Download as PPTX, PDF•
2 likes•943 views
When working on digital projects, it is necessary to utilize experience in various departments within and outside of the library. A planning document called a Memorandum of Understanding (MOU) serves as an agreement between all stakeholders, which will likely include multiple library departments. In order to set expectations, an MOU can assist in the following ways: (1) Evaluating current and potential infrastructure; (2) Determining whether funding is needed or available, (3) Establishing clearly demarcated responsibilities and outcomes for each individual participant, (4) Accounting for and settling potential disagreements, and (5) Serving as a project management plan.
Recommended
Recommended
More Related Content
Similar to Memorandum of Understanding Workshop: Creating a Process for Successful Digital Collaboration
Similar to Memorandum of Understanding Workshop: Creating a Process for Successful Digital Collaboration (20)
More from librarianrafia
More from librarianrafia (20)
Recently uploaded
Recently uploaded (20)
Memorandum of Understanding Workshop: Creating a Process for Successful Digital Collaboration
- 2. About Us Rafia Mirza Digital Humanities Librarian @LibrarianRafia | rafia@uta.edu Peace Ossom Williamson Research Data Librarian @123POW| peace@uta.edu Brett D. Currier Director of Scholarly Communications @BrettDCurrier| brett.currier@uta.edu
- 4. Origin
- 5. National Theme Traditionally, librarians engaged in transactional service. Many of us are beginning to engage in collaborative work.
- 6. External partners may have • Expectations that are higher than possible • Expectations that technology does not allow • Expectations that do not coincide with strategic priorities • Expectations that are unfair
- 7. Librarians tend to have • Inclinations toward saying “Yes” • Inclinations toward gold plating • Inclinations toward not expecting shared credit • Inclinations toward providing seamless (invisible) service
- 9. Workbook Contents • Introduction MOU Documents • Workflow & Instructions • General Template & Instructions • Estimate of Institutional Support & Instructions MOUs for Standardized Projects • Systematic Reviews • Open Access eJournal Hosting & Publishing
- 10. Workflow
- 11. Template Contents Basic Building Blocks • Purpose and Scope • Definitions • Background • External Funding statement • Parties’ Responsibilities • Ownership statement • Signature and Date Optional Additions • Technology Limitations • Project Continuation Plans • Any Contingencies • Mutually Agreed Upon Workflows • Archiving and Preservation Plans • Anything else
- 12. Template Contents Addenda • Collaborator’s Bill of Rights • Project Recommendations • Upfront Costs • Estimate of Institutional Support • Others
- 13. Estimate of Institutional Support Name Job Title Expertise Hours Inst. Rate Market Rate Inst. Total Market Total Total Description of Hardware/Software Institution Cost Market Cost Institution Total Market Total Total
- 14. Workbook Contents • Introduction MOU Documents • Workflow & Instructions • General Template & Instructions • Estimate of Institutional Support & Instructions MOUs for Standardized Projects • Systematic Reviews • Open Access eJournal Hosting & Publishing
Editor's Notes
- Rafia
- Rafia :SPEC Kit, Blogs, etc. That Camps
- Rafia: You agree on blueprint before you commit resources, so you both know you are building a ranch house, and one partner is not expecting a mansion, while you think you are making a birdhouse. / Make service visible, turn it into collaboration: /Make the amount of work a project will take visible before it is begun /Accidental Commitments/ Positive Experiences b/c of MOU use./ Clarity of roles, process, timelines, and expected outcomes for all parties Service: http://literaturegeek.com/2016/02/28/DHjobtalk/ http://acrl.ala.org/dh/2013/06/19/in-service-a-further-provocation-on-digital-humanities-research-in-libraries/ Whole issue: is everyone has different expectations, so this whole process is about making sure all partners are on the same page For a long time libraries had established workflows AND liaisons tended to work alone, but now so many changes, and doing many types of projects you had not done before (so hard to judge how long they will take )
- Rafia: NOTE Specific examples. 1. 10 year project timeline want to do in 1 year. 2. Omeka (web vs. server install. 500 mb vs. Server space) 3. Collection vs. Project area focus/Scope 4. Timeline
- Rafia
- During and after implementation: Attribution Publication Conference presentation Grant application Funding allocation Disruption
- Overview Each template that you might want to use has been added as a word document so you can pull it out to edit and make changes.
- Phase I - Library stakeholders: Talk to their supervisor. Consulted b/c long term plans of that department or the library Phase II – Timelines/ Software Needs Phase III - No major substantive change, getting final approval/sign off Phase IV: No work started before now, documents in one place can become a template for your own institution
- Rafia
- Talk briefly about how we have covered much of the workbook and that as you continue with certain projects, you may developed MOU templates for these as we have with systematic reviews and open access journal hosting and publishing
- Questions? #utamou