Skip to main content

Options outside of ML

Today I wanted to share what I have done in a recent experiment to address an issue that has been quite rapidly getting out of control.  We have a responsibility of pushing out a number of catalogues on a week by week basis, and since the source information has got product labels truncated down due to the size of the original input field, we have got the manual task of renaming to their full displayed length.

Of course, we have got our ways of reducing the amount of manual updates on this, but we certainly could not pick up on most things as fast as a machine could.  It is not as simple as just a "find and replace" though, because while such abbrieviations as "sce" mostly means "sauce, it's never a one-size-fits all, and depending on the brand, they can also each have their own spelling.

I then came up with an idea; using some form of diff algorithm, and having a dictionary be learned associated with the products respective brand name.  The library I found is called "finediff", a simple implementation which breaks down the copy/find-replace segments in to op-codes.  By modifying the class's private function doFragmentDiff to public, this is the crux of how I have applied it to my application:

And there you have it!  What you don't see here is first just making a reference to the brand of the current product, but from the two columns, we are just storing what text we are looking for, and what to replace it with.  This is technically not machine learning, but on the surface, it kind of replicates the next best thing.

Hope this inspires.

Comments

Popular posts from this blog

Running NodeJS Serverless Locally

 So it's been a long time, but I thought this was a neat little trick so I thought I'd share it with the world - as little followers as I have.  In my spare time I've been writing up a new hobby project in Serverless , and while I do maintain a staging and production environment in AWS, it means I need to do a deployment every time I want to test all of the API's I've drafted for it. Not wanting to disturb the yaml configuration for running it locally, I've come up with a simple outline of a server which continues to use the same configuration.  Take the express driven server I first define here: And then put a index.js  in your routes folder to contain this code: Voila! This will take the request from your localhost and interpret the path against your serverless.yml and run the configured function.  Hope this helps someone!

question2answer Wordpress Integration

 Today I want to journal my implementation of a WordPress site with the package of "question2answer".  It comes as self-promoted as being able to integrate with WordPress "out of the box".  I'm going to vent a small amount of frustration here, because the only integration going on is the simplicity of configuration with using the same database, along with the user authentication of WordPress.  Otherwise they run as two separate sites/themes. This will not do. So let's get to some context.  I have a new hobby project in mind which requires a open source stack-overflow clone.  Enter question2answer .  Now I don't want to come across as completely ungrateful, this package - while old, ticks all the boxes and looks like it was well maintained, but I need every  page to look the same to have a seamless integration.  So, let's go through this step by step. Forum Index Update This step probably  doesn't need to be done, but I just wanted to mak...

Getting all deltas from Auth0

Before I get in to the solution of this article, let me tell you how it started and fill you in on the problem that arose.  I wrote a procedure to get daily deltas of users - those of which who had created/updated their account on the given day (and including the day before for good measure on the GMT timestamp).  The simple search criteria was just the following: updated_at:[yyyy-mm-dd TO yyyy-mm-dd] Simple, right?  the []'s being the dates are inclusive, while using {} would mean exclusively.  Auth0 lets you mix these on either side depending on your use.  While this is all well and good, Auth0 will limit the number of results (even with paging) to 1000 only. So, your first option is that you could have your procedure create a user export job, and then parsing through the results and eliminating those which do not meet your updated_at search criteria.  I can tell you first hand that eventually the amount of users will just get to be too much and cumb...