Open TiberiusB opened 9 years ago
That was a temporary workaround. Now we need to figure out the whole relationship. I'm marking this priority and next.
Suggestion for a hack for now: make the selection list for agents who can log work to be agents that have users.
Good idea, will do.
On Tue, Jul 14, 2015 at 1:31 PM, Lynn Foster notifications@github.com wrote:
Suggestion for a hack for now: make the selection list for agents who can log work to be agents that have users.
— Reply to this email directly or view it on GitHub https://github.com/valnet/valuenetwork/issues/422#issuecomment-121332740 .
Description of the problem: SENSORICA is collaborating with another network, 99%media on a funding initiative. 99%media take a risk with us and will be rewarded a % from the funding. Also, they want to test the NRP-VAS. We want to log their contributions as a network organization, one affiliate, of SENSORICA. If we call 99%media a network in the system, we can't make them a user account. Bob found a work around for now, is to make them an individual, make a user account, and flip back to a network, so 99%media can be a network and also have a user account. The problem is that if we do that, their name doesn't appear in the list of agents for process logging. I changed the agent type of 99%media to Individual, in order to be able to log their contributions. But this doesn't reflect the reality, and it makes the whole thing less intuitive. In reality they are a network. We need to log their contributions as if they are a single entity. But that doesn't work no in the system.
Perhaps I don't understand how the network-to-network interface works... Perhaps we need to implement this in a different way...
Here's their account http://nrp.sensorica.co/accounting/agent/319/