Team:Michigan Software/Improve

Improvements

ProtoMetrics

     ProtoCat is meant to enable lab researchers to get feedback on their lab procedures; in order to improve efficiency or gather feedback. But how can they quantify which version of a protocol is better? What if a researcher wants to gather feedback about a specific step, or specific product? Ask for the calibration of the equipment that other people are using? And even if they can get it in the comments, how will they get that information in a readily accessible and usable form? This need gave rise to ProtoMetrics, our way to allow researchers to get quantitative metrics on their protocols.

     ProtoMetrics allows users to specify three types of questions: Text, Numeric, or Polls. Text and Numeric are relatively straightforward; the former asks for a text response (ex: describe the resulting solution), whereas the latter is for strictly numeric responses (ex: How many grams of product were you able to produce?). Polls allow for a respondent to choose from a selection of responses, which can be used for specific equipment calibration. Once the users have submitted the responses, the publisher of the protocol can download the results in a Comma Seperated Value (csv) file for easy import into Excel, MATLAB, or a similar analysis too.

ProtoChat

Describe ProtoChat Here




Protocols.io Import Tool

     Find out more about this import tool here.

Visual Protocol History

     ProtoCat enables users to 'version control' their protocols; anyone can create a variant of a protocol and make modifications as they see fit. However, once multiple revisions are made, and the subsequent tree of protocol revisions gets unruly, it can be quite difficult to figure out which version one should be using. In ProtoCat 3.0, the only way to navigate through a set of protocols was to do it one level at a time, which was incredibly arduous and hard to keep track of. To address this issue, we have created a way for a user to view the history of protocols visually to make navigating to the best version of a protocol as efficient as possible.

     Protocol nodes are color coded from red (1 star) to green (5 star), and are transparent should they be hidden from search. These visual cues, in addition to the tree diagram, makes finding a well-written, tested protocol much easier. On hover, a user can see the title, author, and change log of that specific version of a protocol.

Favorite Protocols


     ProtoCat allows users to find protocols for a variety of disciplines, and gives easy access through an online catalog. However, a Primary Investigator may want his/her students to only use specific protocols that are, for example, optimized to the equipment in the lab. This PI could send everyone in the lab a link to the protocol that should be used, but what if a new version of the protocol becomes available? In addition, every time the PI finds a new protocol, it needs to be sent out to everyone in the lab. To address this, we have built a favorites system into ProtoCat, which allows users to signify a select set of "favorite protocols". Now, the PI only needs to update his favorites, and then when the students check the favorites section they'll find the new protocol.

Group Accounts


ProtoCat 3.0 enabled users have accounts, with which they can establish an identity in the ProtoCat community through uploading protocols, leaving comments, and rating other users' protocols. In ProtoCat 4.0, we've expanded these capabilities to include favorite protocols as well. However, what about organizations? Suppose we had the head of a lab who also works with a company? It would be difficult to separate the protocols just at the user level if the user simply favorites the protocols for his/her work; the distinction needs to be done at an organizational level. So, 'Group Accounts' were added to ProtoCat, allowing for favorite protocols at the lab (instead of individual researcher) level.

Improved Security

Describe Security Upgrades here

Misc Improvements

Improved Search Algorithm, Scalable Server Infrastructure. Adopted Pair Programming Techniques