I know that the 7 branch uses the entity api. I think it'd be useful to be able to make entity types other than users trading partners. In particular, I'm envisioning projects as content types that work can be leveraged against, and people can both get credit based on the work the put into producing the project, and give credit based on usefulness or other self-defined qualities. This would help facilitate contributions to a commons instead of just contributions to private entities.

I'm picturing an implementation like organic groups, where the site admin can declare an entity as able to be a group or group content. WIthin OG, content types were the first entities to be included, but I believe that users and maybe taxonomies can now be groups. If you have any suggestions on where in the code to think about extending in this direction, I'd be happy to hack away.

Thanks!

Comments

matslats’s picture

matslats commented
Status: Active » Postponed

You're quite right that this would be a good approach.
Alternatively a new non-user entity could be created which could be a trading account.
However at the moment it is quite hard-coded, and it would require a degree more complexity once users have permissions over accounts.
So I've no plans to implement this in a voluntary capacity. If someone puts up some money for the 8.x branch maybe! Otherwise perhaps the Cyclos integration will open up possibilities.

mbrakken’s picture

mbrakken commented
Assigned: Unassigned » mbrakken

Thanks for the feedback, Matthew. Knowing that this would be a friendly modification, I'll start looking into it more. I have begun looking through your code to see how users/traders are declared, and I'll compare back and forth with OG. I'll start by seeing if I can shift things from user/uid to entity/eid of the user type. If I can get that stable and sound then there will be something I can increment upon.

This is high priority for the Mutual Aid Network site, so I expect to put in some significant hours over the next few weeks. Another module I use for the site is also trying to move towards entity abstraction (Location Taxonomize), so maybe I can learn things useful to both projects.

matslats’s picture

matslats commented
Issue summary: View changes

This is built in to version 4 (drupal 8).
Any contentEntityType will be able to control a wallet

matslats’s picture

matslats commented
Component: Transactions » Entities
Status: Postponed » Closed (fixed)