Creation RDMC Process

This page provides step-by-step instructions for creating and sealing a container within the RDMC platform. Each step guides you through the required actions, from initializing your artifact to signing and sealing the final container.

Flowchart for the process to create and seal the container

Figure: RDMC Creation Process

Process Overview

The process begins with the user creating the RDMC with RDMC Title and Artifact name with appropriate access level (Public or Restricted or Private). This phase consists of three key components:

  • The user initiates the process by selecting the specific type of resource to be uploaded. Resource types include files, folders, software applications, RDMC resources, and URL/DOI links.

  • The user proceeds to upload the resource. Previously uploaded resources can be permanently deleted at this stage to ensure data accuracy and relevance.

  • The platform stores the resource once uploaded and validates it. If the resource is valid, the platform stores the uploaded resource; otherwise, an error message is displayed.

  • Users can add additional descriptions about individual artifacts to provide context.

  • Users can review the complete artifact summary and have the opportunity to archive the artifact to external platforms such as Zenodo and Dataverse.

  • The user initiates the definition process of the Reusable Execution Environment (REE) by specifying a strategy and selecting relevant resources.

  • The platform provides status information about the process to the user.

  • The user monitors the process until completion and then specifies a title for the execution environment.

  • The platform adds the REE as a new resource with the given title to the RDMC.

Activity diagram of REE definition

Figure: Activity diagram of REE definition

  • The user can download the manifest file in a .rdmc format with some fields pre-filled based on the selected resources.

  • The user uploads the manifest file if available, or completes the provided questionnaires to generate the metadata.

  • The platform verifies the metadata from the uploaded manifest file or questionnaire responses and automatically generates the manifest file accordingly.

  • The user can preview the resources they uploaded and return to the Artifact Initialization page to make any updates.

  • The user reviews the generated manifest file and makes any necessary changes.

  • The user can download the manifest file for final review before submission.

  • The user accepts the terms and conditions to seal the container.

  • The platform finalizes the sealing process to create the sealed container.