|Digital Commons Feature||Hyku||Hyrax||Hyrax with Analytics and Collection Extensions||Fulcrum||Open Journal System||OCS||VIVO||Laevigata||ETDplus Toolkit||Spotlight||Invenio||figshare for Institutions||DSpace||Islandora|
|Expert Gallery Suite (integration)||NA|
Not out of the box. Drupal community can be leveraged for Gallery, Slide Show, or Exhibit features.
|Author profiles ("Selected Works")||NA||Yes. |
Scholar objects are described in MADS. Example: http://islandscholar.ca/islandora/object/ir%253Aabdelaziz
|Journal publishing||NA||Possible. |
No content type for Journals; however, a Journal could be organized or represented by the Collection Content Model. There is support for individual journal articles (Citation cModel)
|Impact & analytics ("the map")||In progress - with Analytics Working GroupNA||Islandora Google Analytics and Islandora Altmetrics modules are available out of the box. There isn't an analytics map feature.|
|Impact & analytics (email notifications)||In progress - with Analytics Working Group||NA|
Drupal Rules module can be leveraged to create email notifications triggered by specific hooks.
|Improved SEO (GScholar?)||Yes. |
Google Scholar tags are added to a citation object's page to be crawled by GoogleBots. Tags are also recognized by Zotero. When using a default Dublin Core display, Schema. org specific tags are added to metadata fields.
Available via customizable workflows
Available via customizable workflows
|Yes, via customizable workflows|
Islandora Scholar suite of modules provides content model support for thesis/dissertations and citations. Various batch ingest options via DOI, PMID, EndNote, RDF, etc.
|Conferences & events||Yes, via collections, but only to host content.||No.|
|Open Educational Resources/Books||No.|
|"Complex collections"||Collection Extensions work allow for complex collections||Collection Extensions work allow for complex collections||ability to group content by "department"||Yes. Collections with sub collections.|
Collections can have sub-collections. Objects can be members of more than one collection.
Not out of the box. Drupal community can be leveraged for Exhibit features. Or possible to integrate will external applications such as Omeka.
|"Customizable metadata"||Yes, you are able to add custom metadata fields at an institutional or department level.||Yes. Modified Qualified Dublin Core primarily. I/O functionality with MODS and MARC|
Islandora XML Forms and Form Builder can support any XML-based schema. A knowledge of xpath is needed to modify forms.
|"Design and branding customization"||Customizable design, branding, and content blocks||Customizable design, branding, and content blocks||Customizable design, branding, and content blocks||Yes, there are elements of the figshare portal you can tailor to your institution's brand.||Yes. By community and collection||Yes. Drupal is the front end of Islandora and is infinitely customizable.|
|Digital Commons Network||NA - though possible connectivity via other services (e.g. SHARE)||NA - though possible connectivity via other services (e.g. SHARE)||figshare.com||No.However, repository can be harvested by aggregators through via OAI||No. |
However, repository can be harvested by aggregators through the Islandora OAI module to promote discovery of repository assets.
|DOI integration||yes||No. DOI can be added as metadata.|
DOI can be added to a metadata entry/ editing form as an identifier field. See Islandora XML Form builder.
There is a DOI batch ingest module that allows an user to upload a txt file of comma separated DOIs or compile a list of DOIs in a GUI for ingest.
Some community members have build custom workflows that mint DOIs when a research object is published or embargoed.
ORCID can be added to a metadata entry/ editing form as an identifier field. See Islandora XML Form builder.
|Hosted Option||Hyku Direct||NA||NA||figshare.com||dspacedirect.org||Yes. Community service providers offer hosted options. Or users can stand it up on a cloud provider themselves.|