npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-red-contrib-ecolect

v1.1.0

Published

A node-red node for natural language matching using Ecolect.

Downloads

11

Readme

node-red-contrib-ecolet

A Node Red node that is a wrapper around the Ecolect natural language matching library.

This node takes a plain text string and tries to match it to one of the configured intents using fuzzy pattern matching of training phrases. The node can also extract values from the string such as numbers, dates, times, and sub-strings.

Messages for each topic are sent on separate outputs so that they can be processed by a flow specific to that topic. The last output is always for messages that the processor could not recognise.

The output message contains the matched topic and the extracted values. All other message properties are passed through unchanged.

Configuration

The node configuration provides the information to train the natural language matcher about the topics it should attempt to match. The configuration for each topic consists of:

  • Topic - the name of this topic
  • Values - the name and type of values to be extracted from the message.
  • Phrases - a list of phrases that would match this topic. Values to be extracted from the phrase are identified by enclosing the value name in {} brackets.

The natural language matcher uses fuzzy logic to determine the match between the message text and the specified phrases to identify the best matching topic. Simple variations of specified phrases should be matched but the more phrases that are specified the better the matching. If you use enumerations for values that have a small set of known values, then the matching will be much better.

Example

  • Topic switch
  • Values
    • room - enumeration ("bedroom", "kitchen", "study", "kids bedroom")
    • item - enumberation ("light", "fan", "radio", "heater")
    • state - boolean
    • when - date-time
  • Phrases
    • turn {item} {state} in {room} at {when}
    • turn {state} {room} {item}
    • turn {room} {item} {state}

Matches the following phrases:

  • turn on kitchen light at 9pm
  • turn on bedroom light
  • turn bedroom light off