The scope of work for this project has been shaped directly by requirements we have gathered (and continue to gather) from UC faculty, OA project stakeholders and colleagues at other institutions.
Below is a summary of our community engagement thus far, as well as specific opportunities for UC faculty and other OA project stakeholders to engage directly with this project. We also invite you to add your voice to the project's discussion forum or contact the implementation team directly.
Learning from Other Institutions
On May 21, 2012, the UCSF Academic Senate voted to adopt a campus-wide Open Access Policy for all articles published by UCSF-affiliated faculty. In the wake of that historic vote, we began exploring options for implementing such a policy - with the understanding that the rest of the UC campuses might soon follow suit. We had early conversations with institutions that had already implemented similar policies to great effect, particularly Duke, Harvard and MIT.
Those conversations prompted us to begin to refine our deposit mechanism for the eScholarship repository and to explore various solutions for harvesting metadata and, where available, publications on behalf of the faculty. We followed up, in January 2013, with the UCSF Committee on Library and Scholarly Communication (COLASC), where we learned valuable information about the faculty perspective on how best to support their compliance with the policy.
Most recently, we have been in conversation with institutions that have already implemented harvesting or CRIS (Current Research Information System) solutions, including: Cranfield University, Duke and the University of Edinburgh.
Engaging the UC Community in the OAPI Project
In the past year, we have engaged in the question of how best to implement the UCSF/UC Open Access policies with various UC Systemwide groups, including:
- University Committee on Library and Scholarly Communication (UCOLASC) - 10/10/12
- Council of University Librarians (CoUL) - 11/09/12
- Systemwide Academic Personnel staff - 01/09/13
- Systemwide Library and Scholarly Information Advisory Committee (SLASIAC) - 02/02/13
We are now in the midst of the development and deployment of an implementation plan for the UC OA Policy and are keen to work with the UC community to develop a system for supporting the policy that is both intuitive and powerful. The following represent opportunities for us to engage more closely with faculty and OA Policy stakeholders in the coming months.
|Date||Community Engagement Opportunity|
|09/08/14-09/10/14||Representatives from CDL and Symplectic meeting at the Southern UC campuses - UC Irvine, UCLA, UC Riverside, UC Santa Barbara, and UC San Diego - to explore the data gathering tools associated with Symplectic Elements.|
User testing of the automated harvesting system with early access faculty at pilot campuses.
|07/22/14-07/24/14||Representatives from CDL and Symplectic met at the Northern UC campuses - UC Berkeley, UC Davis, and UC Santa Cruz - as well as at UCOP to explore the data gathering tools associated with Symplectic Elements.|
|04/24/14||Representatives from Symplectic and partners from the three pilot campuses – UC Irvine, UCLA, and UCSF – met at CDL to discuss the current status and next steps of the UC OA Policy Implementation Project.|
|11/01/13||Launch of Office of Scholarly Communication site|
|11/01/13||90-second introductory video|
|11/01/13||"Ads” that can be inserted on campus websites with direct access to FAQ, Deposit, Waiver (circulated to campus librarians, UCOLASC)|
|11/01/13||Presentation slides to introduce the policy and the tools that support faculty participation (for use by campus librarians, COLASC members, etc.)|
|10/02/13 - 10/18/13||User testing of Office of Scholarly Communication site|
|9/16/13 - 9/20/13|
User testing of streamlined manual deposit beta. would like to be a beta tester.
Meeting with partners from Phase I campuses (UCI, UCLA & UCSF) to review the latest harvesting tool RFP draft
Dates in bold represent future activities. Subscribe to our mailing list to be notified of updates.
Dates in italics represent past activities
- No labels