| [11:00:59] | <rjv23[m]> | hi, great news about the IoT integration, we are working toward a similar solution and had checked into the openpipe development, so very interested to see how the OpenAtrium development works |
| [11:02:01] | <rjv23[m]> | is it possible to let the user set the asset ID, like a part numbering system? |
| [11:03:43] | <mstenta[m]> | No the asset id is a database primary key (auto assigned and incrementing). But I would like to generalize the animal tag id field for other asset types, so that you can do exactly what you described. |
| [11:04:06] | <mstenta[m]> | So you could assign one or more unique tag IDs to assets |
| [11:04:44] | <mstenta[m]> | Eg: part numbers, qr codes, barcodes, Eid/rfid etc |
| [11:07:14] | <rjv23[m]> | tks, |
| [11:09:01] | <rjv23[m]> | we are using farmOS in a growroom, and I have am looking for a way to differentiate assets like an erp system would , with inventory categories and code |
| [11:09:30] | <rjv23[m]> | check us out at www.taiwanhydroponics.com |
| [11:09:43] | <mstenta[m]> | Cool! |
| [11:10:40] | <rjv23[m]> | really apprecite the work you have put in on this system |
| [11:16:23] | <rjv23[m]> | it is a great base for us to get started on |
| [11:16:59] | <rjv23[m]> | how is your progress going with upgrading to drupal 8? |
| [11:18:22] | <rjv23[m]> | I check your pages, do you have a target schedule for the upgrade? |
| [11:27:26] | * cpm has joined #farmos |
| [11:30:41] | <mstenta[m]> | Glad to hear it! |
| [11:31:07] | <troym541[m]> | mstenta: rjv23 so far with the IOT-Atrium build I have been using the entit_ytype/id# generated form ECK module to route my data back and fourth, but I also tried using the UUID module with its out of the box integration with REST API module and so far both methods work to push/pull data from objects. I think the UUID module will be the most efective methode for creating a more secure way to tag/ID devices/data_objects |
| [11:31:08] | <troym541[m]> | as I move forward with the IOT-Atrium build. |
| [11:31:20] | <mstenta[m]> | No target date. If we get some sponsors behind it then we will ;-) |
| [11:31:42] | <troym541[m]> | *entity_type/id# |
| [11:32:16] | <mstenta[m]> | troym541: UUID++ |
| [11:32:53] | <mstenta[m]> | We'll probably do all of the above |
| [11:33:03] | <mstenta[m]> | Auto incrementing primary key |
| [11:33:09] | <mstenta[m]> | UUID |
| [11:33:46] | <mstenta[m]> | And arbitrary tag IDs (for things like linking assets to IDs outside the DB) |
| [11:34:12] | <mstenta[m]> | (eg animal ear tags) |
| [11:34:29] | <troym541[m]> | https://www.drupal.org/project/uuid |
| [11:36:03] | <troym541[m]> | uuid was build into OpenAtrium by default and it has integration with Services module. |
| [11:37:52] | <mstenta[m]> | Yeah! |
| [11:38:04] | <mstenta[m]> | And in D8 UUIDs are included |
| [11:38:37] | <mstenta[m]> | We could consider adding the module to farmOS in D7 if there is an upgrade path supported |
| [11:40:17] | * farmBOT has joined #farmos |
| [11:41:20] | <troym541[m]> | Not sure about the upgrade path, i will look into it later today. But that sounds great, it seems like an easier way to be able to find and sort things out, with out making it so easy for someone to guess your endpoint url. |
| [11:45:39] | <troym541[m]> | I was planning the use the uuid to assign a tag to objects between sites, like we could generate the uuid in FarmOS or Erpal, and then create a filed in IOT-Atrium called Assigned-UUID (or something) and use that to id objects across the different systems. |
| [11:47:03] | <mstenta[m]> | Cool that makes sense |
| [11:49:17] | <rjv23[m]> | regarding the sponsor, how can we contact you? |
| [11:49:58] | <rjv23[m]> | you can also drop me a line thru the email on the website and we can discuss |
| [11:50:30] | <mstenta[m]> | hello@farmier.com |
| [11:50:57] | <mstenta[m]> | rjv23: send me an email! :-) |
| [11:51:03] | <rjv23[m]> | tks again |
| [11:51:30] | <mstenta[m]> | I'm not at my computer right now (phone) but look forward to talking |
| [12:17:02] | <rjv23[m]> | email sent |
| [12:17:22] | <rjv23[m]> | will check bak in a few days if no reply, tks |
| [14:00:16] | * cpm has quit (Remote host closed the connection) |
| [15:17:25] | <troym541[m]> | mstenta: Regarding upgrade path from UUID D7 to UUID D8 if found the following on the project page. |
| [15:17:58] | <troym541[m]> | "UUID Drupal 8 |
| [15:17:59] | <troym541[m]> | This module doesn't need to be ported to Drupal 8. All core entities in D8 support UUIDs. The UUID URL is currently under development for a future release of Drupal 8 core (see #2353611: Make it possible to link to an entity by UUID)." |
| [15:19:30] | <troym541[m]> | The only mention of any upgrade issues refer to upgrade from 6 to 7. Nothing about any issues from upgrading from 7 to 8. |