Versions Compared

Old Version 25

changes.mady.by.user Brian White

Saved on

compared with

New Version Current

changes.mady.by.user James Eddy

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Source data 

Synapse Table: https://www.synapse.org/#!Synapse:syn21517423syn21868591/tables/

Previously used DEPRECATED Synapse fileviewFile View: https://www.synapse.org/#!Synapse:syn18488466/tables/      

NOTE: Studies are selected in this view with is.dataset == TRUE 

DEPRECATED Synapse Table: https://www.synapse.org/#!Synapse:syn21517423/tables/

...

Explore page config

Type / name of card: "Datasets"

Number of Secondary Fields to show: 4

Note that there is no explicit aliasing between Column Name and Display Name. Rather, camelCase Column Names are automatically rendered as Camel Case. The table below just makes that clear.

Facets should be ordered in the order they appear in this table.

Any column that should be faceted in the portal (i.e., faceted on an explore page or have a column facet on a table) must be faceted on the corresponding Synapse table/view. There is a performance penalty incurred with each additional facet – hence, facet only those columns needed by the portal and limit to those likely to be useful.

Display Name

Column Name

Column Type

Link Format

Facet Y/N

Facet Order

Card UI Mapping

Destination

Link Query Key

Link Value Column

Searchable Y/N

Search Order

Search

hint text

Hint Text

Icon







icon

default = disk






Dataset Name

datasetName

STRING


N

NA

Card_TitleLink to dataset details page, where the key in the Synapse datasets table is "datasetName" (call it datasets:datasetName for clarity) and the value <datasetName> is pulled from the "datasetName" column of this same datasets table, e.g. datasets:datasetName=<datasetName> ”

title

Datasets/DetailsPage

datasetId

datasetId

Y

1

e.g. migration

id


datasetId

ENTITY


N

NA





N

NA

datasets



datasetAlias

STRING


N

NA





N

NA


Description

description

LARGE_TEXT


N

NA

Card_Description

description




Y

2

e.g. spatiotemporal

Publication

TitlepublicationTitle

publication

STRING

markdown: 
[publicationTitle](pubMedUrl)

N

NA

Secondary_Label_1URL in markdown

secondaryLabels[0]

PubMed record



Y

4

e.g. immune escape

Overall Design

overallDesign

STRING


N

NA

Secondary_Label_2NA

secondaryLabels[1]




Y

3


Theme

ThemeN

theme

STRING_LIST*


Y

1





N

NA

e.g. tumor-immune

Tumor Type

tumorType

STRING_LIST*


Y

3

secondaryLabels[2]

Secondary_Label_3Secondary_Label_4




Y

7

e.g. Skin Cutaneous Melanoma

Assay

assay

STRING_LIST*


Y

1Secondary_Label_5

2

secondaryLabels[3]




Y

6

e.g. RNA-seq

Species

species

STRING_LIST*


Y

3

4

secondaryLabels[4]




N

NA

e.g. Human

External Link

externalLink

STRING


N

NA

Secondary_Label_6

secondaryLabels[5]

URL embedded in HTML



N

NA

e.g. GSE93776

Grant Name

grantName

STRING_LIST*

portal query (each)

Y

4Secondary_Label_7Link to grant details page, where the key in the Synapse grant table is "grantName" (call it grant:grantName for clarity) and the value <grantName> is pulled from the "grantName" column of this dataset table, e.g. grant:grantName=<grantName> ”

5

secondaryLabels[6]

Grants/DetailsPage

grantName

grantName

Y

5

e.g. immunology

Consortium

consortium

STRING_LIST*


Y

5Secondary_Label_8

6

secondaryLabels[7]




N

NA

e.g. PS-ON

Grant TypegrantTypeY6Secondary_Label_9NNAe.g. U01

Detail pages:*<TYPE>_LIST columns for multi-value annotations not yet implemented

...

Details page config 

Detail pages should display the above information (i.e., from the card) in the header/banner of the page. The query to get that information should be on this table using datasets:

SELECT * FROM syn18488466 where "datasets" = 'syn7248581'

Additionally, we should display files associated with this dataset by querying the files table using datasets, i.e.,.

files:

SELECT * FROM syn9630847 where "datasets" = 'syn7248581'