Test Dataset¶
This page contains links to test dataset files. The compliance suite expects the test dataset project, study, expression, and continuous resources to be available on the server and accessible by all relevant routes.
Project json
id: 9c0eba51095d3939437e220db196e27b
Format: json
- How to Prepare for Compliance Testing
upload
project.json
to RNAget serverproject.json
MUST be accessible by itsid
, ie./projects/9c0eba51095d3939437e220db196e27b
project.json
MUST appear in/projects/search
results arrayproject.json
MUST be filterable by implemented search filters
Study json
id: f3ba0b59bed0fa2f1030e7cb508324d1
Format: json
- How to Prepare for Compliance Testing
upload
study.json
to RNAget serverstudy.json
MUST be accessible by itsid
, ie./studies/f3ba0b59bed0fa2f1030e7cb508324d1
study.json
MUST appear in/studies/search
results arraystudy.json
MUST be filterable by implemented search filters
Expression ticket json
id: ac3e9279efd02f1c98de4ed3d335b98e
Format: json
- How to Prepare for Compliance Testing
modify
expression_ticket.json
url
property, so that it points to the test expression matrix file on the servermodify
expression_ticket.json
fileType
property to indicate test expression matrix file format (ie. ‘loom’ if loom, ‘tsv’ if tsv)upload modified
expression_ticket.json
to RNAget serverexpression_ticket.json
MUST be accessible by itsid
, ie./expressions/ac3e9279efd02f1c98de4ed3d335b98e/ticket
a valid ticket must be returned for requests for an expression ticket pertaining to the compliance dataset (e.g.
/expressions/ticket?format=loom&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Expression loom
id: ac3e9279efd02f1c98de4ed3d335b98e
Format: loom
- How to Prepare for Compliance Testing
upload
expression.loom
ONLY ifexpression_ticket.json
fileType
property was set to ‘loom’if uploaded, make
expression.loom
accessible by the url in theurl
property ofexpression_ticket.json
if uploaded,
expression.loom
must be sliceable by all subsetting parameters (featureIDList, featureNameList, sampleIDList)
Expression tsv
id: ac3e9279efd02f1c98de4ed3d335b98e
Format: tsv
- How to Prepare for Compliance Testing
upload
expression.tsv
ONLY ifexpression_ticket.json
fileType
property was set to ‘tsv’if uploaded, make
expression.tsv
accessible by the url in theurl
property ofexpression_ticket.json
if uploaded,
expression.tsv
must be sliceable by all subsetting parameters (featureIDList, featureNameList, sampleIDList)
Continuous ticket json
id: 5e22e009f41fc53cbea094a41de8798f
Format: json
- How to Prepare for Compliance Testing
modify
continuous_ticket.json
url
property, so that it points to the test continuous matrix file on the servermodify
continuous_ticket.json
fileType
property to indicate test continuous matrix file format (ie. ‘loom’ if loom, ‘tsv’ if tsv)upload modified
continuous_ticket.json
to RNAget servercontinuous_ticket.json
MUST be accessible by itsid
, ie./continuous/5e22e009f41fc53cbea094a41de8798f/ticket
a valid ticket must be returned for requests for a continuous ticket pertaining to the compliance dataset (e.g.
/continuous/ticket?format=loom&studyID=f3ba0b59bed0fa2f1030e7cb508324d1
Continuous loom
id: 5e22e009f41fc53cbea094a41de8798f
Format: loom
- How to Prepare for Compliance Testing
upload
continuous.loom
ONLY ifcontinuous_ticket.json
fileType
property was set to ‘loom’if uploaded, make
continuous.loom
accessible by the url in theurl
property ofcontinuous_ticket.json
if uploaded,
continuous.loom
must be sliceable by all subsetting parameters (chr, start, end)
Continuous tsv
id: 5e22e009f41fc53cbea094a41de8798f
Format: tsv
- How to Prepare for Compliance Testing
upload
continuous.tsv
ONLY ifcontinuous_ticket.json
fileType
property was set to ‘tsv’if uploaded, make
continuous.tsv
accessible by the url in theurl
property ofcontinuous_ticket.json
if uploaded,
continuous.tsv
must be sliceable by all subsetting parameters (chr, start, end)
Filter json
Format: json
- How to Prepare for Compliance Testing
filter.json
is an example, this file does not need to be uploaded, but requests for supported filters must respond with an array of validfilter
objects
Error json
Format: json
- How to Prepare for Compliance Testing
error.json
is an example, this file does not need to be uploaded, but requests that produce an error must respond with a validError
json objectvalid
Error
json objects MUST at least contain a “message” property