| [20:02:10] | * JustTB has joined #farmos |
| [22:04:50] | * JustTB has quit (Ping timeout: 248 seconds) |
| [22:20:08] | * JustTB has joined #farmos |
| [23:02:32] | * JustTB has quit (Ping timeout: 245 seconds) |
| [23:17:02] | * JustTB has joined #farmos |
| [02:22:56] | * margeo[m] has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [02:33:31] | * bumann[m] has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [02:33:46] | * MockingbirdConsu has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [02:35:46] | * amber65[m] has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [02:38:47] | * chriswilliams[m] has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [02:42:32] | * hawkridgehomeste has left #farmos ("Kicked by @appservice-irc:matrix.org : Idle kick: User has been idle for 30 days.") |
| [02:51:28] | * luigig[m] has quit (Quit: Idle kick: User has been idle for 30 days.) |
| [03:36:17] | * JustTB has quit (Ping timeout: 245 seconds) |
| [03:57:30] | * JustTB has joined #farmos |
| [05:56:07] | * JustTB has quit (Quit: Leaving.) |
| [09:40:20] | * JustTB has joined #farmos |
| [12:46:50] | <calbasi_matrix> | Hi, trying to introducing FarmOS in Catalonia (European Union), besides localization stuff there are "agricultural practices and burocratic issues"... |
| [12:47:51] | <calbasi_matrix> | Today, my pilot project farmer have asked me about label the areas with these fields/info, that are a requeriment on EU countries: |
| [12:48:48] | <calbasi_matrix> | 1) Town number (every european town has an official number) |
| [12:48:48] | <calbasi_matrix> | 2) Poligon |
| [12:48:49] | <calbasi_matrix> | 3) Piece of land ("parcel·la" in Catalan) |
| [12:50:26] | <calbasi_matrix> | Then, I think FarmOS don't have fields for this, similar to address module do... I'm a bit surprised because, for example, the location/town and related stuff could be interesting to add on an area record... |
| [12:51:41] | <calbasi_matrix> | Well, my idea could be, for example, add them just in the drupal way: adding taxonomies and related fields to the area records... Not difficult... But, are there problems when updating farmOS? |
| [12:53:29] | <calbasi_matrix> | (a derivated thought is that this: european union usual/common requirements could be added as a submodule of FarmOS. But I'm just learning about it, so I don't want run too fast :-p |
| [13:03:48] | <mstenta[m]> | That's an interesting idea @calbasi - adding address field to areas |
| [13:04:24] | <mstenta[m]> | I'd like to consider it in relation to future plans... |
| [13:05:02] | <mstenta[m]> | We've been talking about converting areas to a different entity type (moving away from taxonomy terms, perhaps to assets) |
| [13:05:10] | <mstenta[m]> | But that should still work |
| [13:05:32] | <mstenta[m]> | I think the address field makes the most sense on a "Property" area type |
| [13:15:25] | <mstenta[m]> | If you want to start an issue we can discuss and link to others |
| [13:52:02] | <calbasi_matrix> | OK! I'll open a new issue ;-) |
| [13:55:34] | <calbasi_matrix> | I think on d8 even a taxonomy entity could be fielable with an address type field... |
| [13:55:58] | <calbasi_matrix> | So that won't be a problem... But now I don't remember if this is possible on d7 :-) |
| [13:56:39] | <mstenta[m]> | Yes, taxonomy terms are fieldable in D7 too |
| [13:57:26] | <mstenta[m]> | If you want to experiment with it feel free! Just know that if we decide to take a different approach in farmOS itself, there won't be an upgrade path (or you'll need to write one yourself) |
| [13:57:44] | <calbasi_matrix> | Address fields, sometimes have certain contraints, because show lot of information that could no be useful here, just for "administrative / regulatory" codes... In fact, they are more similar to ID labels in animals... |
| [13:58:11] | <mstenta[m]> | Hmm good point |
| [13:59:43] | <calbasi_matrix> | Tell me something, if I add a field in a farmos taxonomy, then my system breaks on a "normal" upgrade? (if this taxonomy has not been "altered"?). Or, for example, if I add a new taxonomy linked to a farm OS entity |
| [14:00:30] | <mstenta[m]> | No, adding new fields shouldn't break anything |
| [14:00:41] | <mstenta[m]> | UNLESS farmOS itself adds a field with the same name... |
| [14:01:31] | <mstenta[m]> | But that can be avoided by namespacing the field machine name (don't use `farm_`) |
| [14:01:49] | <mstenta[m]> | You might experience some issues with the ordering of the fields... |
| [14:01:54] | <mstenta[m]> | Because farmOS does manage the order of fields that it provides |
| [14:34:36] | <calbasi_matrix> | Nice, then, easy to "extend", in a custom way... That's a good idea having a drupal base. |
| [14:36:13] | <mstenta[m]> | Yup! :-) |
| [14:53:05] | <calbasi_matrix> | Done: https://www.drupal.org/project/farm/issues/3069161 |
| [16:47:40] | * JustTB has quit (Remote host closed the connection) |
| [16:49:12] | * JustTB has joined #farmos |