Guest User

Untitled

a guest
Dec 13th, 2018
105
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.34 KB | None | 0 0
  1.  
  2. ### Scinario 2: Map common annotations to networks
  3. =====================
  4.  
  5. #### User Data
  6. * 2 human network files
  7. * Annnotation file for human genes
  8.  
  9. Assume annotation table has the following columns:
  10.  
  11. 1. NCBI Gene ID (Globally Unique)
  12. 2. Official Symbol (BRCA1, etc.)
  13. 3. Gene ontology terms (List of terms)
  14. 4. Aliases (IDs used in other databases)
  15.  
  16. #### Steps
  17. 1. Load the annotation file as a global table. Use NCBI Gene ID as primary key
  18. 2. Load two human networks. It can be in same root or two different roots
  19. 3. At this point, we should assume networks have a column (usually NAME) with NCBI Gene ID.
  20. 4. Create links (i.e. create virtual columns) from global table to networks by using NCBI Gene ID and NAME column as join key.
  21. 5. The final network has only one "real" column, NAME. All others are virtual.
  22.  
  23.  
  24. __This is how Gene Ontology Import function is hadnling annotations (Gene Association files are loaded as global tables).__ Most of the annotation files for genes/proteins can be linked to the network in this way.
  25.  
  26.  
  27.  
  28. ### Scinario 3: Import networks and annotations from web services
  29. =====================
  30.  
  31. #### User Data
  32. * None. Just query to the services
  33.  
  34. #### Steps
  35. 1. Send query to a web service.
  36. 2. Web service returns network(s) and annotations in their custom data structure. Usually, it contains at least one unique ID field for each node.
  37. 3. Convert returned data structure to CyNetwork. Use unique ID for NAME column of nodes.
  38. 4. Create global table for node annotations. Use uqinque ID as primary key for the global table.
  39. 5. Create links (i.e. create virtual columns) from global table to the new CyNetwork. Join key is the
  40. 6. Create edge columns in local table. In many cases, it does not make sense to create global table for edges since it usually contains network-specific values, such as edge score, publication links, etc.
  41. 7. Now, in the table browser, user can see node table with only one "real" column: NAME. All others are virtual. For edges, network has
  42. 8. Send another query.
  43. 9. Create a new network in existing network collection or create new root. It's user's choice.
  44. 10. Convert to CyNetwork. Again, use same unique ID as NAME.
  45. 11. For each annotation entry in the returned value, check the global table. If it exists, do not add. Otherwise, add a new row in the __global table__.
  46. 12. Link it to nodes.
  47. 13. Create local edge table values.
Add Comment
Please, Sign In to add comment