Institutional Repository

Drupal for higher education is a large industry. There are several top universities that have been using Drupal for a variety of academic purposes. Here is a small list of a few universities that (as of this writing) are using Drupal.

1. Oxford University Drupal 7.72
2. Harvard University Drupal 7.69
3. Massachusetts Institute of Technology Drupal 8.x
4. Duke University Drupal 7.72
5. UCLA Drupal 7.70
6. University of Arizona Drupal 7.72
7. Penn State Drupal 7.x & 8.x
8. University of Toronto Drupal 8.x
9. Johns Hopkins University Drupal 7.x & 8.x

With the release of Drupal 8 several universities, vendors and volunteers have created and contributed to Drupal module solutions to meet academic needs. Here is a list of a few Institutional Repository (IR) & Research Data Management (RDM) related modules currently available for Drupal.

• Google Scholar: Google Scholar(GS) provides a simple way to broadly search for scholarly literature. From one place, you can search across many disciplines and sources: articles, theses, books, abstracts and court opinions, from academic publishers, professional societies, online repositories, universities and other web sites. Google Scholar helps you find relevant work across the world of scholarly research.

  

• Metatag: automatically provide structured metadata, aka “meta tags”, about a website.

  

• SEO Checklist GS indexing crawlers rely on Googlebot to index a site. All of the typical Google crawler requirements need to be met for GS to index a site. That’s what makes a module like this critical.
• Linked Data Lookup Field: Supports Library of Congress Subject Headings, Global Research Identifier Database (GRID) entries, and CrossRef Funder identifiers and autocompletes the values out of the box.

  

• Persistent Identifiers: for minting and persisting persistent identifiers (Handles, DOIs, ARKs, etc.).

  

• ORCID: ORCID integration and allowing users to login with ORCID credentials. The developer explained that this access has access to all of the user’s content from orcid.org. Some small amount of code needs to be written to port the content to drupal.
• IP restrictions: The Condition and Reaction are independent of each other (Context) but if your intent is to block a user from accessing content based on their IP address.
• User Progress API: The User progress API module was sponsored by the Pennsylvania State University. It has been developed for charting students’ progression throughout a system.

Drupal Workflows is a core Drupal feature and is well documented. This was complicated in Drupal 7/Islandora 7 but now this process is trivial and is built into Drupal 8.

Here is a separate page for Bibliography and Citation

Here is a separate page for OAI-PMH

Here is a separate page for Rights and Restrictions

There are Institutional Repository (IR) & Research Data Management (RDM) solutions in production. As of the writing of this there is 1 university running Islandora 8 as an IR in production, Kent State University and 1 an Islandora 8 RDM portal at UPEI

Institutional Repository (IR) in production

Kent State University migrated from Bepress according to Jonathan Hunt from Catalyst IT in New Zealand.

Their repository “formats” according to their search include:

• Articles
• Conference Proceedings
• Images
• Text
• Newspapers
• Books
• Book Reviews
• Yearbooks
• Newsletters
• Videos
• Events
• Journals
• Magazines
• Dissertations
• Editorials
• News Articles
• Datasets
• Presentations
• Symposiums

Their listing of “format” is a bit misleading. All of the data was migrated from Bepress and aligned with their format limitations. Several items are PDFs when a different format would be expected.

The company that migrated Kent State University Catalyst IT also has another Islandora 8 in production “Christ Church City Libraries“ and several more New Zealand sites in beta.

Research Data Management (RDM) in production

This project is supported by CANARIE Awards Research Data Management (RDM) Funding Call 1.

Develop features in Islandora 8 and integrations with other services that provides a comprehensive research data management platform that is informed by the FAIR principles. The project seeks to develop integrations with identifier, metadata, authentication, storage, and dissemination systems and services that support the research data lifecycle and FAIR principles - that is making research data Findable, Accessible, Interoperable, and Reusable. The project is an out-of the box profile (with configurable but sensible defaults) for institutions wanting to curate and manage research data over its lifecycle.

This system created a Drupal content type that represents a research data management plan. DMPRoadMap is software used by DMPTool in the US, DMPOnline in Europe. In Canada, the DMP Assistant in Canada is moving towards that framework. The draft Tri-Agency Research Data Management Policy highlights the importance of DMPs as a best practice in research data management and this feature provides researchers with a tool to help them meet emerging funding requirements. This content type models a generic funder template and associated guidance modeled on the DMPRoadMap. It is possible to have Conditional fields to provide specific funder templates.

This module directly integrates ORCID oauth login relating thier user profile with their ORCID ID and giving them the ability to link thier submitted content with ORCID.

Research Data Management Resources solution created by UPEI “a suite of services for UPEI researchers that includes: a data management planning tool to create a data management plan for a project; a locally hosted storage service to share research files with colleagues; a publishing framework to publish and assign a doi to a dataset to be made public; and a preservation/archiving function to steward research data for as long as is necessary.” [link]

• Planning
  • Create a funding proposal using the Research Data Management Planning Tool.
  • Share a Draft Planning Document
  • Learn more about research data management plans and where to apply for grants.
• WorkSpace
  • Create a managed and backed up data workspace, similar to, but more secure than, a Dropbox account.
  • Synchronize data on your desktop with your research workspace.
  • Create additional workspaces for your research group or projects.
  • Collaborate with colleagues off campus by sharing your workspaces.
• Publishing
  • Export final datasets from your WorkSpaces into a long-term data repository.
  • Automatically assign a Datacite Digital Object Identifier (DOI) to your dataset which provides a persistent identifier and a Datacite metadata record that facilitates both discovery and citation of your dataset.
  • Share your data publicly, including assigning an appropriate data sharing license.
  • Access metrics for your datasets.
  • Sharing your data with specific people or groups.
• Archiving
  • Move your valuable research data (including raw data) to the long-term repository, thereby meeting funder mandates for preservation of the data.
  • Access and manage your data archive.
  • Make an appointment to discuss your data archiving requirements with the Robertson Library.
• Finding
  • Search for data produced by UPEI researchers.

Slides availables for UPEI

Other Institutional Repository Requirements

1. Supports roles and role types. These are all controls managed by Drupal’s User management along with the core mediation module.
   • Anonymous users
   • Submitter: authenticated user; can submit items (objects) to one or more collections
   • Collection administrator/Editor - can add/remove submitters to a collection; can approve and publish / reject submissions; can edit item metadata; can withdraw items from public view; can delegate reviewers to submissions through roles.
   • Reviewer - can view an item not yet published and provide comments to Collection administrator/Editor.
   • Repository administrator - can perform all functions of the collection administrator for the entire repository; can add new collections.
2. Personalized system access for registered users and segregated submission workspace through basic workflow setup can be accomplished with almost exclusively Drupal core modules.
3. Again Drupal’s user management supports assigning multiple roles with users in the system with different permissions
4. Ability to upload files over 2 GB via GUI into the system.
5. Ability for submitters to upload objects into the system and have that item published by a user with another role and was covered by a previous requirement.
6. Ability to create a metadata only record that refers to an externally hosted object. Depending on the type of content this is mostly built into Drupal core code. When creating a media object this is basically what happens. The next step of either pointing to a local file or a remote resource is fairly common with content management systems.
7. Generates persistent document identification (DOI) for creating permanent links to individual records (CNRI Handles, DOIs). Minting DOIs has been accomplished with the Islandora Research Data Management Platform repository for datacite DOIs. For more information on minting DOIs please see OAI-PMH & DOI Minting
8. There is no documentation or expressed interest from the community (as of yet) in automatic deposits via the SWORD protocol.
9. Ability to populate the repository from objects in an ORCID profile could mean a few things. There are several modules and options to look at for possible options. Here’s a couple

   

   • Bibcite Import Orcid: The purpose of this Contrib module is to be able to import publications from ORCID public API into the ‘Bibliography & Citation’ module.
     • ORCID Importer
   • adds a User entity field to store the user’s ORCID
   • adds an “Import ORCID data” button to the User’s profile page
   • adds an “ORCID Configuration” form for the website using the module where the user can configure the ORCID API integration