Access and reuse

• Scope: All research areas. All types of research. Content must not violate any personally identifiable information or copyright, or violate any confidential or non-disclosure of data.
• State of research data: All states are allowed at all stages of the research life cycle.
• Registrant qualification: Anyone can register as a user of epop. All users can save content that they have the appropriate rights to.
• Ownership: Uploading content does not imply ownership change and does not transfer intellectual property rights to KISTI. All uploaded content is the property of the parties prior to submission.
• Data file format: All formats are allowed, including hard-to-retain formats.
• Volume and size limits: The total file size limit per record is 2 GB. For larger files, you can negotiate the quota separately.
• Data Quality: All information is provided "as is". You shall not, and should not cause any damages to, any information provider providing data to Epops and Epops in connection with your use of such information.
• Metadata format and source: All metadata is stored in a relational database table and exported in "Dublin Core" format.
• Language: Hangul is preferred for text items, but all languages are allowed.
• License: You must specify a license for all publicly available files. Licenses for inaccessible files can be described in the description field.

Access and reuse

• Access to data objects: can be registered as open or open after point in time. Access to metadata and data files is provided through standard protocols such as HTTP and OAI-PMH.
• Usage and reuse of data objects: Usage and reuse are subject to the license on which the data objects are deposited.
• Embargo Status: You can deposit, embed, and exit embeds. The repository restricts access to data until the outage period is over. At that point, the content automatically becomes publicly available.
• Restricted access: If certain requirements are met, users can keep restricted files and share access with others. These files are not publicly available and can be shared only with the consent of the depositary of the original file.
• Metadata access and reuse: Except for email addresses, metadata is licensed under CC0. All metadata can be exported and harvested via OAI-PMH.

Delete

• Revocation: Content that is not considered to be in the scope of the repository is deleted, and the DOI issued by Epops is revoked. If you suspect a policy violation within 24 hours after uploading, please let us know immediately. In addition, content that has already been identified as having an external DOI invalidates the Epops DOI and updates the record to indicate the original external DOI. User access may be canceled in violation of the Terms of Use.
• Withdrawal: If an uploaded research object needs to be withdrawn at a later time, the reason is shown on the tombstone page, and the page will then be delivered to the destination page. Withdrawal is considered an exceptional act and generally requires the originally deposited user to request and justify. In other circumstances, a legal process is attempted to contact the original donor and obtain consent. The original object's DOI and URL are preserved.

Conservation period

• Version: The version of the data file is specified. There is no record version. The uploaded data is kept in the submission information package. A derivative of the data file is created, but the original content is not modified. You can withdraw a record from a public record. However, data files and records are preserved.
• Replicas: All data files are stored in KISTI (usually in action). Data files are kept on multiple copies of the distributed file system and are backed up at night.
• Retention period: The item is retained for the lifetime of KISTI. There are currently defined programs for at least 10 years.
• Function Preservation: Epops does not guarantee the availability and comprehensibility of deposited objects over time.
• File retention: Data files and metadata are backed up at night and replicated to multiple copies on an online system.
• Accuracy and reliability: All data files are stored with the MD5 checksum of the file contents. Files are regularly checked against the checksum so that the contents of the file remain constant.
• Succession planning: When you close the repository, we will do our best to integrate everything into the appropriate alternate or topic-based repository.