Alright, so let's begin.
And then, so last week we looked at the data, and so we may, I guess, if you want we could
try to read in that transactions data and see if we have any better luck, and then I
could try to save it in a better format for you.
And then, roughly the plan today was to talk about APIs.
So I've put together a handful of public APIs that we can use and we can make requests too.
So let's, why don't we just jump in, well, how about you Charles and Jake, which would
you prefer to start with?
Here is David.
There's a good amount, I'm not going to excessive.
Good morning David.
Good morning.
You know how large the actual file was that you were trying to read in?
It's supposed to be like 24 or 26 gigabytes, but when it gets read into the CSV editor,
it expands.
And I don't know if that's part of the problem, because it's corrupted, or if that's what
the CSV file expands that much when you read it in.
Well, let's just take a quick look at that here.
Let me just condense some of these things here, and then.
It might be just the editor.
Now I tried like two different editors.
Really?
The main problem is that pandas won't read it in.
If you open it up in notepad, does it open, or a text editor, does it expand like that?
You haven't tried reading it using a text editor, I've been using a CSV reader.
I would try with notepad, something that just reads text, and it isn't supposedly specialized
for CSV, and see what happens.
That would help isolate whether or not it's the editor, or whether it's something to do
with CSVs.
I've never seen that occur with just notepad.
So just for five minutes, we'll just take a quick look at it.
So here I'm going to drop some links in the chat.
And so these are the data links.
And Jake is new here.
He's my.NET developer.
Oh, awesome.
So I don't know if he's on the audio or not.
Well, I'm here.
Okay.
Good morning, Jake.
Good morning.
I should have shared this last time.
Charles was smart to bring this up.
So this is the data guide for the data.
So we...
That was real helpful.
So you know the fields that we're looking at.
Okay, so say one more time you were looking to read in the transfers.
Now the inventories.
Oh.
Okay.
Two gigs.
So it should be manageable.
Well, it is zipped.
So you're going to...
It's going to uncompress the zip file.
It'll probably get bigger when you uncompress it.
How big is the CSV after you unzip it?
It's like 24 or 26 gigabytes.
Okay.
So we'll look at this maybe at the end of the presentation.
So we'll just dive straight into APIs and then maybe at the end we'll see if we can't
have any luck parsing that for you, Charles.
So some of the things I wanted to share with you today.
First, just wanted to just spend...
So here's the agenda.
So I was just maybe going to do five to 10 minutes of introductions, but it looks like
we've got the usual crowd here, plus Jake.
And so it's good to see you all.
And then I guess real quick, Jake, you said you're a developer?
And then could I just ask, do you have any particular interests in the field of cannabis
data that you're looking to...?
We're interested in developing an add-in for Acumatica's ERP so that all the touch points
for the growing and manufacturing processes can all be... have all their IDs captured
from the API and then be able to send the information back to the state through the
API as those transactions are occurring.
So we sell that particular ERP software, so we know that side.
Jake's done a lot of development within the application in C-sharp.
So we're just kind of looking and exploring how we could potentially build something that
would let the ERP system do everything that growers and processors needed to do, including
the communications with the state API.
Excellent.
So that's kind of a... he's working on a major project right now for investment asset accounting
within our ERP, but that's going to be... we're going to have a viable product on that
pretty soon.
And then he's going to be looking at developing this next big product of ours for the cannabis
industry to allow us to target cannabis growers and manufacturing or processing plants.
Well, you're in the perfect place and we're glad to share as much as we know.
So as you hit on, APIs are used by almost... promote by pretty much every state that's
adopting a cannabis program.
So it looked like, for example, Oklahoma was maybe going to go without, and then they adopted
metric recently.
So and then I put a list of states here to watch out for, for public data, because these
are states that are at least making efforts to start providing public data, even if at
the moment there's the infrastructure is still in development.
So for example, Washington, you can watch there's, I was just pulling it up over here,
but... but we'll dig into some of these others.
So Washington has a Socrata endpoint.
It was rich with cannabis data and it, they've recently announced that they're going to have
efforts this year to start populating more data there.
So something to look out for.
And then one of the ones that's up and running, well, so we'll stay tuned.
Okay.
But one of the ones that is up and running is we have the pesticides from Oregon.
So this will just be a quick example of how you can get data through Socrata.
Okay.
So I'll put the link in the chat.
And so it seems that a lot of these states are adopting Socrata for sharing their data,
all, you know, slowly, but slowly but surely.
And so for example, here's an effort by Oregon to share their pesticide lists.
And so this is a public API endpoint.
So really if you hit this URL with, you know, any programming language or even in the browser,
you know, you should just get a big dump of data.
And then, so that's not too meaningful there in the browser.
So what we've done here is we'll start a new file just to do everything fresh here.
So we'll go ahead and use the request package for Python.
And then we'll be hitting the pesticides endpoint.
And we use requests.get to get that endpoint.
And then a couple tools that you could potentially look into using if you're not trying to
A tool recommended to me was Postman.
So you could look into using Postman.
But just for this tutorial, I'll be sticking here in Spider.
So you'll know you'll get a successful response if you have a 200 status code.
And so then you can then get that actual data.
And so this is just going to be a giant list of dictionaries.
So just so we can, you know, clean this data up and save it to Excel, because I should
have mentioned the point of this exercise is, you know, basically we're just trying
to get as much cannabis.
Here I said lab results, but we'll just generalize to data.
So our goal is to get as much cannabis data as possible from public APIs and then save
it to Excel.
Or, you know, your favorite database.
So that way you can make it useful to yourself.
So we'll need pandas.
And then what I'm doing here is you can turn a list of dictionaries into a data frame
by simply passing it to pd.dataframe.
And if you look at the data, because that's the first rule of data science, look at the
data.
So if you look at the data, you'll see that everything's in all capital letters.
So just for the to save people a headache, you can check out the link here to Stack Overflow,
where we're basically just turning everything to title case.
So that way the data is prettier.
And so then we can save that to Excel.
And you have a nice list of pesticides that may be used on cannabis products.
So essentially, if a cannabis producer was going to use, you know, Velofir, then they're
going to want to know what the active ingredients are and watch for those.
So for example, if you're using anything with Azera, you're going to want to watch out that
your products don't fail for pyrethrins when being tested.
I think flour may not have a limit on pyrethrins in Washington state, but concentrated products
would.
So if you're growing products that are going to be getting concentrated, then you may want
to be careful with your application of any pesticides with active ingredients that you're
trying to avoid.
So that's just a quick look at those pesticide data points.
And just to go ahead and show you one more API, just for fun.
So this is an API that I've put together that allows you to get lab or actual lab data.
So at the moment, you can just get information about particular labs.
So I'll put the link in the chat here.
And so we're going to do a similar thing where we're going to get the data.
So here's the labs endpoint, api.kinlintx.com slash v1 slash labs.
We're going to use requests.
And then we're going to get the JSON.
So I have 140 or so in the database at the moment.
And then I've got a total of 225 that I'm looking to add.
So if we just look at this data, so we're returning a dictionary.
And the dictionary has a single key of data, which has all the lab data.
So what does it look like in full?
A big messy dictionary.
But you can get particular.
So that's just a singular.
So we can look at it a slightly nicer way.
And so this is a singular lab.
So what's their name?
So that's peak analytical.
I think you can get things like full address.
If you get, yeah, it's formatted address.
So that way you can get the full address.
And then I think there's even some nifty data points on here.
So I think I've got, yeah, so some of these labs, I've gone ahead and geocoded them for
you.
And then when possible, I've got their website, their image, or a link to their image, and
then their phone number where possible.
And so these are things that these labs would like public.
So it's on their website.
They want people to get their phone number.
So this is just an easy access way to get this data.
And then once again, you can just dump it to Excel.
So that way you have a nice list of, and so these are all the labs that test for cannabis
in any given state.
So if you're looking for labs in Washington, you can find essentially the general information
about these labs.
And so stay tuned because the idea is to gradually build out this API endpoint to provide the
actual lab results, which we were working with in the last exercise.
And this is a public project, so if anyone wants to lend a hand, you're more than welcome.
So that's that endpoint.
And then just to show you just a myriad of some of the possible data points out there,
if you go to Socrata, you can find just lists of public data that can be accessed all in
similar formats.
So then the pesticide data, here is an interesting, so I'm just going to share these API APIs
with you and then we can maybe spend a minute to talk about the Washington state APIs or
any other traceability system that you may be interested in.
Yeah, and I was thinking about it too.
What we were probably going to do is in the Acumatica ERP, we're going to add custom columns
to their data for the, we'll probably still track our own ID numbers, but we'll create
an extra column, which would be the state ID number for all of the different records,
whether it be vendors or batches or plantings, all of the different things that we're required
to get ID numbers from.
We're probably going to store in separate columns, and that way we can support different
states.
So if we have a column for the Washington ID versus the California ID versus the Colorado
ID, then we can build our APIs, our connections to each of the different state APIs, depending
on which state that they're in, and leave the others blank, because we can have a setup
option that says what state they're in.
Well, awesome.
So let me put this on pause for one second, and then I'm going to grab my tea, and then
we can dive into this LEAF user manual.
I like it.
I'm going to grab coffee.
All right.
Coffee break.
Awesome.
Let's grab tea.
One second.
Charles, where are you located?
Portland.
Awesome.
Two hours down, I-5.
Yeah.
So did you have power up there?
We never lost it in Tacoma.
There were some areas around us when we had the snow.
Fortunately, the snow only lasted a day or two, and we're pretty lucky.
I also, I'm a paranoid guy who believes the grid is going to become more and more unstable
in this country, so I went out and got a natural gas-powered standby generator for our house.
So even if the power does go out, I can still be online helping clients.
As long as we don't have the 10.0 earthquake that takes out all the gas piping, breaks
all the gas pipes, we'll be fine.
I can't do anything about that, but if the 10.0 earthquake comes, we're pretty much all
screwed.
Yeah.
Well, awesome.
So thanks for bearing with me.
I noticed the tea was boiling, so I had to go get that.
But cheers.
Cheers.
All right.
What we were looking to see is if you can give us an example of how you would connect
to their API and get back an ID number for, let's say, something as simple as a vendor.
We're adding a vendor.
We need a state vendor ID with the state of Washington, right, assigned by their API.
Sure.
So how would we call and do that?
I'm assuming there's some kind of authentication piece first.
Ooh.
Go ahead.
So why don't you...
Unless you want to...
Yeah, you're right.
There is an authentication piece.
So why don't we jump into this documentation and we'll go through it.
Okay.
And you can hit me with some bullet points and I'll just sort of mock an API request.
Okay.
And then I was trying to...
So I learned about Postman just for hitting API endpoints.
Uh-huh.
It looks like you can actually mock API endpoints here on Postman.
Really?
Exactly.
So if you would like...
I didn't have enough time to get it prepared for this week, but we'll start going through
the document, the leaf traceability system API here.
Okay.
And essentially, gradually build a mock API here for the leaf data systems because we've
got the data here.
So it would maybe be cumbersome to do a full mock, but you could potentially take a random
sampling out of all of these.
Because these are essentially all the endpoints.
Right.
These are all the things that are having to be reported, right?
So there should be a vendor one there.
So let's just scroll through.
Last time I looked at this documentation, there was something here, but I could not
get through it.
So I'll kind of just give you a brief overview here.
And then, like I said, over the course of the next couple of meetups, I'll essentially
random sample these and we'll essentially create a mock of the Washington State API.
Okay.
That way, exactly, people like you who are building a company to interact with the traceability
system can get some practice in and figure out how to do things.
So what is the traceability system?
So, essentially, they're tracking things from when it's planted to when it gets sold.
So I may send you a diagram of this where I've written on it because there's some
interesting things you can add to this.
So essentially, every user, would the users be like vendors and other people that
you're interacting with?
Good question.
So everybody who uses the state traceability system creates users.
So all licensees create users.
So that would be the retailers, the producers, the processors, and the labs.
Okay.
And then once you create your users, you essentially create what are called areas.
So you're basically creating a blueprint of your lab.
So...
Okay.
Kind of like a warehouse having locations or bins within a warehouse, maybe.
Exactly.
And so this is for traceability purposes.
So you don't want to trip yourself up because these are things that you define.
So if you're a retailer, you may have the front room, the back room, or if you're a
producer, you may have flower room, veg room, or if it's a large cultivator, they may have
flower room one, flower room two, veg room.
That's what I'm familiar with.
I worked with Tilray back when they were first getting started.
And that's what they kind of had.
They had a whole bunch of different rooms for different stages.
And this is a word of wisdom is always prepare for multiples.
Yeah.
Even if it's a small company and they may only have one user, one area, or even one
licensee, there are large companies out there.
So always be prepared for multiples.
So be prepared for multiple licensees.
Just, yeah, so that's the big one, multiple licensees.
That's the trickiest thing to prepare for.
But if you can handle that, then you're golden.
Okay.
So, and then this is where I would like to start making some notes because essentially.
Well, we could just do an ad of an area.
I mean, once we spec out the process for submitting your area and getting back a state
ID for that area, I'm assuming that's how the API works.
Because they've got to keep some unique identifier for each of the records you're
creating, right?
Ooh.
So before we get head over heels, why don't we essentially.
So unfortunately, we won't get responses, but I can still show you how to set up the
requests.
Okay.
Perfect.
So that way.
We can do that with anything, I guess.
Yeah.
That's exactly.
So we'll just start from the beginning and just work our way up.
So.
Yeah.
Let's see if we can't split this up nicely here.
And let's see if we can't get rid of this.
Bookmark thing.
All right.
So how I would do it in Python.
So, of course, you're just going to need to the base endpoint here.
So.
That's going to be.
Unfortunately, some of the things are hard to copy and paste.
So essentially, your base endpoint is out pasted into the chat here in a second.
But it's HTTPS.
W a test.
So this will be the test environment.
That leaf data systems dot com.
API V1.
And so that's basically just the API.
So.
So I think you would essentially just make a.
So say you wanted to get users, you would just.
You would do that, but you're going to need some sort of authentication.
So so we got a little ahead of ourselves, so let's go back.
And actually.
I thought I saw third party developers.
At the bottom.
Go down a little bit farther.
I thought there was a manual third.
If you have a third party integrators web form.
Never mind.
Here we go.
So these are essentially the headers you want.
So.
The way you pass authentication in your quest.
I'm sure you I'm sure you know, but part of me is just speaking to a general audience here.
So bear with me since I'm sure you know, but you know you pass you pass in some some headers here.
And this is basically going to be a dictionary where you would pass in your API key.
And so this may be pro this is programming language specific here, so the way you pass your headers will slight will vary slightly depending on your approach.
But these are essentially the fields that you would want, so you want X and J.F. so that's M.J. freeway, which is the original name of.
Of a Kerna, which is the the parent company.
Of you know, leaf data systems, which is the traceability system, you know, in Washington state.
So so you hear people use a lot of terminology so that you may, you know, hear people in Washington call this M.J. freeway.
You may hear them call it leaf data systems.
You may just hear them refer to it as traceability.
So I heard M.J. freeway.
Exactly.
And so.
And then you get your so you're going to need to get your API key. And this is actually, you know, one of the easier parts. So once.
So you'll apply.
To become a software integrator.
And then they'll give you access to the environment.
You go back up to that list. I think I may have already applied for that.
No, I guess not. I can't software is not on the list. OK.
Well, and you know, how they may just not have updated their list, so it could be worth shooting them an email.
But.
In the the API system, I believe you can.
So you'll have to get your API key from within the system itself.
I'm sure that you'll have to go to like settings or something like that user profile and find your API key.
And then.
The the MME code is a little tricky here.
So.
So, in fact, the the MMEs are essentially their own endpoint.
So one thing you will actually want to, you know, familiarize yourself with, because this is going to be useful is you're going to want you're going to want to hit this.
MMEs endpoint here.
And.
So.
So let's just do like a quick mock of of what this would look like.
You've got your base.
Coincidentally, you're going to have to already know your company's MME ID. And so the way you would essentially go about that is there is a user interface to the leaf data systems API.
So what I would recommend is essentially just using the user interface.
Finding your MME ID or even.
Yeah.
So that's the tricky part. The chicken and the egg.
So you need to see essentially.
So that's what I would recommend. Use the user interface. Get that first MME ID.
And then essentially.
We would have the client look that up for themselves, right? And enter it in, store it in a table somewhere that we could reference it going forward.
Well, exactly. So if you're coming at it from a business point of view, so you're basically going to need your client to enter in their API key and and their MME code in your system.
And.
And so if you look here.
The MME code is the global ID in this response.
Oh, it's not the idea. It's the global ID.
Exactly. And this is different than their license number.
So their license number will actually be down here.
In bio license number.
Got it.
And it may or may not have an an alpha num.
It may or may not be alphanumeric.
So it may have, for example, an M in front of the number if they're a manufacturer or an R if they're a retailer.
Gotcha.
But essentially, this is a little bit of point of a confusion because you'll need this MME code as you're going through the various work as you're going through the workflow.
So for different endpoints, you may need that ID.
And it's not the end of the world, but it's just, you know, you just have to either have this saved in your database or, you know, hit the MMEs endpoint and get the global ID.
Because, for example, it may be used when you're transferring products from, you know, from one one company to the next.
Right. Exactly.
Okay.
So we get an MME and then next in the flow was areas.
It should be like a submit for the area. Right.
Yeah. Okay.
So essentially we've got that.
You'll you may even end up creating creating your users in the user interface.
That they may or may not exist, but you can also make them programmatically.
And so that you have a or do they provide in their documentation example of submitting a user ID create type function.
Or is it just look up with yet.
Actually, I'm on the field.
You know, I.
I want to say there is there should be a post ability, but it's not in the document.
It's not right. They don't I didn't see anything in there with the post documentation.
So I'm wondering if the users may have to be created through the user interface.
So that is that is a possibility because there are.
But you've got to have some ability to post for every transaction for every lot.
Right. The lot number or the lot ID has to be assigned by the state.
So we have to be able to as we're creating lots or as we're creating even areas.
Right. The areas are user defined.
There's got to be a way to do a post on on this to say, give me an ID for this area that I'm going to call, you know, flower room one.
Right. I mean, that's what APIs have.
They have gets and posts.
So it seems crazy to me that they're not providing that.
Let's see.
Well, they have a create. OK, there's create.
Yes. So that's a good question.
So that's one that I may need to try to discover an answer for you for next week, because so, for example.
Oh, there it is.
Yeah. So the areas are created just, you know, your the areas are one of your simpler objects, really.
So, you know, you're just doing.
You know, once again, so well.
So the areas will be a post.
So like you, you know, like you said.
And then, you know, base plus areas.
And then I want to say you can just pass, you know, data.
Yeah. The only thing that in my mind that I'm thinking there needs to be does the authentication in the first part where you do the base and then you do the headers equal.
Does that essentially accomplish the authentication so it knows which licensee is creating the area?
Right. So I guess. Exactly. Because you're only your data that you're.
Yeah, the data you're passing in there, you're essentially just passing it.
Addict, you know, an object here, you know, that just area.
And it's actually a list of areas where, you know, you could create one after the other.
You do one or one post and give them all your areas.
Exactly. So that way you can, you know, you can populate, you know, you can populate the whole, you know, the whole facility in one shot.
We probably do it one at a time, so because it would be on the same of the area.
With an act, Madoka. Yeah.
And that was my sort of comment is I would take increased functionality.
I mean, increased like fields and endpoints over, you know, necessarily being able to do multiple, multiple areas at a time.
But, you know, from a code standpoint, it just makes sense to do it one each one, have a post for each one.
But nonetheless, I was even maybe telling someone the other day that I'm a glass half full type of person.
And there is a lot of complaints about, you know, the Washington State traceability system.
But, you know, at the end of the day, you know, you just have to use what you're given and, you know, make, you know, if you have lemons, you know, try to make lemonade.
So it's like, you know, it is what it is.
But, you know, you can still interact with it programmatically.
So that's the important part. So, yeah, in a perfect world, we'd be like Canada where they don't require you to use as extensive of a reporting system.
In fact, I don't even know if they have an API that you have to comply with in Canada with, with Tilray.
They approached it from the standpoint of you take care of the tracking.
But when we come in and audit you, if anything, if we go to a room and compare it to what the tracking system says and it's different, you lose your license.
And I kind of appreciate that because, you know, if you have a good, if you have a good system, you it's a lot easier to, you know, implement manufacturing and ERP and with cannabis up in Canada because of that.
Right. I mean, you don't have to make an API call for everything that you save, you know, all these different records.
You just have to prove that you have traceability within your own system. And there's a big hammer if you don't, you know, nobody wants to lose a lot.
Tilray doesn't want to lose their license to operate in Canada. Right.
Well, that's a that's a real interesting perspective because you're right, because, you know, they still sort of have, you know, the panopticon where, you know, you don't know when you're going to get inspected.
Right. It's like the IRS, right. It's kind of a, hey, we're going to trust you to, you know, first you got to prove you have a system right before you can get a license up there. So we had to prove that we had traceability with the financial system.
But once you prove it, you get your license, then they just do, you know, occasional checks.
And it's that, you know, fear in our in our heads of that occasional check being catastrophic. Right. That's why we have insurance.
We want to make sure we don't lose everything.
And so it certainly makes implementing cannabis, you know, for companies in business software significantly easier up there.
But like I said, it is what it is in the state of Washington. You got you got to deal with what you got. And well, because we have kind of a screwy country where every state is different and every state potentially has a different API.
You got to work with that too. So my perspective is,
you know, so there's a point of contention in Washington because the state views it as, you know, this is for traceability, you know, just to make sure that, you know, nothing's going out of the system.
But, you know, some people rely on it as sort of like an inventory management system.
And, you know, your inventory is there, but it's not really, you know, managing anything.
Right. So, so, you know, most of them are using QuickBooks and then using the state API for their tracking.
Exactly. So I kind of approached it as, you know, run the business first and then make sure that you're compliant with traceability second.
Just, you know, just so you're not, you know, building your business too much off of you too solely
because you don't want to, you know, you don't want to get stuck in some of the paradigms that they've necessarily chosen for their system.
And then it seems I don't actually know too much about metric, but it seems that it seems maybe it's slightly more features.
Then it seems that people are maybe relying on it as an inventory management system where that's what I've heard.
I've heard it's much better not only to integrate with, you know, from a standpoint of development, but also I think documentation is better on the metric system as opposed to MDA freeway.
I think MDA freeway kind of has their own ERP software that they're allowing people to use and that's probably what you mean by them tracking the inventory in the API is they offer kind of a web ERP system as a financial system and a warehouse system and a manufacturing system kind of all within their software that you pay for to use.
But it's still same thing. Even if it's made more features, I would still be hesitant to, you know, build my business or software entirely based on their paradigm because, you know, everybody wants to do things differently.
So what do you think?
What are the possibilities with the freeway? It's a good question.
I don't have my ear quite to the ground these days, but I don't know.
It seemed for a second that they may be looking into alternatives, but I don't know. It seems to my personal perspective is does seem like there's a lot of complaints and some of them may be legitimate. But at the end of the day, at least it's a system.
So I think really like realistically the alternative would be like going back to like Excel workbooks and things like that, which you don't ever got a metric.
I don't. I actually don't know enough about that. So, but for some reason, just what from what I've gathered, maybe it's too expensive or I'm not sure if that's maybe it's just doesn't seem like they were really considering that.
But like I said, I don't really have that much of a, you know, I'm not I would love to be a fly on the wall sometimes.
But, but can you show us a little more of the postman interface that kind of caught my eye?
Yeah, so, so here, why don't I kind of just show you a bit of this and then for next week, I'll have some of this up and running. So that way we could we could actually do some some mock create areas.
And since it's a mock, we could create post requests for the users. Yeah, whether the actual system has that or not.
Okay, cool. But, but I don't I was actually recommended this by by people I work with, they use, they use postman for for essentially, you know, essentially just developing API.
So when you're building an API and you need to test it, and you just want to, you know, hit your endpoints, you know, this is just, you know, essentially, you know, I've created an account here just today, but it looks like you can, you know, make requests.
So let's see. So create a request.
So let's see if here in two minutes we can't figure this thing out real quick. So,
so I think yeah, you can basic. So let's do the pesticides one just because that was, you know, pretty simple endpoint to, you know, just to see if it works. I think you can basically.
Yeah. So, nice and it'll pretty fight it for you. So, so, you know, so you'll need to, you know, go to postman.com create an account.
And then I from the dashboard.
I can maybe type up some instructions for you, but
yeah, exactly.
So, so the answer. This is a pretty rich tool. Like I said, I haven't. I still need to explore it yet because like I said,
yeah, I bet if you if you looked at the documentation, like if there if we were looking at the one for the state of Washington on the users or the areas, I bet you have to type in manually the key, the parameter keys based off the documentation manual, but then yeah, you should be able to.
Yeah, so essentially
where did I have this guy, you know, so you know, essentially,
so essentially, you know, you'd make your post, and then, so I wonder, your key would be area.
And then I wonder if there's any way to make this like a list.
So, maybe tricky using postman so I may need to figure out.
Yeah, no worries.
But, so how about this how about yeah for next week, I'll start playing around with this and we'll just mock some of these, some of these endpoints because they're relatively simple and they're giving us everything we need because you know in this guide, you basically have your request.
You're the, whoops.
You know the, the
Yeah, don't worry about it. We gotta get going.
Awesome. Awesome. Thanks for coming everyone.
Bye.
See you, Charles. Oh, yeah. Oh, why don't I.
Because, like you said I'm a little worried about that memory. So I don't want everything to crash well on.
Basically, my fear is that everything was going to crash right when I try to read in that data set. So, if you'd like I can try to try to wrangle that and send it to you in a better format or more consumable way if, if you would like.
Yeah, that would be great.
I can read it in and you can chop off the like that corrupted column, but then when I go to save it is when it crashes.
Well, well, and say that one more time it was the inventories and the
the inventories, the plants one was corrupted but I was able to fix that.
Okay.
That one I was able to read in chop off the extra column, and then save it, but inventories, you can read it in, it takes forever.
And then I was able to chop off the column.
There was two extra columns. I was able to chop those off and then when I went to save them.
Then that's when it would crash.
Well, I'll try to tackle that today for you and send you send it send you either, either my findings or some results.
Okay, great.
All right.
Appreciate that.
All right, Charles. Well, I've got a full agenda today myself so I'm going to go ahead and give myself but it's awesome.
I'm talking about cannabis data with you so I'll look forward to getting back at it next week with you.
Okay, yeah, great. I'll see you next week.
All right, I'll be in touch.
Okay, bye.
Thank you.