Scope: All fields of research. All types of research artifacts. Content must not violate privacy or copyright, or breach confidentiality or non-disclosure agreements for data collected from human subjects. 

Eligibility of research data: Research data from any stage of the research data lifecycle is accepted. 

Eligible depositors: Anyone registered with SWITCHaai or SWITCH edu-ID account linked to Geneva higher education institution (including the Geneva University Hospitals, HUG) may create an organizational unit to deposit data. Registered users are allowed to deposit content for which they possess the appropriate rights. 

Ownership: By uploading content, no change of ownership is implied, and no property rights are transferred to Yareta. All uploaded content remains the property of the users prior to submission. 

Data file formats: All file formats are allowed – even those that are not suitable for preservation. A compliance system (in the form of stars) allows “unfriendly formats” to be distinguished from “golden formats”. 

Volume and size limitations: There is no technical limit to the amount of data you may deposit. Any limit depends solely on the pricing. 

Metadata types and sources: All metadata are stored internally in XML-format. Metadata are exported according to the DataCite Metadata Schema. 

Language: For textual items, 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 Metadata form. 

Access to data objects: Files may be deposited in closed, restricted, or openaccess (with the possibility of embargoes as explained further down). 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 HTTPS and OAI-PMH. 

Use and re-use of data objects: Use and re-use are subject to the license chosen by the user under which the data objects were deposited. 

Embargo status: Users may deposit content under an embargo status and provide an 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 automatically become publicly available. 

Restricted Access: Users may deposit restricted files with the ability to share access with others if certain requirements – chosen by user – are met. These files will not be made publicly available, and sharing will only be made possible by the original file approval depositor. 

Metadata access and reuse: Metadata are licensed under CC0. All metadata are exported via OAI-PMH and can be harvested. 

Withdrawal: If the uploaded research object must later be withdrawn, Yareta will indicate the reason for this withdrawal 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 depositor. In any other circumstance reasonable attempts will be made to contact the original depositor to obtain consent. The DOI and the URL of the original object are retained. 

Versions: Metadata are versioned but not Data files. The uploaded Data filesare archived as a Submission Information Package. Derivatives of Data files are generated, but original Data files are never modified. Archives can be retracted from public view; however, the data files and Metadata are preserved. 

Replicas: All data files are stored in the UNIGE data centers in Geneva, Switzerland. Datasets are kept in two replicas on redundant architectures. 

Retention period: Items will be retained for the lifetime indicated upon deposit. 

Functional preservation: UNIGE makes no promises of usability and understandability of deposited objects over time but recommends “golden formats” to increase functional preservation on the very long term. 

Fixity and authenticity: All Data files are stored along with a checksum (small-sized block of dataderived from the datasets for the purpose of detecting errors that may have been introduced during their transmission or storage); different checksum formats are used. File checksums are regularly checked to ensure that the corresponding datasetsremainintact.