Changeset 3445 for SMC


Ignore:
Timestamp:
08/20/13 12:06:37 (11 years ago)
Author:
vronk
Message:

added some links, moved examples to separate file

File:
1 edited

Legend:

Unmodified
Added
Removed
  • SMC/trunk/SMC/docs/userdocs.rst

    r2480 r3445  
    1515and elements or data categories as leaf nodes, parent-child relationship being defined by the inclusion (``componentA -includes-> componentB``) or referencing (``elementA -refersTo-> datcat1``).The reuse of components in multiple profiles and especially also the referencing of the same data categories in multiple CMD elements leads to a blending of the individual profile trees into a graph (acyclic directed, but not necessarily connected).
    1616
    17 SMC Browser visualizes this graph structure in an interactive fashion.
    18 
    19 It is implemented on top of wonderful js-library d3_, more technical documentation follows soon.
     17SMC Browser visualizes this graph structure in an interactive fashion. You can have a look at the `examples`_ for inspiration.
     18
     19It is implemented on top of wonderful js-library d3_, the code checked in `clarin-svn`_ (and needs refactoring). More technical documentation follows soon.
    2020
    2121.. _d3: https://github.com/mbostock/d3
     22.. _clarin-svn: https://svn.clarin.eu/SMC/trunk/SMC
     23.. _examples: examples.html
    2224
    2325
     
    3335The same goes for elements in reused components. In most cases it is indicated in the label, if the number reflect distinct items, or all (expanded) occurrences.
    3436
     37(Some of the) numbers in the statistics lead to a list of corresponding terms.
     38E.g. in the summary for a profile, clicking on the components-number lists all the components of given profile alphabetically.
     39Currently there are such lists for:
     40
     41  * ``profile -> components``
     42  * ``profile -> elements``
     43  * ``profile -> data categories``
     44  * ``data category -> profiles``
     45
    3546.. _Component Registry: http://catalog.clarin.eu/ds/ComponentRegistry/#
    3647.. _ISOcat: http://www.isocat.org
     
    106117  clicking on an item in the detail pane unselects it
    107118
     119select in statistics
     120        as mentioned in `Data`_ (some) numbers in the statistics reveal a list of corresponding terms.
     121        Clicking on these terms in the statistics page leads to the browser, with given term as selected node (and default settings)
     122       
     123select in statistics in the detail pane
     124  the numbers from statistics page are shown also in the detail pane for selected nodes.
     125  Here, clicking on a term from these lists adds it to the graph, as a selected node.
     126 
    108127mouseover
    109128  on mouse over a node, all connected nodes to given node (and connecting links) within the visible sub-graph are highlighted
     
    112131drag a node
    113132  click and hold on a node, one can move the node around, however usually the layout is stronger
    114   and puts the node back to its original position
     133  and puts the node back to its original position. Not so with the freeze-layout, that freezes all the nodes and lets you move them around freely
    115134
    116135Options
     
    131150        the higher the charge, the more the nodes tend to drift apart
    132151       
     152friction
     153  factor for "cooling down" the layout, lower numbers (50-70) stabilize the graph more quickly,
     154  but it may be too early, with higher numbers (95-100) the layout has more time/freedom to arrange,
     155  but may get jittery
     156 
    133157node-size
    134158  N = all nodes have given diameter N;
     
    146170 
    147171layout
    148   There are a few layouting algorithms provided,
    149   for different data displayed other algorithm may be more appropriate:
     172  There are a few layouting algorithms provided. They are all not optimal in any way, but most of the time, they deliver quite good results.
     173  For different data displayed other algorithm may be more appropriate:
    150174 
    151175  force
     
    155179    top-down layout respect the direction of the edges, children are always below the parents
    156180  horizontal-tree
    157     left-right layout respect the direction of the edges, children are always right to the parents
     181    left-right layout respect the direction of the edges, children are always right to the parents
     182    (at least they should be, currently, in certain configurations, the layout does not get the orientation for some links right)
    158183  weak-tree
    159184    a layout that "tends" towards left to right arrangement, but not strictly so (experimental)           
     
    192217.. _server-side processing: http://d3export.cancan.cshl.edu/
    193218 
    194  
    195 Examples
    196 ========
    197 
    198 `DCMI terms`_
    199 
    200 .. _DCMI terms: ?link-distance=24&charge=107&layout=force&selected=clarin_eucr1p_1288172614023,clarin_eucr1p_1288172614026&
    201219 
    202220Issues
     
    220238* Add information from **RelationRegistry** (relations between DatCats)
    221239* Blend in instance data from **MDRepository** (allow search on MDRepository)
     240* graph operations (intersect, difference of subrgraphs)
    222241
    223242Smaller enhancements of the user interface:
     
    229248* backlinking from detail (e.g. view all the profiles a data category is used in by clicking on the number ('used in profiles')
    230249* store/export SVG/PDF/PNG-renderings of the graphs
    231 * add layout ``freeze`` static layout, were individual nodes can be moved around freely
    232250* add edge-weight: scale based on usage, i.e. how often appears the relation in the complete dataset
    233251  i.e. often reused combinations of components/elements will be nearer
    234        
     252* allow to blend in further (private) CMD-profiles dynamically
Note: See TracChangeset for help on using the changeset viewer.