Orvium is founded by:
Among the Orvium team you can find advisors from NASA, CERN or Oracle.
Orvium is member of:
We are partners in multiple European Commission funded projects, amongst others:
Orvium uses Invenio, an open source software framework for large-scale digital repositories that provides the tools for management of digital assets in an institutional repository and research data management systems.
Invenio is initially developed by CERN with both individual and organisational external contributors and is freely available for download.
Orvium is powered by the Invenio digital library framework and is an Open source product.
Our cloud server provider is well known and very trustfull always have the latest security patches applied. Traffic to Orvium frontend servers is load balanced via a combination of DNS load balancing and HAProxy load balancers.
All changes done in the source code or in a infrastructure level are tested and validates on our quality assurance system prior to being applied to our production system. We run two independent systems: one production system and one quality assurance system.
Orvium frontend servers are responsible for running the Invenio repository platform application which is based on Python and the Flask web development framework. The frontend servers are running nginx HTTP server and uwsgi application server in front of the application and nginx is in addition in charge of serving static content.
All files uploaded to Orvium are stored safely and with more than one copy with our cloud server provider. Each interaction that users are doing with the life-cycle of the publication remain in the blockchain.
Papers, reviews, reviewers, citations, authors, etc. are timestamped and hashed within the blockchain. Every submission, modification and review is registered so the complete life cycle of the paper, starting from the first submission, is publicly available. The blockchain enables Orvium to keep a public trace of all the activity pertaining to a given document, including first submission, revisions, accepted and rejected peer reviews, copyright and user license changes, among other activities.
Orvium introduces support for manuscript versions. Initially, any changes in a manuscript will be first treated as a work in progress and only the authors will see those modifications. Once the new version is ready and the authors confirm it in the system, and this action triggers a new submission that creates a new version of the manuscript, which becomes publicly available. These versioning capabilities enhance the complete life cycle traceability by attaching a new version to the history of the manuscript.
Metadata and persistent identifiers in Orvium are stored in a PostgreSQL. Metadata is in addition indexed in an Elasticsearch cluster for fast and powerful searching. Metadata is stored in JSON format in PostgreSQL in a structure described by versioned JSONSchemas. All changes to metadata records on Orvium are versioned, and happening inside database transactions.
In addition to the metadata and data storage, Orvium relies on Redis for caching and RabbitMQ and python Celery for distributed background jobs.
Special note on closed access data
Orvium allows users to upload files under closed access. Closed access means that orvium.io users will not be able to access the files you uploaded. The files are however stored unencrypted and may be viewed by Orvium operational staff under specific conditions. This means that “closed access” on Orvium is not suitable for secret or confidential data.