New Year, New Release

As of January 16, ScholarSphere is at Version 2.1. Folks may remember that we released ScholarSphere 2.0 in September 2014 and unveiled a brand new interface, based on user feedback and participatory user design activities that we undertook in the last couple of years. With the 2.1 release, we focused on improving the functionality of some existing features and broadened discovery possibilities for ScholarSphere content and authors.

Statistics on file access/use
Since we started working on ScholarSphere, we have been keen to expose a variety of usage stats directly in the dashboard, in addition to enabling graph data visualizations for files (example here) deposited to the service. With the 2.1 release, users may now see statistics in their dashboards on the number of file views and downloads generated. The stats date from March 22, 2013.

Screenshot showing the stats part of the ScholarSphere dashboard.

Area of the dashboard in ScholarSphere showing stats.

ORCIDs – Do you have one?
We now have a way for users to enter their ORCID identifiers. (For those who aren’t familiar with ORCID [] – it was created largely to help disambiguate between like names [e.g., “David Jones”] by minting unique identifiers for researchers who sign up with ORCID. My ORCID, for example, is 0000-0003-0013-2655.) Users may input their OCRCIDs in their profile page (the same place where handles for Twitter, Facebook, and Google+ go). We expect there will be an automated way of integrating ORCIDs in ScholarSphere in the near future, especially now that the CIC has joined ORCID as a consortium member.

Image of a section of the ScholarSphere profile page where ORCID IDs and social media handles may be input.

Users can now enter their ORCIDs on the ScholarSphere profile page

And speaking of names . . .
ScholarSphere 2.1 makes possible for users to input names instead of Penn State Access Account IDs when assigning permissions, proxy authorization, and file transfers. Because you just shouldn’t be made to remember random numbers and letters!

Screenshot of the input box for Authorize Proxy, demonstrating that names rather than PSU IDs can now be entered.

No more typing in PSU IDs!

Discovery via Twitter
Post the link to your file in ScholarSphere via Twitter, and your followers can now see all sorts of details about the file you’re sharing: a thumbnail image of it, the keywords you entered, the rights/permission information, and the first few sentences of the abstract or summary for the file. This is what’s called “Twitter card integration.” Another example of discovery of research outputs via social media platforms.

Tweet from Mike Giarlo's Twitter account, showing information about the article (deposited in ScholarSphere) that he has tweeted.

It works! Also, this is a really great article. Click on the image to access it.

The ScholarSphere Users Group (SUG) – Then and Now

In 2012, in the weeks before the Penn State Libraries and Information Technology Services went live with the beta release of the ScholarSphere repository service, we met frequently to draft a fairly detailed FAQ page (see the web-archived version). In doing so, one of us – Nan Butkovich, head, Physical and Mathematical Sciences Library – had the brilliant idea of forming a user group for ScholarSphere that could serve as a resource for people just starting to use the service. Then we released ScholarSphere 1.0, and the rest is history, as they say. But the idea for the user group lingered on the back burner of our minds.

Fast forward almost two years later. In early 2014, as the ScholarSphere Service Team was gearing up to dedicate the next several months to revamping the user interface (UI) and improving the user experience (UX) of the service, we knew we would need a core set of users familiar with ScholarSphere to provide regular feedback on the evolving design. The notion of a user group for ScholarSphere began to percolate again. So, Michael Tribone, UI/UX Developer in ITS Services and Solutions, and I decided to launch the ScholarSphere Users Group (SUG) solely for user response and user assessment purposes. And we decided the group would be based in . . . wait for it . . . Yammer!

Why Yammer? Responsible UX means frequent interactions with users. Because of time constraints, we knew it wasn’t realistic to expect our users to commit to several meetings a month, in person, to show them wireframes and solicit their responses, contribute user stories, participate in user interviews, etc. Yammer was becoming – has become – a key communication channel for user groups at Penn State that typically have face-to-face meetings (typically begin and continue to operate that way, too). What if we tried forming a small user group that would be completely virtual and thus would meet only in Yammer?

The SUG kicked off in February 2014 with an in-person meeting that allowed members to see each other IRL before we went completely virtual. We kept the group under fifteen members, and we made it a private group in Yammer – largely because we’d never done this before and weren’t quite sure what to expect, and because we definitely wanted current users of ScholarSphere in the group. The SUG was instrumental in providing feedback on the emerging re-design of the UI, informing decisions on information architecture, look and feel of the site, and improvements on existing features and functionalities. It was also (and continues to be) a valuable resource for user interviews. In time, Sarah Irwin, Data Services Manager in SaS, came on board to assist with user assessment activities. We hoped the SUG could play a lightweight role in implementing some basic UX, participatory design practices. And it worked!

The original members of this private Yammer group were the following blend of librarians, teaching faculty, staff, and students:

We also added various staff from ITS Services and Solutions to the group, as a way for them to track user needs: Dan Coughlin, Mike Giarlo, Beth Hayes, Jeff Minelli, Jennifer Montminy, Rose Pruyne, and Adam Wead.

So, it’s time to acknowledge the good work of the virtual SUG. MANY thanks to the original “SUG 14” for their participation in the UI re-design process for ScholarSphere 2.0!

A month following the September 24th release of ScholarSphere 2.0, I wanted to let folks know that the SUG is now a public group in Yammer:

The public presence of this user group in Yammer enables all of the Penn State community to learn more about ScholarSphere; post questions about the service; and contribute insight into, and ideas for, new features and functionalities. It’s also a chance to revive Nan’s original idea for the group, in which community members develop as expert users of the service – and, we hope, act as a knowledge base for the group. We invite everyone to join.

In going public, we also plan to hold in-person, bi-monthly sessions in the Libraries, where users across Penn State can get support depositing files, ask questions about the service, and be apprised of various “tricks of the trade” when it comes to using ScholarSphere. In addition, so that we’re not always learning in a vacuum, so to speak, we plan to use these sessions as opportunities for gaining knowledge in data management planning, data publishing, open-access publishing, and in building one’s online scholarly/professional presence, as well as for eliciting input on emerging new features and functionalities.

So, we hope you will join the public SUG in Yammer and soon be on your way to playing a key role in improving and enriching ScholarSphere!

An early wireframe that the SUG made decisions on in March 2014.

An early wireframe for the UI re-design that the SUG made decisions on in March 2014.


It’s been a while since we’ve blogged about ScholarSphere activities – but not for any lack of them! The service team has been incredibly busy since the release of ScholarSphere 1.0. Developers, especially, are coding away on ScholarSphere 2.0, for release this fall, when we will unveil – TADA! – a fabulous new user interface. In other words, we’ve been “ScholarSphering”! Below is what’s been happening of late.

ScholarSphere Collaborates with Zotero!

  • Ellysa Cahoy (Education Librarian at Penn State) developed the grant, in collaboration with Sean Takats (Associate Professor of History and Director of Research Projects at the Roy Rosenzweig Center for History and New Media).

ScholarSphere 2.0 and the ScholarSphere Users Group

    • In spring 2014 we launched the ScholarSphere Users Group (SUG), consisting of teaching faculty, librarians, and library staff. The SUG is one of the engines driving the 2.0 release!
    • This is a lightweight commitment, since SUG interactions take place mainly in Yammer.
    • Here’s our process:
      • Michael Tribone, UI/UX designer, posts user interface designs to Yammer.
      • SUG members offer feedback, generating ideas for improvements.
      • A revised design goes up, and additional responses are gathered.
      • Rinse. Repeat.
      • We do a quick poll to decide on a design, and, once decided, it’s becomes the design for implementation.
  • The service team will be conducting user interviews with a few SUG members in summer 2014, to help us get a fuller sense of what the UX needs to be like for researchers, what tools they currently use, and how ScholarSphere fits, or could fit, into that workflow.
  • Interested in being an SUG member? Request to join our group in Yammer!
  • Watch for a future blog post that will tell more about the SUG, its members, and its activities.

A Gentle Reminder of these Key Features in ScholarSphere

    • Create sets, groups, or collections of files
  • Get large files (> 500MB) into ScholarSphere via Dropbox
  • Allow you to give permission to others to deposit files on their behalf
  • Enable you to transfer ownership of files (perhaps after you’ve give permission for another person to deposit those files)

Next blog post: On promoting and marketing ScholarSphere