Samvera Partners Call |
Friday, January 8th, 2021 |
11:30 am | Eastern Daylight Time (New York, GMT-05:00) | 1 hr |
https://emory.zoom.us/j/96461461639?pwd=Y1BJTnBBSlJlZ3BoTUV0L09OdGVXZz09 |
Join by phone |
Dial by your location +1 312 626 6799 US (Chicago) +1 470 250 9358 US (Atlanta) +1 470 381 2552 US (Atlanta) +1 646 558 8656 US (New York) +1 301 715 8592 US (Washington D.C) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) Meeting ID: 964 6146 1639 Find your local number: https://emory.zoom.us/u/ab7TUxc0tC |
We want Samvera Community to be a fun, informative, engaging event for all our partners and participants. We've got a few strategies to help make this happen:
We encourage everyone to apply the Samvera community principles of openness, inquiry, and respect in their interactions at the event.
We have officially adopted an Anti-Harassment Policy.
If you have any questions or concerns, please feel free to reach out to community helpers .
Facilitator: Richard Green & Heather Greer Klein
Note Taker: Chris Awre
Stuart Kenny
Alicia Morris
Seth Erickson, Research Data Librarian for Social Sciences at Penn State Libraries and Product Owner for ScholarSphere, gave a presentation on the development of ScholarSphere 4.0 over the past year, followed by a demo of some of the new functionality. Key points raised were:
- As a reminder, ScholarSphere is Penn State's IR, and was originally implemented in 2012. It facilitates self-deposit and is content agnostic.
- The previous version (3.0, built using Sufia) had become difficult to maintain and wasn't scalable in the ways currently needed. It was also hard to integrate with other systems and missed some features that other repositories (e.g., Dryad) were providing.
- Version 4.0 is taking a cloud native approach to address scalability and has implemented APIs for integration. A key development is the ability to version a work. The development has also seen a refresh of associated repository policies. Version 4.0 is a new tech stack that was migrated to - it is Ruby on Rails and uses Blacklight, but uses PostgreSQL instead of Fedora and has sought to use common tech elements as much as possible. It is licensed using the MIT Licence.
- Seth demo'd the versioning functionality, as well as showing the need for an ORCID ID for any author not at Penn State (who will have their own local ID). Content upload is straight to Amazon by default. Penn State only access is an option for content that cannot be open.
- Questions:
- File versioning - the versioning functionality allows a work to be versioned by changing the file, but in-file edits are not recorded in this way.
- A separate homegrown Researcher Metadata Database uses OAuth to authenticate to ORCID and push metadata there. This may be added to ScholarSphere, but the preferred route is through the RMD. Other functionality using ORCID is planned.
- Fedora (4.7) was taken out of the stack as it was causing performance issues. Penn State also had staff leave who took Fedora knowledge with them.