Export time logging data

[fosterlynn]

Tibi suggests we add a feature where they can filter and export time logging data into a CSV format. The need is to be able to start looking at the data to decide questions in the value equation, like what should be the percentage taken for "overhead" or "non-production" support work. (Eventually this could be reporting, with graphics, etc. Also eventually it would include financial contributions.)

[bhaugen]

You can already do that. Go to Economic Events in Admin, select what you want to export, and in the Action dropdown, select "Export selected objects as CSV file".

We might want to make it easier and format differently, but the basic capability is there for all Value accounting pages in Admin.

[TiberiusB]

I know that most of us agrree with these principles, but just for tue record - access to data and analysis on the data must be open to all members. Otherwise we create information asymetries, which will end up crearing classes and power unbalances. On Jul 29, 2013 11:12 AM, "Bob Haugen" notifications@github.com wrote:

You can already do that. Go to Economic Events in Admin, select what you want to export, and in the Action dropdown, select "Export selected objects as CSV file".

We might want to make it easier and format differently, but the basic capability is there for all Value accounting pages in Admin.

— Reply to this email directly or view it on GitHubhttps://github.com/valnet/valuenetwork/issues/70#issuecomment-21726022 .

[bhaugen]

I agree with the principle, but it takes work to make it happen (exports outside of admin), which somebody must do.

The exports inside admin were a plugin which took very little time to enable.

For exports outside of admin, we will need:

1. a design
2. priorities
3. what should be raw from the database and what should be combinations
4. code to make it happen

An alternative would be for somebody to do periodic exports from admin and put them into uploadable files somewhere in SENSORICA-land.

[TiberiusB]

This requires a definition of "private data" from an individual perspective, and some thoughts on security issues.

I don't know how this can be implemented, but the database should be stripped of "private data" and made ALL available to all members, and perhaps beyond, for analysis. All members should be able to write apps to interact with the data.

Relying on a gatekeeper to export data from the database is, in my opinion, not in accordance with the p2p principles.

I understand that this is not our top priority at this moment, because there are other more important things to do. I am just proposing a direction.

On Fri, Aug 2, 2013 at 10:44 AM, Bob Haugen notifications@github.comwrote:

I agree with the principle, but it takes work to make it happen (exports outside of admin), which somebody must do.

The exports inside admin were a plugin which took very little time to enable.

For exports outside of admin, we will need:

1. a design
2. priorities
3. what should be raw from the database and what should be combinations
4. code to make it happen

An alternative would be for somebody to do periodic exports from admin and put them into uploadable files somewhere in SENSORICA-land.

— Reply to this email directly or view it on GitHubhttps://github.com/valnet/valuenetwork/issues/70#issuecomment-22010179 .

t!b! http://www.google.com/profiles/tiberius.brastaviceanu co-founder of SENSORICA http://www.sensorica.co, an open, decentralized and self-organizing value network (an open enterprise)

founder of Multitude Project https://sites.google.com/site/multitude2008/

Google Profile https://plus.google.com/117593809719446924575/about Facebook Tiberius Brastaviceanuhttp://www.facebook.com/profile.php?id=100000279944184 Twitter @TiberiusB http://twitter.com/TiberiusB

[bhaugen]

(I edited this comment to dial back the sarcasm...)

I have no disagreement with the statement of direction.

But take seriously the idea of having one or more people export the data periodically now and put it somewhere where whoever you think should be able to work with it can do so.

As for anonymizing, I think the extracts that have any info that identifies people would be Users and Economic Agents. Or maybe names in descriptions, as in labnotes. Everything else will identify users and agents by database record keys, which are just numbers. We can do some test extracts to be sure, but I think the anonymization would be doable by a person in the short term. You would not need to handles users and agents very often, they won;t change much. Might not need to export users at all.

One more time on gatekeepers: to me, if you restrict the information you export, you are a gatekeeper. If you just export all of it, you are performing a service. Anonymization is somewhere in between, but if you got rough consensus on how to do it, it's probably a service.

[bhaugen]

I edited my previous comment, which those concerned with this issue should re-read. (Don't know if edited comments get notifications again.)

But I also wanted to add that the people who do the data exports do not need to be Tibi. (Or me or Lynn.) Could be anybody. We can give them access to just what they need to do the exports without necessarily overwhelming them with all the admin machinery.

[bhaugen]

This is how I plan to resolve this issue: https://github.com/burke-software/django-report-builder

Burke is also working on a dashboard app.

[bhaugen]

Also offer JSON in addition to CSV.

[automenta]

when this ticket closes i will try importing data into netention. i keep imagining how the valnet data would look in netention.

a public URL endpoint serving CSV or JSON would be the easiest way to connect valnet to any other service, just make sure it's well documented