General Policies


  • Range: Orvium aims to host publications from all fields of research, the associate technology and science-related events. All the content uploaded in Orvium have to respect the privacy or copyright, and it will not breach confidentiality or non-disclosure agreements for data collected from human subjects.
  • Status of research: It's not necessary that the study is complete, any manuscript from any stage of the research lifecycle is accepted.
  • Users: There are not any requirements to join Orvium, anyone can register and upload the content that own or have the appropriate permissions to upload them.
  • Copyright: Orvium produces bespoke licensing models by design. The model is always the author's own decision. Orvium will not take ownership of any of the contents uploaded to the platform. All uploaded content rights and ownership remains property of the parties prior to submission.
  • Data file formats: Any formats are welcomed. We recommend follow our guide that will help you to deposit content in a friendly format.
  • Volume and size limitations: Total files size limit per record is currently 1GB.
  • Data quality: All information is provided “as-is”, and the user shall hold Orvium and information providers supplying data to Orvium free and harmless in connection with the use of such information.
  • Metadata types and sources: All metadata is stored internally in JSON-format according to a defined JSON schema. Metadata is exported in several standard formats such as MARCXML, Dublin Core, and DataCite Metadata Schema (according to the OpenAIRE Guidelines).
  • Blockchain: Papers, reviews, reviewers, citations, authors, etc. are timestamped and hashed within the blockchain. Every submission, modification and review is also registered so the complete life cycle of the paper, starting from the first submission, is publicly available.
  • Language: English is preferred but all languages are accepted.
  • Licenses: Users must specify a license for all publicly available files. Licenses for closed access files may be specified in the description field.

Access and Reuse

  • Access to data objects: Files may be deposited under closed, open, or embargoed access. Files deposited under closed access are protected against unauthorized access at all levels. Access to metadata and data files is provided over standard protocols such as HTTP and OAI-PMH.
  • Use and re-use of data objects: Use and re-use is subject to the license under which the data objects were deposited.
  • Embargo status: Users may deposit content under an embargo status and provide and end date for the embargo. The repository will restrict access to the data until the end of the embargo period; at which time, the content will become publicly available automatically.
  • Restricted Access: Users may deposit restricted files with the ability to share access with others if certain requirements are met. These files will not be made publicly available and sharing will be made possible only by the approval of depositor of the original file.
  • Metadata access and reuse: Metadata is licensed under CC0, except for email addresses. All metadata is exported via OAI-PMH and can be harvested.


  • Revocation: Content not considered to fall under the scope of the repository will be removed and associated DOIs issued by Orvium revoked. Please signal promptly, ideally no later than 24 hours from upload, any suspected policy violation. Alternatively, content found to already have an external DOI will have the Orvium DOI invalidated and the record updated to indicate the original external DOI. User access may be revoked on violation of Terms of Use.
  • Withdrawal: If the uploaded research object must later be withdrawn, the reason for the withdrawal will be indicated on a tombstone page, which will henceforth be served in its place. Withdrawal is considered an exceptional action, which normally should be requested and fully justified by the original uploader. In any other circumstance reasonable attempts will be made to contact the original uploader to obtain consent. The DOI and the URL of the original object are retained.


  • Versions: Data files are versioned. Records are not versioned. The uploaded data is archived as a Submission Information Package. Derivatives of data files are generated, but original content is never modified. Records can be retracted from public view; however, the data files and record are preserved.
  • Replicas: Data files are kept in multiple replicas in a cloud distributed file system, in multiple availability zones.
  • Retention period: Items will be retained for the lifetime of the repository.
  • Functional preservation: Orvium makes no promises of usability and understandability of deposited objects over time.
  • Fixity and authenticity: All data files are stored along with a MD5 checksum of the file content. Files are regularly checked against their checksums to assure that file content remains constant.
  • Succession plans: In case of closure of the repository, best efforts will be made to integrate all content into suitable alternative institutional and/or subject based repositories.