Direct comparison
CRIS Vendors Compared: Pure vs Elements vs VIVO
Compare Pure, Symplectic Elements, VIVO, and DSpace-CRIS — ownership, open-source vs. commercial licensing, and which CRIS fits your institution's needs.
Side-by-side comparison
| Dimension | Pure | Symplectic Elements | VIVO | DSpace-CRIS |
|---|---|---|---|---|
| Ownership / vendor | Elsevier (part of RELX Group). Originally built by Atira A/S (Denmark, founded 2002); Elsevier acquired Atira in August 2012. | Digital Science, a portfolio company of the Holtzbrinck Publishing Group (same parent group as Springer Nature, operated independently). Symplectic was founded in the UK in 2003 and joined Digital Science in 2011. | No commercial vendor — community-governed open source. Originated at Cornell University Library (2003); became a DuraSpace open-technology project (2013); DuraSpace merged into LYRASIS in 2019, which now hosts VIVO's governance. | No commercial vendor — an open-source extension of DSpace, itself LYRASIS-stewarded (originated at MIT Libraries with Hewlett-Packard Labs, released 2002). The CRIS-entity extension is developed primarily by 4Science, an Italian company, with the DSpace community. |
| License / cost model | Proprietary, commercial license; per-institution subscription/licensing fee. | Proprietary, commercial license; per-institution subscription/licensing fee. | Open source, BSD License; no license fee. Institutions still budget for hosting, configuration, and optional LYRASIS member support. | Open source, BSD 3-Clause License (same as core DSpace); no license fee. Most production deployments contract 4Science or another integrator for implementation and support. |
| Underlying data model | CERIF-based relational model — researchers, organisational units, publications, projects, awards, and equipment as connected entities. | A harvesting-and-workflow engine layered over a relational store, built to discover and match researcher publications rather than model a full institutional entity graph. | Semantic web / linked data — an OWL ontology (drawing on FOAF, BIBO) storing data as RDF triples, queried via SPARQL. | Extends the DSpace repository's metadata model with additional entity types (person, project, organisational unit, journal, funding, equipment) alongside items/collections/communities. |
| Automated publication harvesting | Yes — built-in harvesting from Scopus, Web of Science, Crossref, Embase, PubMed, with researcher-claiming workflows. | Yes — this is Elements' core function: automated discovery/matching from Scopus, Web of Science, Crossref, PubMed, arXiv and similar sources. | No built-in harvesting engine; populated via API/RDF ingest from other systems, not automatic literature-database matching. | No dedicated harvesting engine; commonly paired with a harvesting tool (e.g. Elements) or fed via OAI-PMH/API from upstream sources. |
| Public researcher-profile portal | Yes — a configurable public 'research portal' is a standard feature. | Limited on its own — primarily an internal capture/reporting tool; public display usually comes from a paired system. | Yes — public linked-data researcher/organisation profile pages are VIVO's core purpose (human-readable and machine-queryable). | Yes — researcher, project, and organisational-unit profile pages alongside the repository's item pages. |
| Typical institutional use case | Large research-intensive universities needing one system for national research-assessment submission (REF/ERA-style), funder reporting, and a public portal. | Institutions primarily needing reliable, low-effort publication capture and faculty activity/impact reporting, often feeding a downstream system. | Institutions or consortia wanting an open, linked-data researcher network without recurring vendor licensing. | Institutions (often in southern Europe and Latin America) wanting one open-source platform combining repository and CRIS, meeting open-access/assessment mandates without a commercial license. |
| Governance model | Vendor-governed (Elsevier product roadmap; customer advisory input, no open community governance). | Vendor-governed (Digital Science product roadmap; customer advisory input, no open community governance). | Community/consensus governance — elected/appointed Leadership Group within LYRASIS's membership-based governance model. | Core DSpace is community-governed via LYRASIS (MOU, Steering Group); the CRIS-extension module is developed primarily by 4Science in coordination with that community. |
Common questions
FAQ
Are Pure and Symplectic Elements both owned by Clarivate?+
No. Pure is owned by Elsevier (part of RELX Group); Symplectic Elements is owned by Digital Science (a Holtzbrinck Publishing Group company). Clarivate owns a separate commercial CRIS product, Converis — a distinct system from either. All three are large information-industry-owned CRIS vendors, which is likely why they get conflated, but they have different corporate parents.
Are VIVO and DSpace-CRIS really free?+
The software itself is free and open source (both released under the BSD License) — there's no vendor license fee. Most institutions still budget for hosting, configuration, integration, and ongoing support, whether handled in-house or contracted out (commonly to 4Science for DSpace-CRIS, or via LYRASIS membership for VIVO).
Can Symplectic Elements and Pure be used together?+
Yes — this is a common deployment pattern. Elements is used as the automated publication-capture and researcher-facing front end; Pure (or another downstream system) handles institutional reporting and the public research portal.
Is DSpace-CRIS the same as DSpace?+
No. DSpace is the underlying open-source repository platform (BSD-licensed, originated at MIT Libraries with Hewlett-Packard Labs in 2002, now stewarded by LYRASIS). DSpace-CRIS is an extension of it that adds CRIS-style entity management (people, projects, organisational units) — a standard DSpace deployment without that module is not DSpace-CRIS.
