Felipe Gomez

Scott B. Weingart

Other URLs relevant to the resource, e.g. ORCID, etc.

URL, ideally landing page, of the resource.

Person/group/body who helped create the resource.

Should be concise and raise interest in the entry. Allows <Link>Markdown</Link> content.

Other URLs relevant to the resource, e.g. code, DOI, etc.

URL pointing to info about the access policy.

The activities you can do with the resource. See <Link></Link>.

Name of the conference where paper was given.

Describes the discipline covered by resource. See <Link></Link>.

Locations where the Resource is offered. See <Link></Link>.

URL to helpdesk for incidents & user requests.

Audience targeted by the resource. See <Link></Link>.

A particular published issue of a journal.

Concept or term related to MP entry. See <Link></Link>.

Language(s) in which a resource is available. See <Link></Link>.

Select license pertaining to resource. See <Link></Link>. If license is unknown, use the "Terms of use" property field to describe the usage terms.

Status of the Resource life-cycle. See <Link></Link>.

Mode of use for the resource. See <Link></Link>.

File format of the linked resource. See <Link></Link>.

Page #s of a resource, separate by commas.

Refine the resource's nature and function. See <Link></Link>.

Links to non-MP materials that are relevant.

Info about performance levels provider expected to deliver.

Standard used by the resource. See <Link></Link>.

Technology Readiness Level of the Resource. See <Link></Link>.

Resource user manual and documentation URL.

Version of the tool or service that is linked.

The volume of a journal or multivolume book.

If you are having trouble with the sign in process, please <ContactLink>contact the SSH Open Marketplace team</ContactLink>.

If you are having trouble with the sign up process, please <ContactLink>contact the SSH Open Marketplace team</ContactLink>.