Comments (9)
There is already a "has_physical_specimen" field in the required_sample_info table; does that suffice, or do we also need a "has_dna" field? Is this a question for the wet lab folks?
from qiita.
Need both
On Sep 15, 2014, at 1:42 PM, "adamrp" <[email protected]mailto:[email protected]> wrote:
There is already a "has_physical_specimen" field in the required_sample_info table; does that suffice, or do we also need a "has_dna" field? Is this a question for the wet lab folks?
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/5#issuecomment-55646848.
from qiita.
We also need an easy way for people to update that field otherwise it could
easily get out of sync
Need both
On Sep 15, 2014, at 1:42 PM, "adamrp" <[email protected]<mailto:
[email protected]>> wrote:
There is already a "has_physical_specimen" field in the
required_sample_info table; does that suffice, or do we also need a
"has_dna" field? Is this a question for the wet lab folks?
—
Reply to this email directly or view it on GitHub<
https://github.com/biocore/qiita/issues/5#issuecomment-55646848>.
—
Reply to this email directly or view it on GitHub
#5 (comment).
from qiita.
This could be tracked in the mapping file we receive from the wetlab so that it is available for upload to prep. Problems occur when subsets of study samples are used for e.g. primer testing or retrieved for collaborations e.g. family study samples for Blastocystis collaboration. We will have to estimate remaining dna volume (some is lost in aliquoting repeatedly).
from qiita.
In the wetlab there should be a log of samples available - primary sample and primary dna (we usually discard the amplicons. We should also track the freezer location/inventory.
from qiita.
How do we want to deal with this? These are not required fields for any of the templates and it sounds more like a standard that we want to impose in the template generation (perhaps in the weblab) and not in Qiita.
from qiita.
I think this should be move to the labadmin project - qiita is not a labadmin site to deal how our freezers are organized.
from qiita.
This will be fairly easy to track for studies sequenced by us in the wetlab
but will not be generally available. Right now I usually assume that the
physical specimen is not available unless it is AGP (potentially available)
or a study I am familiar with (like Jess M soils) where I know there is
physical specimen. Many times we have to return the specimen to the
collaborator and have no knowledge of what happens to it.
On Mon, Oct 12, 2015 at 9:09 AM, Antonio Gonzalez [email protected]
wrote:
How do we want to deal with this? These are not required fields for any of
the templates and it sounds more like a standard that we want to impose in
the template generation (perhaps in the weblab) and not in Qiita.—
Reply to this email directly or view it on GitHub
#5 (comment).
Gail Ackermann
Knight Lab
UCSD
[email protected] [email protected]
from qiita.
From your replies it sounds like we can close as it's not longer within the scope of the template validations. Please, reopen if you think otherwise.
from qiita.
Related Issues (20)
- sample_sheets and pre-prep files get no newlines/tabs in Firefox
- missing `limits.h` during install HOT 1
- Setting up qiita processing instance HOT 3
- example for publication HOT 3
- nginx missing websocket proxy
- no commands listed HOT 3
- IndexError: list index out of range for /analysis/dflt/sumary/ HOT 4
- analyses can't be created using archived artifacts
- how to activate private plugins? HOT 3
- add settings table to DB schema HOT 1
- Allow admins to define a workflow via an existing processing. HOT 4
- register Artefact_types HOT 4
- `make env --download-reference` inserting into non existing table? HOT 4
- rm get_reference_fp and ontology download deprecated functionality HOT 4
- hard coded emails should be part of the configuration HOT 1
- docstring: `name` listed twice
- track time a new user account was requested HOT 1
- concurrency with deblur using `PLUGIN_LAUNCHER = qiita-plugin-launcher` HOT 3
- dbBact's wordclouds for Qiita HOT 2
- qiimp doesn't produce compliant templates
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from qiita.