v1.0.0 Implementation Tracking #102
Closed
claymcleod
started this conversation in
API Design Discussion
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
This discussion represents the progress that each federation member is making in implementing v1.0.0 of the API specification. Members are expected to edit this post for their respective implementations to report progress.
Kids First (Children's Hospital of Philadelphia)
Subjects
GET /subject
).per_page
andpage
support.GET /subject/{organization}/{namespace}/{name}
).GET /subject/by/{field}/count
).GET /subject/summary
).Samples
GET /sample
).per_page
andpage
support.GET /sample/{organization}/{namespace}/{name}
).GET /sample/by/{field}/count
).GET /sample/summary
).Files
GET /file
).per_page
andpage
support.GET /file/{organization}/{namespace}/{name}
).GET /file/by/{field}/count
).GET /file/summary
).Metadata
GET /metadata/fields/subject
).harmonized: true
.path
pointing to the right location (e.g.,disease_phase
—notmetadata.disease_phase
).wiki_url
pointing to the wiki (e.g.,https://github.com/CBIIT/ccdi-federation-api/wiki/Sample-Metadata-Fields#disease_phase
)standard
has both the name of the standard (e.g.,caDSR CDE 12217251 v1.00
) and the backing URL for the standard (e.g.,https://cadsr.cancer.gov/onedata/dmdirect/NIH/NCI/CO/CDEDD?filter=CDEDD.ITEM_ID=12217251%20and%20ver_nr=1
).harmonized: false
.name
.path
pointing to the right location (e.g.,unharmonized.foobar
—notmetadata.unharmonized.foobar
).url
,description
or both that describe the metadata field. Be as specific as possible, don't link to a general documentation page (linking within a particular documentation page where a metadata element's definition can be easily located is okay).Namespaces
GET /namespace
).GET /namespace/{organization}/{namespace}
).Organizations
GET /organization
).GET /organization/{name}
).Information
GET /info
).Other
v1
instead ofv0
.PCDC (University of Chicago)
Subjects
GET /subject
).per_page
andpage
support.GET /subject/{organization}/{namespace}/{name}
).GET /subject/by/{field}/count
).GET /subject/summary
).Samples - Not supported
GET /sample
).per_page
andpage
support.GET /sample/{organization}/{namespace}/{name}
).GET /sample/by/{field}/count
).GET /sample/summary
).Files - Not Supported
GET /file
).per_page
andpage
support.GET /file/{organization}/{namespace}/{name}
).GET /file/by/{field}/count
).GET /file/summary
).Metadata
GET /metadata/fields/subject
).harmonized: true
.path
pointing to the right location (e.g.,disease_phase
—notmetadata.disease_phase
).wiki_url
pointing to the wiki (e.g.,https://github.com/CBIIT/ccdi-federation-api/wiki/Sample-Metadata-Fields#disease_phase
)standard
has both the name of the standard (e.g.,caDSR CDE 12217251 v1.00
) and the backing URL for the standard (e.g.,https://cadsr.cancer.gov/onedata/dmdirect/NIH/NCI/CO/CDEDD?filter=CDEDD.ITEM_ID=12217251%20and%20ver_nr=1
).harmonized: false
.name
.path
pointing to the right location (e.g.,unharmonized.foobar
—notmetadata.unharmonized.foobar
).url
,description
or both that describe the metadata field. Be as specific as possible, don't link to a general documentation page (linking within a particular documentation page where a metadata element's definition can be easily located is okay).Namespaces
GET /namespace
).GET /namespace/{organization}/{namespace}
).Organizations
GET /organization
).GET /organization/{name}
).Information
GET /info
).Other
v1
instead ofv0
.St. Jude Cloud (St. Jude Children's Research Hospital)
Subjects
GET /subject
).per_page
andpage
support.GET /subject/{organization}/{namespace}/{name}
).GET /subject/by/{field}/count
).GET /subject/summary
).Samples
GET /sample
).per_page
andpage
support.GET /sample/{organization}/{namespace}/{name}
).GET /sample/by/{field}/count
).GET /sample/summary
).Files
GET /file
).per_page
andpage
support.GET /file/{organization}/{namespace}/{name}
).GET /file/by/{field}/count
).GET /file/summary
).Metadata
GET /metadata/fields/subject
).harmonized: true
.path
pointing to the right location (e.g.,disease_phase
—notmetadata.disease_phase
).wiki_url
pointing to the wiki (e.g.,https://github.com/CBIIT/ccdi-federation-api/wiki/Sample-Metadata-Fields#disease_phase
)standard
has both the name of the standard (e.g.,caDSR CDE 12217251 v1.00
) and the backing URL for the standard (e.g.,https://cadsr.cancer.gov/onedata/dmdirect/NIH/NCI/CO/CDEDD?filter=CDEDD.ITEM_ID=12217251%20and%20ver_nr=1
).harmonized: false
.name
.path
pointing to the right location (e.g.,unharmonized.foobar
—notmetadata.unharmonized.foobar
).url
,description
or both that describe the metadata field. Be as specific as possible, don't link to a general documentation page (linking within a particular documentation page where a metadata element's definition can be easily located is okay).Namespaces
GET /namespace
).GET /namespace/{organization}/{namespace}
).Organizations
GET /organization
).GET /organization/{name}
).Information
GET /info
).Other
v1
instead ofv0
.Treehouse (UCSC)
Subjects
GET /subject
).per_page
andpage
support.GET /subject/{organization}/{namespace}/{name}
).GET /subject/by/{field}/count
).GET /subject/summary
).Samples
GET /sample
).per_page
andpage
support.GET /sample/{organization}/{namespace}/{name}
).GET /sample/by/{field}/count
).GET /sample/summary
).Files
GET /file
).per_page
andpage
support.[ ] With functional quick filtering parameters for any unharmonized keys (only if you have unharmonized metadata).Treehouse has no unharmonized file metadata. -ETK 5/28[ ] Error responses for missing data (404, only if you can't share data for files for some reason or if you don't have any).Treehouse has no missing files data. -ETK 5/28GET /file/{organization}/{namespace}/{name}
).GET /file/by/{field}/count
).[ ] Unharmonized fields support.Treehouse has no unharmonized file fields. -ETK 5/28GET /file/summary
).Metadata
GET /metadata/fields/subject
).harmonized: true
.path
pointing to the right location (e.g.,disease_phase
—notmetadata.disease_phase
).wiki_url
pointing to the wiki (e.g.,https://github.com/CBIIT/ccdi-federation-api/wiki/Sample-Metadata-Fields#disease_phase
)standard
has both the name of the standard (e.g.,caDSR CDE 12217251 v1.00
) and the backing URL for the standard (e.g.,https://cadsr.cancer.gov/onedata/dmdirect/NIH/NCI/CO/CDEDD?filter=CDEDD.ITEM_ID=12217251%20and%20ver_nr=1
).harmonized: false
.name
.path
pointing to the right location (e.g.,unharmonized.foobar
—notmetadata.unharmonized.foobar
).url
,description
or both that describe the metadata field. Be as specific as possible, don't link to a general documentation page (linking within a particular documentation page where a metadata element's definition can be easily located is okay).Namespaces
GET /namespace
).GET /namespace/{organization}/{namespace}
).Organizations
GET /organization
).GET /organization/{name}
).Information
GET /info
).Other
v1
instead ofv0
.Beta Was this translation helpful? Give feedback.
All reactions