…r any given node
…lationships, with workaround for problem with incoming rels - expanded size of visualisation component (need further UI work to accomodate this - TBD)
…f relationship types to appear.
… Note, double-click event is not responding to allow redrawing of the chart around the new selection. ...work in progress :-)
…commit was hardwired to a local development address)
…eves EVERYTHING within 2 relationships. Obviously this will bring back a lot of noise on larger data sets, but it is good for demoing (for now). The SWF visualisation component is a little nicer now that it has a different color for each node type, although I'm still working on labels and edge positions (should be centred to each node). Other than that, cleaned up some more code and made things work a bit better!!!
…ere are plenty of broken bits in here and my code for network data retrieval is just plain wrong. :-) Sorry. This cut provides a very ugly visualisation of the network surrounding any person node. The visualisation component is a SWF file using the Prefuse Flare ActionScript library. A rudimentary GraphML generator page (/people/graphml/id) produces GraphML data to be read by the visualisation component. Lots of next steps before this is anywhere near ready! I'm mainly pushing this so interested people can see the first cut of data visualisation. Signed-off-by: sashaagafonoff <firstname.lastname@example.org>
…steps now and much easier to use!!!! Signed-off-by: sashaagafonoff <email@example.com>
…config changes to assist installation Signed-off-by: sashaagafonoff <firstname.lastname@example.org>
…link tests within each model type (eg person to person). Fixed some bugs found in the process of testing!!! Signed-off-by: sashaagafonoff <email@example.com>
…hese initial test cases create Person data and test relationship linking. Signed-off-by: sashaagafonoff <firstname.lastname@example.org>
…ared/_filtered_target.html.haml), made some facial changes to the UI and changed the generic search model for events. Next steps are to add attachment_fu support for files and images and to start building a test suite before writing too much more code... :-) Signed-off-by: sashaagafonoff <email@example.com>
…main model without extensive testing - i know there are still issues!!! Signed-off-by: sashaagafonoff <firstname.lastname@example.org>
….xml and update linking across whole domain model Signed-off-by: sashaagafonoff <email@example.com>
…el easily implemented in Rails, but which draws on a master XML file (/config/relationships.xml) to define richer relationship definitions. This file is used to configure drop down lists as well as to supply additional relationship metadata which should not be written to the store (ie not user-defined). Using the relationships.xml file allows you to manage all of the sub-types from a simple XML/Excel file, allowing super-quick updates to the relationship model. As usual, this is still in pieces and should be treated as broken... Signed-off-by: sashaagafonoff <firstname.lastname@example.org>
…, but I won't extend this approach to all types - it is very unwieldy. The next step is to rewrite all of that code to work with an OWL ontology so that drop lists and relationship descriptions are informed by that rather than long case statements and hard-coded hashes in controller files (yuk). All Person and shared files have been converted to HAML now, but the other types won't move over until I've written the OWL support.
…notes, category, subcategory and English descriptions (past and present). Obviously the code for this needs a few more rounds of refactoring (being hopelessly naive) but it is starting to work nicely. Fixed a bunch of other things and (as usual) fiddled with styles. I'm not going to get too verbose about changes in such early prototyping!
…, started work on the rich link form for creating links with start/end dates and notes - all very incomplete...