Difference between revisions of "Team:Michigan Software/HP/Silver"
| Line 47: | Line 47: | ||
<div> | <div> | ||
| − | <h3>Protocol | + | <h3>Protocol Model</h3> |
<p>Research we did into what it takes to make a protocol</p> | <p>Research we did into what it takes to make a protocol</p> | ||
| − | <h3>OpenWetWare | + | <h3>OpenWetWare</h3> |
| − | <p> | + | <p>Our protocol database is not the only one out there. OpenWetWare and protocols.io are some of the most popular alternatives. Since there are so many different databases, our team wanted to find a way to ensure that no matter which database someone decides to use, they can upload their protocol to all of them the same way. We reached out to OpenWetWare and began discussing how to standardize the file format of protocol to be uploaded. Our format is based on the JSON format, and we gave them an example of one of our protocols to begin the collaboration. The first steps were taken to build a cooperative relationship and create a standard protocol that will help make protocols even easier to use, test, review, and design.</p> |
</div> | </div> | ||
Revision as of 20:37, 15 October 2016
Michigan Software Team
Protocat 3.0 - Human Practices
Protocol Model
Research we did into what it takes to make a protocol
OpenWetWare
Our protocol database is not the only one out there. OpenWetWare and protocols.io are some of the most popular alternatives. Since there are so many different databases, our team wanted to find a way to ensure that no matter which database someone decides to use, they can upload their protocol to all of them the same way. We reached out to OpenWetWare and began discussing how to standardize the file format of protocol to be uploaded. Our format is based on the JSON format, and we gave them an example of one of our protocols to begin the collaboration. The first steps were taken to build a cooperative relationship and create a standard protocol that will help make protocols even easier to use, test, review, and design.
