| [06:13:17] | * farmBOT has joined #farmos |
| [09:49:29] | <mstenta[m]> | Should we just add a general purpose key-value field to all assets/logs? |
| [09:49:38] | <mstenta[m]> | https://www.drupal.org/project/key_value_field |
| [09:50:22] | <mstenta[m]> | We've talked about this before |
| [09:50:40] | <mstenta[m]> | As a middle ground between fields and conventions |
| [09:51:05] | <mstenta[m]> | Also as a way to capture non-quantity information in a flexible way |
| [09:51:10] | <mstenta[m]> | on logs |
| [09:51:23] | <mstenta[m]> | (Actually maybe we ONLY add this to logs as a first step) |
| [09:53:10] | <FarmerEd[m]> | Does this will allow you to define they key and the value from the log UI? |
| [09:53:30] | <mstenta[m]> | Yea that would be the idea |
| [09:53:55] | <FarmerEd[m]> | How would that work from API? |
| [09:54:49] | <mstenta[m]> | Not sure - would need to test out that module |
| [09:55:18] | <symbioquine[m]> | <mstenta[m]> "Should we just add a general..." <- What about on quantity entities? |
| [09:55:48] | <mstenta[m]> | Hmm perhaps - maybe there are use-cases for both |
| [09:55:54] | <mstenta[m]> | I would probably start with logs at least |
| [09:56:14] | <symbioquine[m]> | oh, yeah I meant "also on quantity entities" |