Logo OR2015

Conference Agenda

Overview and details of the sessions of this conference. Please select a date or room to show only sessions at that day or location. Please select a single session for detailed view (with abstracts and downloads if available).

Return to conference web site

Session Overview
Date: Monday, 08/Jun/2015
9:00am - 12:30pmWorkshop 03: The DuraCloud Workshop: "Clear Blue Skies" Training and Discussion
Regency E 

The DuraCloud Workshop: "Clear Blue Skies" Training and Discussion

Carissa Smith, Bill Branan

DuraSpace, United States of America

The DuraCloud workshop will familiarize participants with the DuraCloud open source software and hosted service. Starting with an overview of the core DuraCloud open source software and REST API capabilities, the workshop will then move into how to transfer content into DuraCloud, how DuraCloud replicates and performs content health checks, and how to retrieve content from DuraCloud. Participants will follow along with a hands-on, interactive demo of the DuraCloud software as examples of the abovementioned are discussed.

Smith-The DuraCloud Workshop-66.doc
1:30pm - 5:00pmWorkshop 08: A Hands-On Introduction to GeoBlacklight
Regency E 

A hands-on introduction to GeoBlacklight

Jack Reed

Stanford University, United States of America

GeoBlacklight is a discovery solution for geospatial data that builds on the successful Blacklight platform. Many repositories have collections of GIS data and maps that aren’t easily discoverable. GeoBlacklight solves these problems by providing a geospatial user focused discovery experience. This will be a hands-on workshop, showcasing the features of GeoBlacklight and working through installing and running the software.

Reed-A hands-on introduction to GeoBlacklight-180.pdf

Date: Thursday, 11/Jun/2015
11:00am - 12:30pmFED1: Fedora Interest Group 1: Fedora 4 Deep Dive
Session Chair: Susan Agnes Lafferty
Regency E 

Fedora 4 Update

David Wilcox


With the recent launch of Fedora 4.0 and upcoming support for Fedora 3 to Fedora 4 migrations, this is an exciting year for the Fedora community. This significant release signals the effectiveness of an international and complex community source project in delivering a modern repository platform with features that meet or exceed current use cases in the management of institutional digital assets. Fedora 4 features include vast improvements in scalability, linked data capabilities, research data support, modularity, ease of use and more.

This presentation will provide an update on the Fedora project, both in terms of the community and the software. This includes important information on community growth, the new governance model, support for Fedora 3 to Fedora 4 migrations, and the roadmap for the next year. Attendees will have an opportunity to engage with the Product Manager and Technical Lead and find out how they can participate in upcoming Fedora project initiatives.

Wilcox-Fedora 4 Update-170.pdf

Fedora Technical Working Group - Assessment of Fedora 4

Declan Fleming1, Esmé Cowles1, Zhiwu Xie2, Adam Soroka3

1University of California, San Diego; 2Virginia Tech; 3University of Virginia

Last year’s production release of Fedora 4.0.0 (F4) came with significant capability improvements from previous Fedora versions. However, given the newness of the internal application stack, F4 also came with a variety of questions and concerns. It was not clear to many Fedora stakeholders whether F4 held fast to the project’s historic values of preservation and durability, and if the future-facing features performed as expected. It was out of these questions that the Fedora Leadership team formed a working group chartered to analyze and assess the current state of F4 and its suitability as a platform to meet the community’s future needs.

This team, termed the Fedora Technical Working Group, established nine areas of which the top four were selected for an in-depth assessment. The areas of assessment were as follows:


- Clustering

- Preservation-worthiness

- Performance

An assessment was produced for each of these four areas which then resulted in specific outcomes and recommendations.

Fleming-Fedora Technical Working Group-63.pdf

Upgrading? Migrating? There’s a portmanteau for that!

David Wilcox1, Michael Friscia2, Nick Ruest4, Adam Wead3

1DuraSpace; 2Yale University; 3Penn State University; 4York University

Fedora 4, the new, revitalized version of Fedora, boasts a feature set that includes improvements in scalability, linked data capabilities, research data support, modularity, and more. Since the launch of Fedora 4.0, a number of institutions have begun the process of upgrading their existing Fedora 3 repositories to Fedora 4 and migrating their content (thus the portmanteau "upgration"). Upgration will be different for every institution, but the common thread is the wealth of new opportunities Fedora 4 provides, both in terms of data modeling and application integrations.

This presentation will focus on planning a move to a new repository platform and the opportunities provided by the new Fedora 4 feature set. In particular, the Linked Data Platform implementation provides some exciting capabilities for enhancing metadata and building semantic relationships between objects both within the repository and on the open web. By engaging in upgration projects now, the panelists are making sure their use cases are supported, as well as paving the way for full scale migrations later this year. Attendees considering their own upgration projects will have a chance to learn from the experience of the speakers and get excited about the new opportunities provided by Fedora 4.

Wilcox-Upgrading Migrating There’s a portmanteau for that!-169.pdf
1:30pm - 3:00pmDSP2B: DSpace Interest Group 2B: Supporting Open Scholarship / Exploring Metrics
Session Chair: Sarah Potvin
Regency E 

Supporting Federally Funded Research Requirements with DSpace and SWORD

Hui Zhang, Michael Boock

Oregon State University, United States of America

The National Institutes of Health (NIH) Public Access Policy requires that final peer-reviewed journal manuscripts sponsored by the agency are freely available in PubMed Central (PMC) no later than 12 months after the official publication date. Furthermore, NIH requires that researchers who apply for grants must include a PMC reference number (PMCID) when citing their papers that were supported by NIH funds. To meet the rising demands from researchers to provide support for fulfilling the NIH public access mandate and article submission requirements, the Oregon State University Libraries & Press implemented a web application to facilitate article deposit using DSpace and the SWORD protocol.

Zhang-Supporting Federally Funded Research Requirements with DSpace and SWORD-68_a.pptx

Visualizing Open Access: building a scalable infrastructure to showcase the reach of MIT research

Richard Rodgers, Matt Bernhardt, Michael J Graves, Sean Thomas

Massachusetts Institute of Technology, United States of America

The MIT Libraries recently launched a public reporting system to display how items in the MIT Open Access Articles collection have been downloaded over its history. Our presentation describes the project to build this platform, including: the need to build a system capable of scaling to tens of millions of downloads; the significant work to improve the collection itself, with particular attention paid to author and department identities; the construction of a data processing pipeline to augment and summarize download logs from the DSpace@MIT service; and the design of a series of interfaces to visualize this information for the public, contributing departments, and individual faculty members. We also describe the lessons we learned through this process, and detail some planned next steps.

Rodgers-Visualizing Open Access-181_a.pptx

Metadata based usage statistics for DSpace

Art Lowel, Lieven Droogmans


The DSpace infrastructure for logging page-views and downloads has been limited to aggregations on communities, collections and items. While this already provides a wealth of aggregated information that is impossible to retrieve using Google Analytics, it still does not assist a repository manager in addressing questions such as:

“How many downloads did Professor X get through Google Scholar last month?”

Because authors are represented as metadata on items, tackling this challenge effectively means opening the potential to aggregate pageview and download statistics on any metadata field in the repository.

By the time of the conference, functionality that addresses this need will be available as part of @mire’s Content and Usage analysis module. The metadata based usage statistics were realized in co­development with the World Bank.

Lowel-Metadata based usage statistics for DSpace-112_a.pdf
3:30pm - 5:00pmDSP3B: DSpace Interest Group 3B: DSpace-CRIS Workshop
Session Chair: Tim Donohue
Regency E 

DSpace-CRIS Workshop

Andrea Bollini1, Luigi Andrea Pascarelli1, Michele Mennielli1, David Palmer2

1Cineca, Italy; 2Hong Kong University

The 90-minute workshop will introduce attendees to the latest version of the DSpace-CRIS module, covering its functional and technical aspects.

DSpace-CRIS is an additional open-source module for the DSpace platform. It extends the DSpace data model providing the ability to manage, collect and expose data about any entities of the research domain, such as people, organizational units, projects, grants, awards, patents, publications, and so on. Before OR2015 a new version of the system will be released to follow the new DSpace 5.0 version. The new version contains, among other things, important enhancements of its integration with ORCID.

The DSpace-CRIS extensible data model will be explained in depth, through examples and discussion with participants.

Other main topics are DSpace-CRIS "components", management of relationships and network analysis functionalities.

At the end of the workshop, participants will be able to:

- understand the DSpace-CRIS data model

- evaluate if DSpace-CRIS fits the requirements of their institution

- use the DSpace-CRIS User Interface

- change the default configuration, adapting it to a specific data model.

Bollini-DSpace-CRIS Workshop-132.pdf