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

    • Download project.json

    • id: 9c0eba51095d3939437e220db196e27b

    • Format: json

    • How to Prepare for Compliance Testing

      • upload project.json to RNAget server

      • project.json MUST be accessible by its id, ie. /projects/9c0eba51095d3939437e220db196e27b

      • project.json MUST appear in /projects/search results array

      • project.json MUST be filterable by implemented search filters

  • Study json

    • Download

    • id: f3ba0b59bed0fa2f1030e7cb508324d1

    • Format: json

    • How to Prepare for Compliance Testing

      • upload study.json to RNAget server

      • study.json MUST be accessible by its id, ie. /studies/f3ba0b59bed0fa2f1030e7cb508324d1

      • study.json MUST appear in /studies/search results array

      • study.json MUST be filterable by implemented search filters

  • Expression ticket json

    • Download

    • 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 server

      • modify 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 server

      • expression_ticket.json MUST be accessible by its id, 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

    • Download

    • id: ac3e9279efd02f1c98de4ed3d335b98e

    • Format: loom

    • How to Prepare for Compliance Testing

      • upload expression.loom ONLY if expression_ticket.json fileType property was set to ‘loom’

      • if uploaded, make expression.loom accessible by the url in the url property of expression_ticket.json

      • if uploaded, expression.loom must be sliceable by all subsetting parameters (featureIDList, featureNameList, sampleIDList)

  • Expression tsv

    • Download

    • id: ac3e9279efd02f1c98de4ed3d335b98e

    • Format: tsv

    • How to Prepare for Compliance Testing

      • upload expression.tsv ONLY if expression_ticket.json fileType property was set to ‘tsv’

      • if uploaded, make expression.tsv accessible by the url in the url property of expression_ticket.json

      • if uploaded, expression.tsv must be sliceable by all subsetting parameters (featureIDList, featureNameList, sampleIDList)

  • Continuous ticket json

    • Download

    • 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 server

      • modify 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 server

      • continuous_ticket.json MUST be accessible by its id, 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

    • Download

    • id: 5e22e009f41fc53cbea094a41de8798f

    • Format: loom

    • How to Prepare for Compliance Testing

      • upload continuous.loom ONLY if continuous_ticket.json fileType property was set to ‘loom’

      • if uploaded, make continuous.loom accessible by the url in the url property of continuous_ticket.json

      • if uploaded, continuous.loom must be sliceable by all subsetting parameters (chr, start, end)

  • Continuous tsv

    • Download

    • id: 5e22e009f41fc53cbea094a41de8798f

    • Format: tsv

    • How to Prepare for Compliance Testing

      • upload continuous.tsv ONLY if continuous_ticket.json fileType property was set to ‘tsv’

      • if uploaded, make continuous.tsv accessible by the url in the url property of continuous_ticket.json

      • if uploaded, continuous.tsv must be sliceable by all subsetting parameters (chr, start, end)

  • Filter json

    • Download

    • 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 valid filter objects

  • Error json

    • Download

    • 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 valid Error json object

      • valid Error json objects MUST at least contain a “message” property