DataPath Example 1

This notebook gives an example of how to access the model elements (e.g., schemas, tables, columns) that are used when building data paths.



In [1]:

    
# Import deriva modules
from deriva.core import ErmrestCatalog, get_credential



In [2]:

    
# Connect with the deriva catalog
protocol = 'https'
hostname = 'www.facebase.org'
catalog_number = 1
credential = get_credential(hostname)
catalog = ErmrestCatalog(protocol, hostname, catalog_number, credential)

The PathBuilder Interface

The path builder interface gives you access to a representation of the catalog's data model beginning with the catalog's schemas. The path builder does not record any state about your paths, it is just an entry point to begin building paths.



In [3]:

    
# Get the path builder interface for this catalog
pb = catalog.getPathBuilder()

Access to Schemas

The .schemas property acts like a python dictionary or Map object. Use its keys() method to get a listing of the schema names.



In [4]:

    
pb.schemas.keys()









    Out[4]:





[u'vocab', u'viz', u'isa', u'_acl_admin']

Here we will get a handle to the isa schmea.



In [5]:

    
isa = pb.schemas['isa']

PROTIP: Jupyter Notebook supports <tab> completion. Press the <tab> key after typing the brackets of a dictionary to see the keys. Typing pb.schemas[<tab>] will give you a dropdown of schema names. Note that the notebook interpretter will not know anything about your objects until you have executed a step with them. So instantiate an object in one step, and then you can use tab-completion in the following steps.

Alternative access method for schemas and other model objects

An alternative way to get a handle to the same schema object is directly as a property of the path builder object itself. However, this only works for schema names that are valid python identifiers.

A valid python identifier may start with '_' or a letter as its first character and have '_', letters, or numbers for the rest of its characters.

Valid Python identifiers: 'dataset', 'assay', 'Molecule_Type', etc.
Invalid Python identifiers: 'Sample 1 Type', 'Control?', '# of reads', etc.

IMPORTANT Similar access methods will be demonstrated for tables and columns below. Since not all catalog model names are valid python identifiers when you use this method, you may not see your catalog's complete data model. However, the notation is more compact and ideal for cases where your model uses (all or mostly) valid python identifiers in its model element names.



In [6]:

    
isa = pb.isa  # same schema object we got from the previous step

Access to Tables

Similarly, a schema object has a tables property that gives you access to a representation of the catalog schema's tables. Again, use its keys() method to list the table names in the schema.



In [7]:

    
isa.tables.keys()









    Out[7]:





[u'enhancer',
 u'protocol',
 u'dataset_mutation',
 u'dataset_gene',
 u'dataset_somite_count',
 u'dataset',
 u'sample',
 u'dataset_instrument',
 u'mesh_data',
 u'file',
 u'project_publication',
 u'dataset_genotype',
 u'dataset_data_type',
 u'clinical_assay',
 u'alignment',
 u'biosample_cell_source',
 u'project_investigator',
 u'publication',
 u'library',
 u'imaging_data',
 u'sequencing_data',
 u'experiment',
 u'replicate',
 u'processed_data',
 u'project_member',
 u'dataset_cell_characterization',
 u'thumbnail',
 u'biosample',
 u'dataset_experiment_type',
 u'dataset_mouse_genetic_background',
 u'array_data',
 u'pipeline',
 u'previews',
 u'tracks',
 u'dataset_gender',
 u'track_data',
 u'dataset_phenotype',
 u'dataset_anatomy',
 u'icon',
 u'dataset_cell_source',
 u'dataset_human_age',
 u'dataset_chromosome',
 u'biosample_cell_characterization',
 u'dataset_enhancer',
 u'sample_replicate_group',
 u'dataset_stage',
 u'dataset_geo',
 u'project',
 u'person',
 u'external_reference',
 u'dataset_organism']

Similarly we can get a table from the schema's tables property in both of the demonstrated methods.



In [8]:

    
dataset = isa.tables['dataset']
# or
dataset = isa.dataset

Access to Columns

A table has a columns dictionary. We can get the column names as usual.



In [9]:

    
dataset.column_definitions.keys()









    Out[9]:





[u'RMB',
 u'funding',
 u'description',
 u'_keywords',
 u'title',
 u'RCT',
 u'release_date',
 u'show_in_jbrowse',
 u'accession',
 u'human_anatomic',
 u'summary',
 u'project',
 u'study_design',
 u'RMT',
 u'mouse_genetic',
 u'RID',
 u'released',
 u'id',
 u'RCB']

Again, we have the following methods to get handles to the table's column objects.



In [10]:

    
accession = dataset.column_definitions['accession']
# or
accession = dataset.accession

Final Thought

The model introspection provided in the datapath module (i.e., the PathBuilder) is intended for the narrowly scoped usage required for building paths and accessing data from ERMrest catalogs. It is not intended for general introspection of catalogs and therefore does not include details such as constraints, annotations, ACLs, column data types, etc.



In [ ]: