Q: Descriptive documentation of how "things" work together and depend on each other in MISO?

[sklages]

Although the documentation of each part of MISO is quite complete and good, there is no (descriptive) "connection" between "things".
It is hard, if not impossible, to follow the path of a sample[1] should follow all the way from receiving to its final destiny as part of a library dilution ..

We are using MISO productively since 2013 or so .. with only few changes in our (MISO's) workflow. But over the time, especially when you took over the development, there were many features, options and methods added to the system, which is really great and which I indeed appreciate.

We are setting up a new, fresh MISO system, from the very beginning, probably "plain sample mode", from zero, scratch .. that's a chance to optimize things, in MISO, in the lab workflow possibly.

We can read what a "Pool Order", "Sequencing Order", "Workset" or a "Requisition" is, the description is formal, but good.
But it is hard to see where and how these "things" fit best into the way of processing a sample in MISO to use it efficiently.
How these things work together and depend on each other.

Do you have such documentation available for external users?

Most useful would be a flowchart showing/describing the path of a sample all the way through MISO.

A textual example would be just as good. Or both :-)

thanks

[1] sample = tissue, DNA/RNA, cells, other input material

[djcooke]

We're probably not going to get to it for a while, but I agree this would be useful documentation and something we should work on at some point. Flowcharts would be nice for illustrating how these things fit together in processes. We'll keep this issue open as a request for all of that.

In the meantime, I'm including a bit of general info on each of these things below. As you may have guessed, all of these things are made to be optional, so you may choose whether they would be useful to you. Most of them are used as communication tools. Please let us know if you have any other specific questions.

• Requisitions are used to track the purpose that some samples were received for via an assay. The assay specifies a number of tests and metrics that may be used for reporting (mainly in other systems via Pinery, but some of this will be in MISO at some point as well). The requisition page also lets you track the progress of this, showing all of the receipts (samples), extractions (detailed sample model only), library preps, and sequencing that have been completed.
• Pool orders are useful if you have one person/team deciding how pools should be created, and another person/team actually creating the pools
• Sequencing orders are useful if you want to keep track of pools that are ready for sequencing - maybe for handoff to a separate sequencing team
• Worksets are useful for grouping items for any reason. We often use them as work queues
• You didn't mention transfers, but they're another major addition we made. These are good for tracking chain of custody and notifying recipients when items have been transferred to them