Yareta

General Policies

Yareta-h-v2-01.png

v. 1.0

Content

  • 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.
  • Status of research data: Any status is accepted, from any stage of the research lifecycle.
  • Eligible depositors: Anyone registered as staff of the Higher Education Institutions of the Geneva Canton 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 UNIGE. All uploaded content remains the property of the parties prior to submission.
  • Data file formats: All formats are allowed - even preservation unfriendly. A qualification system (under the form of stars) provides indication from “unfriendly formats” to “golden formats”, guaranteed for long-term preservation.
  • Volume and size limitations: There is no size limit, but a fee applies beyond 50GB allocated to an organizational unit.
  • Metadata types and sources: All metadata is stored internally in XML-format. Metadata is exported according to the DataCite Metadata Schema.
  • Language: For textual items, French and English are 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, restricted, 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. All metadata is exported via OAI-PMH and can be harvested.

Removal

  • 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.

Longevity

  • Versions: Data files are not 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: All data files are stored in UNIGE Data Centers, in Geneva Canton. Datasets are kept in two replicas on redundant architectures.
  • Retention period: Items will be retained for the lifetime indicated upon deposit.
  • Functional preservation: Yareta makes no promises of usability and understandability of deposited objects over time, but recommend “golden formats” to increases functional preservation on the very long term.
  • Fixity and authenticity: All data files are stored along with a checksum of the file content; different checksum formats are used. Files are regularly checked against their checksums to assure that file content remains constant.