Comments (6)
Adding this to this sprint as we need to determine custom attributes for NCBI submission testing.
from nmdc-schema.
Comprehensive example from NCBI (Submission, BioProject, BioSample, SRA): https://www.ncbi.nlm.nih.gov/viewvc/v1/trunk/submit/public-docs/sra/samples/sra.submission.bs.bp.run.xml?view=co
from nmdc-schema.
Mechanism by which we say who owns the Submission:
<Submission>
<Description>
<Comment>BP(1.0)+BS(1.0)+SRA</Comment>
<Organization role="owner" type="institute">
<Name>Institute of Biology</Name>
<Contact email="[email protected]">
<Name>
<First>jane</First>
<Last>doe</Last>
</Name>
</Contact>
</Organization>
<Hold release_date="2015-10-21"/>
</Description>
from nmdc-schema.
- Where does "ownership" appear in the NCBI Submission Schema (or any of its constituents)? Look in the XSDs.
- which are required?
- which optional ones do we want to fill in?
- do we already have slots that capture all of that?
The NMDC schema has has_credit_association
for Study and processing_institution
for PlannedProcess
.
- Submission XSD: https://www.ncbi.nlm.nih.gov/viewvc/v1/trunk/submit/public-docs/common/submission.xsd?view=co
- BioProject XSD: https://www.ncbi.nlm.nih.gov/viewvc/v1/trunk/submit/public-docs/bioproject/bioproject.xsd?view=co
- BioSample XSD: https://www.ncbi.nlm.nih.gov/viewvc/v1/trunk/submit/public-docs/biosample/biosample.xsd?view=co
from nmdc-schema.
From the Submission XSD:
<xs:element name="Organization" minOccurs="1" maxOccurs="unbounded" type="typeOrganization">
<xs:annotation>
<xs:documentation>
Organization(s) involved into the submission.
One organization is the owner of submission data which is identified by attribute "role"
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:attribute name="role" use="optional">
<xs:annotation>
<xs:documentation>
Role of the ogranization in submission - owner of the data or just a participant.
It is expected that there is one owner of the submission data.
</xs:documentation>
</xs:annotation>
<xs:simpleType>
<xs:restriction base="xs:string">
<xs:enumeration value="owner"/>
<xs:enumeration value="participant"/>
</xs:restriction>
</xs:simpleType>
</xs:attribute>
<xs:complexType name="typeOrganization">
from nmdc-schema.
@turbomam to contact John at NCBI and check assumptions about the Organization
and Submitter
nodes in the NCBI submission schema
from nmdc-schema.
Related Issues (20)
- Remodel class that aggregates steps of `WorkflowExecution` for easier schema traversal HOT 1
- `has_input`, `has_output`, and `has_process_parts` slots on `ProtocolExecution` need pattern constraints
- `berkeley-schema-fy24`: Facilitate access to `nmdc_materialized_patterns` schema via PyPI package HOT 2
- Delete Class WorkflowChain in Berkeley schema HOT 2
- `berkeley-schema-fy24`: Implement super migrator that runs all partial migrators in correct order HOT 1
- Find a home for these comments taken from `src/scripts/report_biosamples_per_study.py`
- check if classes associated with `alternative_identifiers` can use ANY `alternative_identifiers` HOT 5
- Migrations: Make it easier to test migrators against a Mongo database
- `berkeley-schema-fy24`: Update migrators to account for `WorkflowChain` class being removed
- Publish schema to PyPI via GitHub Release `v10.5.4` HOT 1
- Migrations: Implement "no op" migrator from `v10.4.0` to `v10.5.4`
- `berkeley-schema-fy24`: Some migrators use incorrect collection name (instead of `mags_set`)
- Rename branches to eliminate Berkeley commits from `main` HOT 6
- 2024-06-18 `id` pattern validation summaries and SPARQL-based referential integrity checks on MongoDB contents with and without migration HOT 6
- Facilitate access to `nmdc_materialized_patterns` schema variant via PyPI package HOT 2
- produce a nmdc-schema YAML artifact with deprecated elements included HOT 1
- Remove WorkflowExeuctionActivity as a range for Database slot activity_set
- tighter pattern constraint on was_generated_by
- Migrator: Update `migrator_from_10_3_0_to_10_4_0.py` so it also updates `was_generated_by` values HOT 1
- Docker Compose shows warning saying `version` (specifier) is obsolete
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 nmdc-schema.