Hello Martin! Do you have documentation on how XOvis pipeline works? I would like to see how it works after the data is store and the visualization is generated.
Writing a tool to export the metadata from Harvest-server to a compatible subset in the visualization-ready format of XOvis, would be cheaper in development cost, but more expensive in running time (with large datasets). The other way around, would be to allow XOvis read directly from Harvest-server MySQL format. There are other options for integration too, but ultimately depends on how XOvis pipeline works :) On Fri, Jun 27, 2014 at 5:09 AM, Martin Dluhos <mar...@gnu.org> wrote: > On 06/24/2014 07:20 PM, Sameer Verma wrote: > > On Mon, Jun 23, 2014 at 9:32 PM, Martin Abente > > <martin.abente.lah...@gmail.com> wrote: > >> Hello Sameer, > >> > >> The harvest-client serializes (using json) a subset of journal-objects > >> metadata and then sends it to the harvest-server, which is basically a > >> web-service plus a MySQL back-end. > >> > > > > Great! Then we can perhaps add a method to process_journal_stats.py in > > XOVis to support Harvest. > > XOvis visualization relies on journal metadata being stored in couchdb in > json, > so it should be relatively straightforward to add a method to > process_journal_stats.py to read data generated by harvest-client and > store it > in the db. > > Martin >
_______________________________________________ Server-devel mailing list Server-devel@lists.laptop.org http://lists.laptop.org/listinfo/server-devel
