Comments (10)
Just to be clear, I am referring to:
1 / study | Lab name
1 / study | Contact information (data collection)
1 / study | Contact information (data deposition)
1 / study | Lab address
from airr-standards.
My understanding was that the "lab" is related to the data submitter/contact person:
As you said
"the contact info for the data collection and data deposition are contact points within the lab for key aspects of the work"
from airr-standards.
I'm not sure this completely answers the question, but for NCBI submission at least the study <-> BioProject. In a BioProject submission, the first screen has submitter information. This would correspond to the "Contact information (data deposition" and "Lab address" fields, though note that NCBI does not have any field that corresponds explicitly to "Lab name".
Later on the submission process, there is the ability to indicate a data provider with the help saying "indicate the data provider (data submitter) if it is someone other than the submitting organization or consortium. For example, a sequencing center or a DACC." It would seem you could specify this scenario with "Contact information (data collection)". In the NCBI form, this is a free text field, plus an additional field to provide a URL.
from airr-standards.
Could we collapse these 4 fields into 2 (data collection & data deposition), which both contain:
- PoC name
- PoC email
- department
- institution
- full address
This way we would be most flexible, e.g. if a consortium has a centralized facility for data submission that could belong to a different institution.
from airr-standards.
I assume that the intent is that through these fields we are providing the principal contact point for a study (there is no other mechanism for this at the moment). If so, which one of these is the principal contact. Or should there be three, the principal lab/contact person (the "corresponding author" so to speak), the data collection lab, and the data submission lab? In the iReceptor world, we have a principal lab and contact, but not separate information for data collection and data submission. I am trying to figure out which is the principal contact point for the study from the current fields. This is unclear to me at the moment.
iReceptor allows you to group/aggregate study/data views based on lab. For example, you could look at all of the studies where the "Kleinstein Lab" was the "data collector" (assuming there was such data in a repository). I am trying to determine which "lab" entity in the Minimal Standards our principal lab aggregation should relate to.
Should there be another group of entities in the Minimal Standard about being the principal contact for the study itself (as opposed to data collection and data submission which could be different). Or is what we have enough?
Brian
from airr-standards.
The "collecting" lab / PoC would be the principal contact for the study. The "submitting" PoC is mainly provided to quickly resolve technical issues with the submission itself.
IIRC we discussed the trichotomy (corresponding/collecting/submitting) you mentioned, but decided that for nearly all purposes (sample requests, legal compliance, etc.) "collecting" could be considered a subcontractor of "corresponding", so we did not include it. In case there is any scenario in which this would be important, we should discuss again.
from airr-standards.
OK, this seems more clear...
One other question - the standard states that the "Contact information (data collection)" field has a content type of "RFC6530-compliant email address". This seems restrictive, in that there is no ability to put something like "Brian Corrie ([email protected])" as the contact information. Was the intent of this field to enforce it to be an email address and only an email address? That is how I interpret the "content type" as it stands now.
from airr-standards.
I think the idea here was that Lab name
, Lab address
and Contact information (data collection)
would all refer to the same group/institution, so that in the contact field we wanted to make sure that there is a valid e-mail address on file (assumed to belong to the PI). If we go for the dichotomy (collecting/submitting) we discussed, then each of the two fields would become free text again, containing the five items listed above.
from airr-standards.
The definitions have been amended and slightly changed in 8f63c1e, but otherwise the four fields are still in v0.1. I will close this issue, if you want to have it on the MiAIRR v2 change list, please reopen it.
from airr-standards.
I have a vague memory that not all possible contacts were included in the minimal standards template because of 'the minimalism'
from airr-standards.
Related Issues (20)
- Do we need adc_keywords HOT 1
- ADC API versions are confusing, and not right for AIRR v1.4.1 and v1.5.0 releases HOT 7
- R library validation does not handle properties with ontologies correctly
- deprecate OpenAPI 2 spec for ADC API? HOT 4
- Re-visit implementation decisions around `Cell` object HOT 30
- Add a "nonphysical" keyword to Rearrangement and Cell HOT 7
- reference libraries do not provide access to CURIEMap and InformationProvider for CURIE resolution HOT 2
- AIRR could use a specification of mutations counts/frequencies and maybe aggregates HOT 1
- specification of AA physiochemical properties of the CDR3
- Add consistency checks to make sure unit test data are identical between R and python HOT 3
- Remove "experimental" designation from Alignment schema? HOT 1
- Consider new event model for AIRR
- Add verification for Manifest to AIRR libraries
- How do I capture known antigen/epitope reactivity to AIRR objects (Rearrangement/Cell) HOT 18
- Validation of logical fields in R
- version number in spec files is not correct for 1.5.x HOT 20
- JavaScript Errors
- python error when using airr.read_rearrangement with gzip file HOT 1
- Incompatibility with Python 3.12 HOT 6
- Inconsistency in required elements and properties in `RearrangedSequence` and `UnrearrangedSequence`
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 airr-standards.