VF Code Experiments issueshttps://lab.allmende.io/groups/valueflows/vf-code-experiments/-/issues2021-08-07T16:47:00Zhttps://lab.allmende.io/valueflows/vf-code-experiments/demo-app-backend/-/issues/1Get most recent code off of server2021-08-07T16:47:00ZLynn FosterGet most recent code off of serverThis version is now old. Although it worked locally, it didn't work at all on the pythonanywhere server, even with all the same lib version numbers. So we hacked at it on the server itself, since there are nice facilities to be able to...This version is now old. Although it worked locally, it didn't work at all on the pythonanywhere server, even with all the same lib version numbers. So we hacked at it on the server itself, since there are nice facilities to be able to do that. That version has not been brought back here. Might never be, if there isn't much interest in it. But if it becomes useful, we should get the server version back into git here, get it working locally, and get a more "normal" workflow going.https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/12Allow import of examples2020-08-07T11:52:42ZJohannes Winteryova@freedomhost.deAllow import of examplesTo visualize and test the examples for correctness the vocabulator seems to be of good use. See https://lab.allmende.io/valueflows/valueflows/-/issues/646To visualize and test the examples for correctness the vocabulator seems to be of good use. See https://lab.allmende.io/valueflows/valueflows/-/issues/646https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/11Upgrade to latest python3 and valueflows2021-07-15T15:05:08ZJohannes Winteryova@freedomhost.deUpgrade to latest python3 and valueflowspython2 is out of date, and the ontology evolved but the vocabulator seems still be useful for modelling purposes: https://lab.allmende.io/valueflows/valueflows/-/issues/646#note_37850python2 is out of date, and the ontology evolved but the vocabulator seems still be useful for modelling purposes: https://lab.allmende.io/valueflows/valueflows/-/issues/646#note_37850https://lab.allmende.io/valueflows/vf-code-experiments/valuenetwork/-/issues/2"Too Many Redirects" for non-staff users2020-04-04T19:38:47ZLynn Foster"Too Many Redirects" for non-staff users*Created by: JamesVorder*
> James. what I did to make it work for Stephanie is made her a staff
> user. That fixed the "too many redirects" problem.
>
> But
> 1) I am not sure why, so there's still an underlying problem.
> 2) That...*Created by: JamesVorder*
> James. what I did to make it work for Stephanie is made her a staff
> user. That fixed the "too many redirects" problem.
>
> But
> 1) I am not sure why, so there's still an underlying problem.
> 2) That only works if we want to make everybody a staff user.
>
> So it's a good clue, and maybe a good temporary solution, but maybe
> not a good permanent solution.
## Steps To Reproduce
1. Create a non-staff account
1. Log in with that account
1. Navigate to the "Organization" tab
Expected behavior: The organization page is shown
Actual behavior: Error! "The page isn't redirecting properly"https://lab.allmende.io/valueflows/vf-code-experiments/valuenetwork/-/issues/1Order schedule process date changes do not bump subsequent processes2020-03-11T16:46:23ZBob HaugenOrder schedule process date changes do not bump subsequent processesSee https://valnet.lurker.dev/accounting/order-schedule/1/
Changed date on Translate to later, did not bump Copyedit etc.See https://valnet.lurker.dev/accounting/order-schedule/1/
Changed date on Translate to later, did not bump Copyedit etc.https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/10Show data for resource flows like for Agents etc2018-07-27T19:37:29ZBob HaugenShow data for resource flows like for Agents etcThis is required for https://github.com/valueflows/vf-apps-traversing-the-flows/issues/2This is required for https://github.com/valueflows/vf-apps-traversing-the-flows/issues/2https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/9incoming flows tree has some weird repetitions2017-11-26T21:39:23ZBob Haugenincoming flows tree has some weird repetitions![screenshot from 2017-11-26 15-37-20](https://user-images.githubusercontent.com/117439/33244584-efd021d4-d2bf-11e7-88e1-dde8c268e539.png)
![screenshot from 2017-11-26 15-37-20](https://user-images.githubusercontent.com/117439/33244584-efd021d4-d2bf-11e7-88e1-dde8c268e539.png)
https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/7Traversing process/resource flows2020-08-02T17:29:22ZBob HaugenTraversing process/resource flowsI am thinking through this topic from the viewpoint of https://github.com/django-rea/rea-app/wiki/Writing-Tests
See also https://www.valueflo.ws/introduction/processes.html
I'll be working on this for awhile, slowly, thinking about...I am thinking through this topic from the viewpoint of https://github.com/django-rea/rea-app/wiki/Writing-Tests
See also https://www.valueflo.ws/introduction/processes.html
I'll be working on this for awhile, slowly, thinking about every step. I'm writing it down here, but if you are watching and reading, don't expect quick coherence.
I'm doing this here instead of in django-rea, because the code is a lot simpler here, and I am starting from scratch on the traversal code, while the traversal code in django-rea is still the same as [the original version of NRP](https://github.com/valnet/valuenetwork). Which was not architected according to the rea-app standards, but mostly improvised using the make-it-work, make-it-right, make-it-fast method. And it's still at the first stage. It does have some tests, but written after the code.
So this is a chance to rethink and maybe make-it-right. We'll see.
https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/6Documenting some policies I am following2017-04-02T16:42:46ZBob HaugenDocumenting some policies I am followingTo the extent possible, I will implement only stuff that we have agreed on in valueflows discussions: where we have a pretty clear consensus, like in the latest release, or something that has been explicitly okayed and not explicitly blo...To the extent possible, I will implement only stuff that we have agreed on in valueflows discussions: where we have a pretty clear consensus, like in the latest release, or something that has been explicitly okayed and not explicitly blocked. That is true for the code for models and output representations, and also for the demo data that I am creating.
That means, for example, I deleted ValueFlows as an Agent in the demo data, because we clearly do not have consensus on that. So, in the fine tradition of the Web, those of use who want to think of VF as an Agent can do so, and those of us who not want to think of VF as an Agent will not have a VF Agent staring at them from the Vocabulator pages.
What I mean by "to the extent possible", I do intend implement a good selection of our use cases, both to test vocabulator, but also for testing and demoing and probably refining the vocabulary. So sometimes I may need to stretch a little beyond what we have agreed on in order to implement the use case. I will try to do that sparingly, and raise an issue here before I do so, to give people time for comments and disagreements.
Let me know if you are unhappy with any of these policies.https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/5How to implement Person, Group, Organization and other Agent whatevers?2017-03-31T21:32:59ZBob HaugenHow to implement Person, Group, Organization and other Agent whatevers?in the vocabulator relational models. I can do subclassing. I can also do type objects, or just plain hard-coded lists of choices.
https://github.com/valueflows/vocabulator/blob/master/vocab/models.pyin the vocabulator relational models. I can do subclassing. I can also do type objects, or just plain hard-coded lists of choices.
https://github.com/valueflows/vocabulator/blob/master/vocab/models.pyhttps://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/4How to implement Agent relationships to other Agents?2017-03-24T13:07:33ZBob HaugenHow to implement Agent relationships to other Agents?I want to add them to the vocabulator now, today. They need to be expressable in a relational model, for the time being.
See https://github.com/valueflows/vocabulator/blob/master/vocab/models.py
I want to add them to the vocabulator now, today. They need to be expressable in a relational model, for the time being.
See https://github.com/valueflows/vocabulator/blob/master/vocab/models.py
https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/3Request for ongoing code review2017-03-24T12:54:06ZBob HaugenRequest for ongoing code reviewEspecially re https://github.com/valueflows/vocabulator/blob/master/vocab/models.py
As @fosterlynn mentioned, I am working with a relational data model. I can do a little inheritance, but it's also a little ugly.
I am doing this t...Especially re https://github.com/valueflows/vocabulator/blob/master/vocab/models.py
As @fosterlynn mentioned, I am working with a relational data model. I can do a little inheritance, but it's also a little ugly.
I am doing this to get something deployed that is usable, and also because I want to support relational models as well as RDF-based models as well as plain old json and CSVs.
You can see the current output formats here: https://github.com/valueflows/vocabulator/blob/master/vocab/views.py#L20
More can be added, or if any of those are not needed, they can be removed.
This will all change over time. The current models are not fully implemented yet, but see next issue...https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/2A place to start2017-03-07T22:21:46ZLynn FosterA place to startOf course a few names will change, but here is where I think is the most stable place to start. And probably most useful, in terms of experimenting with value flow tracing.
Resource, Process, Event, Agent, Person, Group, Relationship...Of course a few names will change, but here is where I think is the most stable place to start. And probably most useful, in terms of experimenting with value flow tracing.
Resource, Process, Event, Agent, Person, Group, Relationship, Action - with their properties
I can help you figure out what in LOD land this involves. If you use a sqlite database, we'll have to add on something for RelationshipType, which needs a new name and is not needed in LOD. And Action will be different in the db and LOD.
https://lab.allmende.io/valueflows/vf-code-experiments/django-vocabulator/-/issues/1Rough draft head design2017-03-08T14:52:57ZBob HaugenRough draft head designAnd I mean, rough.
* User declares a context for their entries.
* Vocabulator offers CRUD for each nailed-down VF concept: data entry forms with selectors for relationships to other concepts.
* Saved in SQLite db.
* Shows graphical...And I mean, rough.
* User declares a context for their entries.
* Vocabulator offers CRUD for each nailed-down VF concept: data entry forms with selectors for relationships to other concepts.
* Saved in SQLite db.
* Shows graphical representation of everything in the user's context, as the user enters it.
* Offers buttons to display and export data in a variety for formats:
* Turtle
* Json-LD
* Plain old JSON
* CSV
* SQLite db with only their context
Feel free to suggest or make improvements.https://lab.allmende.io/valueflows/vf-code-experiments/resourceful/-/issues/5Explain my evolving methodology.2016-10-05T14:59:00ZLynn FosterExplain my evolving methodology.*Created by: agentlewis*
I have been thinking about spec writing for a long time. In this project I tried to both do a Domain Driven Design/Development to define all the requirements of the app. Along the way I came up with a different ...*Created by: agentlewis*
I have been thinking about spec writing for a long time. In this project I tried to both do a Domain Driven Design/Development to define all the requirements of the app. Along the way I came up with a different approach to organising/rationalising the specs.
It goes a little something like this:
- Define an event. (gherkin: when)
- Define the conditions that could precipitate the event. (gherkin: givens)
- Define the consequences for each of the scenarios. (gherkin: thans)
Note:
- There is only one event (When) per scenario. Ands/Buts are used to define validation criteria at the event occurrence. eg
```
Given I am an Anonymous User
When I send my New Account data
But my user name is already taken
Than I receive a helpful error message "Username taken :("
```
- And works well for conditions. But doesn't make sense... (thoughts)
```
Given I am an Anonymous User
And I have a shopping cart cookie
When I load any page
Than my cart is populated with its last items
```
- And & But can be used successfully for consequences
```
Given I am an Anonymous User
When I click on show more
Than I see more stuff
But I don't see show more anymore
```
With this understanding of specs I have come to see Discovery Sessions with clients to be more about trying to define all the events that should occur in the app and the main scenarios that go with these.
I also think there are different types of events. UI events, time based events and processing events. In a way an event can be thought of as a function being run.
https://lab.allmende.io/valueflows/vf-code-experiments/resourceful/-/issues/4Move from featurebook to cucumber.js2016-07-23T00:39:17ZLynn FosterMove from featurebook to cucumber.js*Created by: agentlewis*
Since starting this project cucumber.js has become much more of a thing and looks to do what is needed better :) So lets migrate.
*Created by: agentlewis*
Since starting this project cucumber.js has become much more of a thing and looks to do what is needed better :) So lets migrate.
https://lab.allmende.io/valueflows/vf-code-experiments/resourceful/-/issues/2How to read the Resourceful specs?2016-07-23T00:40:17ZBob HaugenHow to read the Resourceful specs?The link from the readme is a 404:
https://github.com/valueflows/resourceful/blob/master/features
And it's checkbox is not checked. Which I assume means, not implemented yet. Which is ok.
I can also find individual specs like this:
htt...The link from the readme is a 404:
https://github.com/valueflows/resourceful/blob/master/features
And it's checkbox is not checked. Which I assume means, not implemented yet. Which is ok.
I can also find individual specs like this:
https://github.com/valueflows/resourceful/blob/master/specification/backend_app/user/resources/create_resource.feature
But I assume the intent is to have an overview/table of contents/navigation thingie?
Any way I can help with this? I'd like to learn a little Cucumber.
https://lab.allmende.io/valueflows/vf-code-experiments/resourceful/-/issues/1Sharing of resources feature?2016-01-02T19:17:28ZLynn FosterSharing of resources feature?@ahdinosaur @donlewi Hi! Would you be interested in including sharing of resources at some point? (I don't know of any immediate needs. Just wanted to park the idea here for your consideration some day.)
There might be a lot of differ...@ahdinosaur @donlewi Hi! Would you be interested in including sharing of resources at some point? (I don't know of any immediate needs. Just wanted to park the idea here for your consideration some day.)
There might be a lot of different use cases for this, car share, etc. The one I have some familiarity with is when Sensorica (an open value network we work with) wanted to move into a new space with other maker type networks, and implement an app so they could share equipment between networks. This never happened, and the app never happened either. But we did a bit of initial requirements definition, which I could find.
A key feature was access rules for a resource, defined by the owner or custodian of the resource. Like certain people, certain projects, certain training required, others.
https://lab.allmende.io/valueflows/vf-code-experiments/linked-data-browser/-/issues/12duplicate items emerge after following my nose in a cycle2015-11-14T13:25:35ZBob Haugenduplicate items emerge after following my nose in a cyclefocus @id http://nrp.webfactional.com/api/agent-jsonld/
http://nrp.webfactional.com/api/agent-jsonld/
http://nrp.webfactional.com/api/agent-jsonld/success
http://nrp.webfactional.com/api/agent-type-lod/Organizationredirect
http://nrp.web...focus @id http://nrp.webfactional.com/api/agent-jsonld/
http://nrp.webfactional.com/api/agent-jsonld/
http://nrp.webfactional.com/api/agent-jsonld/success
http://nrp.webfactional.com/api/agent-type-lod/Organizationredirect
http://nrp.webfactional.com/api/agent-type-lod/Organization/success
http://nrp.webfactional.com/api/agent-type-lod/Networkredirect
http://nrp.webfactional.com/api/agent-type-lod/Network/success
http://nrp.webfactional.com/api/agent-lod/6/success
http://nrp.webfactional.com/api/agent-relationship-lod/2/success
http://nrp.webfactional.com/api/agent-lod/7/success
view as: nodelist
nrp:agent-lod/7/
vf:label
"Mikorizal Software"@en
"Mikorizal Software"@en
rdf:type
nrp:agent-type-lod/Group
nrp:agent-type-lod/Group
nrp:agent-relationship-type-lod/hasMember
nrp:agent-relationship-inv-lod/1/
nrp:agent-relationship-inv-lod/2/
nrp:agent-relationship-lod/2/
rdf:type
vf:Relationship
vf:Relationship
vf:subject
nrp:agent-lod/6/
nrp:agent-lod/6/
https://lab.allmende.io/valueflows/vf-code-experiments/linked-data-browser/-/issues/11Make breadcrumbs into hyperlinks2015-11-14T12:14:04ZBob HaugenMake breadcrumbs into hyperlinksI really like the history of what I've explored on the top, but would love it if each of those was hyperlinked as a LDB focus so I could refocus on it.
For example:
http://nrp.webfactional.com/api/agent-jsonld/ success
http://nrp.webfac...I really like the history of what I've explored on the top, but would love it if each of those was hyperlinked as a LDB focus so I could refocus on it.
For example:
http://nrp.webfactional.com/api/agent-jsonld/ success
http://nrp.webfactional.com/api/agent-type-lod/Organization redirect
http://nrp.webfactional.com/api/agent-type-lod/Organization/ success
http://nrp.webfactional.com/api/agent-type-lod/Network redirect
http://nrp.webfactional.com/api/agent-type-lod/Network/ success
http://nrp.webfactional.com/api/agent-lod/6/ success
http://nrp.webfactional.com/api/agent-relationship-lod/2/ success
http://nrp.webfactional.com/api/agent-lod/7/ success
They're not live hyperlinks. I'd love it if the "success" ones were, and if I clicked on one, it would refocus the LDB on that.