Infra Finder expression of interest form

Need help using Jotform? Consult our orientation documentation.

Looking for definitions and examples for the questions in this form? Consult our definitions and guidance.

Need a break at any time? Scroll to the bottom of the page and click "Save" to save your progress and return later.
Overview
Need help?

Consult our definitions and examples.
Contact name*

Your first nameYour last name
Contact email*
Your email address formatted as example@example.com
Solution name*
A solution is a tool, product, or infrastructure component. In some cases, the solution may be the same as the provider.
Provider name*
A provider is a formal or informal organization responsible for running a solution. In some cases, the provider may be the same as the solution.
Website*
Primary web presence of the solution. URL should start with https://.
Public contact information*
Contact form or email address potential adopters can use to get additional information (https://www.example.com OR example@email.com)
Solution summary*

An overview of the functions of the solution and its role in supporting research.0/1000
Launch year*
Year that the solution was first made available to users.
Location
Location of incorporation of the solution or provider or geographical area of primary activity.
Hosting and software as a service (SaaS) options
Indication of whether the software can be hosted, deployed, configured, maintained, or otherwise serviced by a vendor, whether the solution provider or a third party.
Link to vendor registry or SaaS description*
Link to a public registry of approved third party vendors or to a description of SaaS options available. Links should start with https://.
Eligibility
Help us determine your elibility for inclusion in this iteration of Infra Finder. Inclusion criteria are subject to change.
Need help?

Consult our definitions and examples.
Your solution may be eligible for inclusion in Infra Finder if it is in active use as a service, protocol, standard or software that the academic ecosystem needs in order to perform its functions throughout the research lifecycle.

For your solution, please provide information about the following:
Solution category describes the function(s) the solution is primarily designed for, or how adopters primarily use the solution. Select up to three (3). Refer to our solution category definitions for more details.
Solution category*

Annotations systemArchive information management systemAuthoring toolComputing frameworkComputing libraryData management planning tool or serviceDigital asset management systemDigital library, collection or exhibit platformDigital preservation serviceDigital preservation systemDigital preservation tool:Discovery systemFederated identity or authentication managementFormat conversion tool or serviceIndex or directoryInformal scholarly communicationsMedia viewer/playerOpen access or subscription management toolOpen access policy information compilationOpen scholarly datasetPeer review systemPersistent identifier servicePublishing systemRepository serviceRepository softwareResearch profiling systemResearch software communityStandard, specification or protocolSubmissions systemWeb archiving system
Maintenance status*
The solution's maintenance status. Evidence of active maintenance may include regular commits and issue resolutions in a GitHub repository, activity in community and support forums.
Technology readiness level*
The solution's readiness for broad adoption, adapted from the framework developed by the Horizon 2020 project.
We are currently prioritizing services that meet one or more of the following criteria. Please share information for as many criteria as are relevant to your service.
Which of the following describe your solution? Select all that apply.

Meets the definition of open source software (OSS)Primarily or exclusively distributes openly licensed (open access) contentIs free to use by anyone (free of charge or other restrictions)Is community-governed and is transparent in its operations and financesIs operated by a non-profit or non-commercial entity
Open code repository*
Does the solution maintain a public repository where the full source code is stored and shared openly, allowing anyone to access, inspect, modify, or contribute to it? Code repositories that only contain plug-ins or community contributions, or that lack critical components for running the solution do not meet the criteria for inclusion.
Link to open code repository*
Provide a public link to your primary code repository. Links should start with https://.
Open code license*
Indication of whether the solution applies a standard open software license to its primary source code.
Link to code license*
Link to the code license attached to the tool's primary source code repository. Links should start with https://.
What types of code license are attached to the tool's primary source code repository?*

Apache License, Version 2.0MIT LicenseBSD licensesUnlicenseGNU General Public License (GPL)NoneOther
What licenses do you use, require, or support?*

Traditional copyrightCreative commons licensesRightsstatement.org licensesOther
Transparent pricing*
For solutions that charge a fee, do you make available public pricing documentation in a way that allows users to meaningfully evaluate the costs associated with using the solution?
Pricing information*
A public link to pricing or fees. Links should start with https://.
Governance structure*
Availability of a public description of how the solution is organized and managed, such as the roles, responsibilities, decision-making, and communication mechanisms of the stakeholders.
Link to governance structure*
Public description of how the solution is organized and managed, such as the roles, responsibilities, decision-making, and communication mechanisms of the stakeholders. Links should start with https://.
Board structure
Structure of the solution or provider's governing board.
List of board members*
Link to a list of the organization's current board members. Links should start with https://.
Community governance type
Public documentation of a community-driven governance structure, including evidence of community representation in governing bodies.
Commitment to community engagement*
Public stated interest in and evidence of available resources for engaging with the solution's stakeholder community in a meaningful way. This may include staff explicitly tasked with community engagement, evidence of regular community involvement in major decisions, and community-driven governance.
Community engagement activities*

Staff roles with responsibility for community engagementMailing lists and discussion forums (including Slack)Social mediaBlogsWebinars and trainingCommunity callsAnnual meetingsInterest, working, user, or advisory groupsVolunteer or ambassador networkUser researchDevelopment sprintsConference participationOther
Business form*
Non-profit status*
Does the solution or provider have a specific non-profit designation or status in the country of incorporation?
What's your primary reason for wanting your data included in Infra Finder?

I want our open infrastructure or service to be discovered by potential end users / adoptersI want to have a quick reference that I can share with end users of our open infrastructure or serviceI want to see how our open infrastructure or service compares to those already listedOther organizations we work with are listed hereOther
How did you hear about Infra Finder?

IOI social mediaIOI newsletterReferred by another open infrastructureFrom a conference (please state which one)Word of mouth
Not ready to submit?

Click "Save" to save your progress and return later.
Consent
By submitting this intake form you acknowledge that you have read, and on behalf of the applicable provider, agree that IOI may use the information you've submitted below in accordance with IOI's Terms & Conditions and Privacy Policy.
Should be Empty:

Overview

Need help?

Eligibility

Need help?

Not ready to submit?

Consent