Skip to content
This repository has been archived by the owner on Apr 12, 2023. It is now read-only.

Add Udp case pages - ready to merge #1346

Merged
merged 20 commits into from
Nov 28, 2016
Merged
Show file tree
Hide file tree
Changes from 4 commits
Commits
Show all changes
20 commits
Select commit Hold shift + click to select a range
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
156 changes: 156 additions & 0 deletions conf/golr-views/single-tab/individual-gene.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,156 @@
id: individual_gene
schema_generating: true
document_category: generic_association
weight: 20

## Results table, horizontal
result_weights: subject^6.0 object^5.0

## Ordering of facets, vertical
filter_weights: subject_taxon_closure_label^3.5 object_taxon_closure_label^3.0

## SOLR FIELD DEFINITIONS

fields:

## SUBJECT

- id: subject
description: "The CURIE for oban:association_has_subject. May be disease, variant, gene, person, ...."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here I would suggest "case" instead of person

display_name: Case
type: string
property: []

- id: subject_label
description: "Label for association_subject. This will always be rdfs:label. Conventions may vary as to what goes in the label. For genes will be symbol, but we may choose to uniquify by prefixing with species"
display_name: Case
type: string
property: []
searchable: true

- id: subject_closure
description: "Reflexive closure of association_has_subject. A list of CURIEs. If an individual, first traverse rdf:tpye. The default closure is subclass, but other may optionally be added depending on what type of association this is and what the class is. E.g. for expression associations, the object is an anatomy class, and the closure will include part_of"
display_name: Case
type: string
cardinality: multi
property: []

- id: subject_closure_label
description: "Labels for subject_closure."
display_name: Case
type: string
cardinality: multi
property: []
searchable: true

- id: subject_taxon
description: "Taxonomic class of the subject. This is typically a CURIE of the form NCBITaxon:nnnn."
display_name: Species
type: string
property: []

- id: subject_taxon_label
description: "Label of taxon."
display_name: Species
type: string
property: []
searchable: true

- id: subject_taxon_closure
description: "Reflexive closure of taxon. ALWAYS up SubClassOf."
display_name: Species
type: string
cardinality: multi
property: []

- id: subject_taxon_closure_label
description: "Labels for taxon_closure."
display_name: Species
type: string
cardinality: multi
property: []
searchable: true

- id: object
description: "The CURIE for oban:association_has_object. This is often, but not always an ontology class. E.g. for a gene-gene interaction it is an (arbitrary) member of the pair."
display_name: Gene
type: string
property: []

- id: object_label
description: "Label for association_object."
display_name: Gene
type: string
property: []
searchable: true

- id: object_closure
description: "Reflexive closure of association_has_object. A list of CURIEs. If an individual, first traverse rdf:tpye. The default closure is subclass, but other may optionally be added depending on what type of association this is and what the class is. E.g. for expression associations, the object is an anatomy class, and the closure will include part_of"
display_name: Gene
type: string
cardinality: multi
property: []

- id: object_closure_label
description: "Labels for object_class_closure."
display_name: Gene
type: string
cardinality: multi
property: []
searchable: true

- id: object_taxon
description: "Taxonomic class of the object. This is typically a CURIE of the form NCBITaxon:nnnn. This field may be unfilled when used with certain categories"
display_name: Species
type: string
property: []

- id: object_taxon_label
description: "Label of taxon."
display_name: Species
type: string
property: []
searchable: true

- id: object_taxon_closure
description: "Reflexive closure of taxon. ALWAYS up SubClassOf."
display_name: Species
type: string
cardinality: multi
property: []

- id: object_taxon_closure_label
description: "Labels for taxon_closure."
display_name: Species
type: string
cardinality: multi
property: []
searchable: true

- id: evidence_object
description: "List of CURIES of all entities that form part of the evidence graph."
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_label
description: "evidence object label"
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_closure
description: "Closure for evidence object"
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_closure_label
description: "List of CURIES of all entities that form part of the evidence closure."
display_name: Evidence
type: string
cardinality: multi
property: []
156 changes: 156 additions & 0 deletions conf/golr-views/single-tab/individual-phenotype.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,156 @@
id: individual_phenotype
schema_generating: true
document_category: generic_association
weight: 20

## Results table, horizontal
result_weights: subject^6.0 object^5.0

## Ordering of facets, vertical
filter_weights: subject_taxon_label^3.5

## SOLR FIELD DEFINITIONS

fields:

## SUBJECT

- id: subject
description: "The CURIE for oban:association_has_subject. May be disease, variant, gene, person, ...."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here I would suggest "case" instead of "person"

display_name: Case
type: string
property: []

- id: subject_label
description: "Label for association_subject. This will always be rdfs:label. Conventions may vary as to what goes in the label. For genes will be symbol, but we may choose to uniquify by prefixing with species"
display_name: Case
type: string
property: []
searchable: true

- id: subject_closure
description: "Reflexive closure of association_has_subject. A list of CURIEs. If an individual, first traverse rdf:tpye. The default closure is subclass, but other may optionally be added depending on what type of association this is and what the class is. E.g. for expression associations, the object is an anatomy class, and the closure will include part_of"
display_name: Case
type: string
cardinality: multi
property: []

- id: subject_closure_label
description: "Labels for subject_closure."
display_name: Case
type: string
cardinality: multi
property: []
searchable: true

- id: subject_taxon
description: "Taxonomic class of the subject. This is typically a CURIE of the form NCBITaxon:nnnn."
display_name: Species
type: string
property: []

- id: subject_taxon_label
description: "Label of taxon."
display_name: Species
type: string
property: []
searchable: true

- id: subject_taxon_closure
description: "Reflexive closure of taxon. ALWAYS up SubClassOf."
display_name: Species
type: string
cardinality: multi
property: []

- id: subject_taxon_closure_label
description: "Labels for taxon_closure."
display_name: Species
type: string
cardinality: multi
property: []
searchable: true

- id: object
description: "The CURIE for oban:association_has_object. This is often, but not always an ontology class. E.g. for a gene-gene interaction it is an (arbitrary) member of the pair."
display_name: Phenotype
type: string
property: []

- id: object_label
description: "Label for association_object."
display_name: Phenotype
type: string
property: []
searchable: true

- id: object_closure
description: "Reflexive closure of association_has_object. A list of CURIEs. If an individual, first traverse rdf:tpye. The default closure is subclass, but other may optionally be added depending on what type of association this is and what the class is. E.g. for expression associations, the object is an anatomy class, and the closure will include part_of"
display_name: Phenotype
type: string
cardinality: multi
property: []

- id: object_closure_label
description: "Labels for object_class_closure."
display_name: Phenotype
type: string
cardinality: multi
property: []
searchable: true

- id: object_taxon
description: "Taxonomic class of the object. This is typically a CURIE of the form NCBITaxon:nnnn. This field may be unfilled when used with certain categories"
display_name: Species
type: string
property: []

- id: object_taxon_label
description: "Label of taxon."
display_name: Species
type: string
property: []
searchable: true

- id: object_taxon_closure
description: "Reflexive closure of taxon. ALWAYS up SubClassOf."
display_name: Species
type: string
cardinality: multi
property: []

- id: object_taxon_closure_label
description: "Labels for taxon_closure."
display_name: Species
type: string
cardinality: multi
property: []
searchable: true

- id: evidence_object
description: "List of CURIES of all entities that form part of the evidence graph."
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_label
description: "evidence object label"
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_closure
description: "Closure for evidence object"
display_name: Evidence
type: string
cardinality: multi
property: []

- id: evidence_object_closure_label
description: "List of CURIES of all entities that form part of the evidence closure."
display_name: Evidence
type: string
cardinality: multi
property: []
Loading