Planning for Libra Data
•Download as PPTX, PDF•
1 like•416 views
Lightning Talk for VA Scholarly Communications Summer 2016 Forum
Recommended
Recommended
More Related Content
What's hot
What's hot (17)
Similar to Planning for Libra Data
Similar to Planning for Libra Data (20)
More from Sherry Lake
More from Sherry Lake (20)
Recently uploaded
Recently uploaded (20)
Planning for Libra Data
- 1. Planning for Libra Data June 17, 2016 Sherry Lake Scholarly Repository Librarian Scholarly Repository Services shLake@virginia.edu
- 2. Libra 2.x Project Summary Background November 2014: Libra Services Team submitted Libra 2.0 Project Proposal to Library leadership for replacement of Libra 1.x (Old Hydra/Fedora) institutional repository. The key factors indicating the need to replace Libra 1.x are: 1. to improve information flow into and out of the repository (for depositors, for administration, and for analysis); 2. to eliminate the risks and inefficiencies of further development on a platform comprised of components that are now obsolete and unsupported.
- 3. Libra 2.x Project Summary Project Approval Repository Comparison Report comparing advantages and features of existing institutional repository systems with in-house development of a Fedora 4- based institutional repository system. Reviewed: Dataverse, Sufia, DSpace, Eprints, PURR, CDL-DASH Requirement Categories: • User interface and user experience • Statistics and reporting • Infrastructure • Metadata
- 4. Libra 2.x Project Summary Project Approval Recommendations approved (June 16, 2015): OA and ETD Repositories: Penn State University’s Sufia, as core for UVa-built Hydra/Fedora 4 solution. Data Repository: Harvard University’s Dataverse, hosted and administered by UVa. Pros: DOI minting, no cost, API, “known” data solution Cons: No Fedora compatibility
- 5. Libra Data Working Group • Usability Testing (Limited) • Policies – Deposit License – Use License CC0 (default) • Configuration – Dataverse bugs, UVa Must haves! • Technical Review – DOI account, server, backups, shibboleth!
- 6. Libra Data Rollout January 2016February 2016 March 2016
- 7. http://dataverse.lib.virginia.edu For final, publishable products of research
- 8. LibraryPublishing Data OpenContent ETD OpenEdResources Discovery & Dissemination (OA/SEO, APIs, VIRGO)
- 9. Thank You! Sherry Lake Scholarly Repository Librarian 434-924-6730 libra@virginia.edu
Editor's Notes
- The Libra Services Team compared (pros & cons, and costs) advantages and features of Dataverse, Sufia, and Dspace. Data Repository First Choice: Harvard University’s Dataverse, hosted and administered by UVa. Shared development of repositories has centered on OA solutions with the exception of Dataverse, which places primary emphasis on sharing data and products of research. Products of Research(PoR)/Data https://docs.google.com/spreadsheets/d/1XF47eA4VmOU1SlBB_KV_YY5v0UayQ-gRwKBppY7IUlE/edit#gid=0
- The Libra Services Team will compare advantages and features of other identified institutional repositories with in-‐‐house development of UVa-‐‐specific requirements. Usability testing will be conducted to evaluate fit with repository requirements as expressed in [the Libra 2.0 Project Proposal] document. A report comparing alternatives to building our own Fedora 4-‐‐based systems will be generated by March 2015. Data Repository First Choice: Harvard University’s Dataverse, hosted and administered by UVa. Shared development of repositories has centered on OA solutions with the exception of Dataverse, which places primary emphasis on sharing data and products of research.
- UVA must haves: shibboleth – only Uva authenticated users can deposit Popup publish confirmation
- Two sessions to introduce Libra Data to the Library and one for Researchers
- Benefits of using Libra Data include: Increased visibility and impact of your research data. Sharing your data publicly can increase your research impact and visibility, creating additional opportunities for collaboration and connection within and beyond your existing network. To assist in the sharing process, a persistent identifier (DOI) is created for each Libra Data dataset. Safe management of your data. Depositing your research data in Libra Data not only makes your data discoverable and accessible to a wider audience, but also keeps your data safer. The UVA Library, and UVA’s Information Technology Services, are committed to the durability and sustainability of scholarship deposited in Libra. Libra uses standard data management practices, including security and backup procedures, to provide a reasonable assurance that files will remain retrievable over time. Libra Data will be preserved in the Academic Preservation Trust, of which UVA Library is a founding member and partner. Fulfillment of journal and grant mandates. More journals and public and private funding agenciesare requiring that researchers deposit data created as part of the research process. Publishing your data within Libra Data meets the requirements of these mandates. Valuable research time saved. Using Libra Data’s easy-to-use interface to deposit, describe, and share your data saves you time and allows you to focus on your research.