## page was renamed from Molecular Interaction Maps/SimpleBinding ## page was renamed from SimpleBinding ## These are wiki comments - leave them in so that people can see them when editing the page ## This template may be useful for documenting use cases ## Developed in response to a hackathon request for formalized, detailed use cases ## to help direct implementation proposals || '''Use Case Name''' : ../NonCovalentBinding || || '''For Feature''' : MIM Editor|| || '''Editors''': DavidKane || ## EXAMPLE: ## Use Case Name: Representation of Protein Complex ## For Feature: Grouping Function ## Editors: Mr. Knowitall <> == Summary == ## Provide a one paragraph description of the use case A user wants to describe the possibility that two proteins can bind into a complex. == Step-by-Step User Action == ## Provide a step-by-step account of how the user would execute the use case. For example: (1) right click on node, (2) choose "expand" from context menu, (3) new view is created, etc... 1. User specifies a protein to be involved in the interaction 1. User specifies another protein to be involved in the interaction 1. User specifies that there is a binding relationship between the two 1. User specifies the evidence for this relationship == Visual Aides == ## Provide attachments to images to illustrate the use case (screenshots, mock-ups, storyboards, etc) The Kohn notation for this binding is the following: {{attachment:simplebinding1a_061113_dwk.png}} == Requirements for Cytoscape == ## List the components/functions already in Cytoscape that are relevant to the use case and possible implementations (e.g., "current context menus can be used accomplish step 2 above") ## Also list components/functions that are needed in Cytoscape to execute the use case (e.g., "cytoscape needs to allow for multiple views of the same network for this to work") Best mapped to a group. A and B are connected and are part of the group. The edge might be a new node type. The visualization of the Kohn notation would require changes to the rendered and the vizmapper. == Importance == ## Describe whether this use case is critical and how frequently users would come across it. Describe common work flows that might involve the use case (e.g., "this use case comes up regularly, on a weekly basis, whenever we want to analyze our protein superfamily networks"). This is a basic building block of the Kohn notation. == Other Examples == ## List other applications or relevant examples outside of Cytoscape that provide some or all of the desired functionality (e.g., "You can do this using the group function in PowerPoint"). == Variations == A protein can be involved in more than one interaction. A protein can appear in a particular MIM once, and only once. If a protein is involved in additional reactions, then additional edges are added for each reaction. {{attachment:simplebinding2a_061113_dwk.png}} The layout rules for the edges for bindings require that they be horizontal or vertical, and may have any number of right angles. The edges may cross other edges at right angles. == Comments == Shared ../MimEditorUseCaseComments The BioPAX representation of this binding could be a Conversion Object, i.e. with Participants = A,B, AB, Left = A,B, Right=AB, where A and B are Proteins, but AB is a complex with components A and B ) ---- AllanKuchinsky - 2006-11-16 04:03:13   The right angle constraints will require 'snap-to-grid' functionality in the Cytoscape editor.  This should be scheduled for implementation for Cytoscape 2.5.   Would this also require a mechanism in the editor to *enforce* constraints such as Manhattan (right-angle) geometry under certain conditions?  For example, when the user draws connecting edges for complexes in a MIMs-oriented editor, should the rubberbanding be restricted to horizontal or vertical lines?  This should be worked into the editor framework for Cytoscape 2.5, perhaps via support in the API for a 'right-angle' flag for the BasicCytoShapeEntity class.  But are there other, more general constraints that we need to support?  That would require a more general constraint handling mechanism in the editor framework, which would require more thought.  Hopefully, there is a finite set of constraints that we can handle directly, without the need for a general constraint handling mechanism. ---- GaryBader - 2006-11-16 07:40:25   This can also be represented as a 'physicalInteraction' in BioPAX as a shorthand.  In this case, you do not have to specify that a complex is formed.  However, this use is more general and you are not specifying the type of physical interaction.  I.e. it could be a biochemical reaction, but the underlying experiment only tells you that there is a physical association.  This is the kind of data generally stored in BIND, DIP, IntAct, MINT, HPRD, etc. ---- AllanKuchinsky - 2006-11-21 16:14:56   How does user specify evidence for an edge?  Do we do this via contextual menu?  By drag/drop?  Would this be represented in Cytoscape via attribute(s)?  Do we need a complex, structured 'evidence' attribute type, to handle the metadata as well as the data? ---- MiritAladjem - 2007-02-01 09:09:20   In response to  Allan's last question:  currently, evidence in the Kohn annotations is typically handled in the annotation file that is attached to the map.  Interactions are numbered to correspoond to those annotations. This is an area where there is an opportunity to directly attach evidence to elements of the model.