Step 3: Container Metadata

This is the third step of the RDMC Creation Workflow. You come here after Step 2: Execution Environment. Here you describe the container as a whole: what it is about, who contributed, and under which license it is shared. This information is stored in the manifest file. If you want to know what the manifest file contains, see Manifest File.

  • You can download the manifest file, which comes with some pre-filled information such as the container title and artifact details. You then complete the remaining fields and upload the file using the upload option.

  • You can validate the manifest file using the RDMC JSON schema validator.

  • Additional fields are available for contributor details, including First Name, Last Name, Affiliation, ORCID, and Role. You can save each contributor and add more as needed, or click Save when finished.

  • If you want to add more contributors, click Save and add another.

  • Instead of uploading a manifest file, you can also fill in the information manually (or edit the fields after uploading). After you click Save, all details are stored. Until the information is saved, a validation message appears on the right side.

Note

  • You can update or modify the information even after submission.

  • A success message appears once the information is saved correctly. If errors occur or duplicate answers are submitted, an alert message is displayed.

Multiple Licenses

  • Software containers may require multiple licenses because components, libraries, or tools included in them often have distinct licensing terms. This ensures legal compliance and usage flexibility.

  • For example, a container used for software development could include:

    • Core framework under the Apache 2.0 license

    • Third-party libraries under MIT and BSD licenses

    • Proprietary plugins or modules under a commercial license

  • Each license must be declared and comply with the terms specific to that software component.

  • Multiple licenses may exist due to varying legal requirements, a mix of open-source and commercial models, or different dependencies.

  • You should document all licenses clearly and ensure compatibility between different licenses applied to the container.

Manifest Download and Upload

Figure: Manifest File Download and Upload


Manifest Validation

Figure: Validate Manifest File


Contributor Information

Figure: Contributor Information