TextExtractor: Easily Extract Data From Text

TextExtractor is a simple DSL for extracting data from text which follows a simple, consistent format, but which is not a well known format such as XML, JSON, or YAML, and for which conventional regular expression syntax might be too bulky or hard to follow. It is inspired by the TextFSM project (https://github.com/google/textfsm).

Installation

Ruby 2.1 or later is required. There are no other dependencies.

Add this line to your application's Gemfile:

gem 'text_extractor'

And then execute:

$ bundle

Or install it yourself as:

$ gem install text_extractor

TextExtractor requires Ruby 2. There are no other dependencies.

Example And Explanation

TextExtractor instances are wrappers around regular expressions. They are defined using a simple DSL that breaks the regexp into values and records, and they emit arrays of hashes when applied to text.

Here is a simple example to extract some information from a BGP router which is provided in a format that looks like this:

BGP neighbor is foo, vrf bar
 Remote AS 1243
 Description: foobar
 For Address Family: spam eggs
 BGP state = confusion
 Policy for incoming advertisements is myinpolicy
 Policy for outgoing advertisements is myoutpolicy extra
 31337 accepted prefixes, 42 are bestpaths
 Prefix advertised 23, suppressed

BGP neighbor is kilroy, vrf washere
 This neighbor is down. Nothing to see here, move along.

BGP neighbor is bar, vrf foo
 Remote AS 1243
 Description: barfoo
 For Address Family: beer 99
 BGP state = disarray
 Policy for incoming advertisements is otherin 22
 Policy for outgoing advertisements is otherout
 1337 accepted prefixes, 40 are bestpaths
 Prefix advertised 0, suppressed

The extractor is defined in a block passed to TextExtractor.new:

bgp_neighbors = TextExtractor.new do
  # values go here
  # records go here
end

The first part of the definition is declaring the possible values. Each value consists of a name and a tiny regular expression:

  value :bgp_neighbor, /\S+/
  value :vrf_name, /\S+/
  value :asn_remote, /\d+/
  value :description, /\S+/
  value :bgp_state, /\S+/
  value :address_family, /\w+\s+\w+/
  value :policy_in, /\S+\s*\S*/
  value :policy_out, /\S+\s*\S*/
  value :prefixes_received, /\d+/
  value :prefixes_advertised, /\d+/

Within an extractor definition, each value must have a unique name, since they will eventually be placed into a hash together.

The regexp associated with each value is interpolated into one or more record regexps, so it's important that they are not anchored here.

The other part of the definition is defining one or more records. A record is just a regular expression, but it uses a special syntax:

  record do
    /
    BGP neighbor is #{bgp_neighbor}, vrf #{vrf_name}
     Remote AS #{asn_remote}
     Description: #{description}
     For Address Family: #{address_family}
     BGP state = #{bgp_state}
     Policy for incoming advertisements is #{policy_in}
     Policy for outgoing advertisements is #{policy_out}
     #{prefixes_received}\s+accepted prefixes,\s+\d+ are bestpaths
     Prefix advertised\s+#{prefixes_advertised}, suppressed
    /
  end

  record do
    /
    BGP neighbor is #{bgp_neighbor}, vrf #{vrf_name}
     This neighbor is down. Nothing to see here, move along.
    /
  end

Adding a second record means that there are two possible formats, equivalent to alternation (|) in a standard regexp (and this is how it is implemented). Of course, it is possible to have any number of records.

The record regexp syntax has a few differences to standard regexps which are intended to improve readability.

First, the interpolated sections (#{value_name}) will match the same-named values defined previously, and the matched values will be placed into a hash, one per instance of the record in the input. This is implemented using named capture groups, but is more concise and modular.

Second, whitespace at the beginning or end of the regexp is removed, but not internally, which keeps the regexp visually similar to the text it is meant to match, in contrast with an extended regexp. The extended, case-insensitive, and multiline options will be honored if they are used.

Third, record regexps are unindented according to the indentation of the last line, so it's possible to nicely represent an unindented section of text in indented code, or an indented section of text, by indenting the internal regexp lines relative to the closing /.

Now we can run the extractor on some text with TextExtractor#scan:

bgp_neighbors.scan(text)

Successful output will be an array of hashes. For our example, we can expect the following data:

[
  {
    bgp_neighbor: "foo",
    vrf_name: "bar",
    asn_remote: "1243",
    description: "foobar",
    address_family: "spam eggs",
    bgp_state: "confusion",
    policy_in: "myinpolicy",
    policy_out: "myoutpolicy extra",
    prefixes_received: "31337",
    prefixes_advertised: "23"
  },
  {
    bgp_neighbor: "kilroy",
    vrf_name: "washere"
  },
  {
    bgp_neighbor: "bar",
    vrf_name: "foo",
    asn_remote: "1243",
    description: "barfoo",
    address_family: "beer 99",
    bgp_state: "disarray",
    policy_in: "otherin 22",
    policy_out: "otherout",
    prefixes_received: "1337",
    prefixes_advertised: "0"
  }
]

Extracting Non-String Values

A block passed to value will specify how the extracted string should be interpreted. In the above example, were we to use the following value definitions:

value(:asn_remote, /\d+/) { |str| str.to_i }
value(:prefixes_received, /\d+/) { |str| str.to_i }
value(:prefixes_advertised, /\d+/) { |str| str.to_i }

These values would be converted from strings to integers before being returned. The first record of the output might include the following:

  {
    ...
    asn_remote: 1243,
    ...
    prefixes_received: 31337,
    prefixes_advertised: 23
  },

The following methods are available for extracting values from the Ruby core and standard library:

integer
float
rational
ipaddr (no prefix length)
ipnetaddr (includes prefix length)

Since such types have unambiguous string representations, a minimal Regexp is provided for each one. These defaults are highly permissive, so it may be desirable to provide stricter ones depending on your application.

Inline Values

It's possible to define a value inside a record expression using standard ruby named capture group syntax. To do this, pass an array of symbols containing the names of the capture groups from the pattern using the inline keyword:

TextExtractor.new do
  record(inline: [:foo]) do
    /
    before
    (?<foo>pattern to capture)
    after
    /
  end
end

Inline values can also be defined using the #.capture line directive (see directives, below). In this case, the inline keyword argument is not needed:

TextExtractor.new do
  record do
    /
    before
    #.capture(foo)
    pattern to capture
    #.end
    after
    /
  end
end

In either case, the inline method can be used to give a conversion block for the value:

TextExtractor.new do
  inline(:foo) { |v| v.strip }

  record do
    /
    before
    #.capture(foo)
    pattern to capture
    #.end
    after
    /
  end
end

Factories

By default, records are converted into hashes, but it's possible to specify a callable, Struct or other class to use in place of a hash.

extractor = TextExtractor.new do
  WhoWhere = Struct.new(:person, :place)
  Where = Struct.new(:place)

  value :person, /\w+ \w+/
  value :place, /\w+/

  record(factory: WhoWhere) do
    /
    whowhere #{person} #{place}
    /
  end

  record(factory: Where) do
    /
    where #{place}
    /
  end
end

Given this input:

whowhere Rene Descartes France
where America
whowhere Bertrand Russell Wales
where China

We should expect extractor.scan to return:

[
  WhoWhere.new("Rene Descartes", "France"),
  Where.new("America"),
  WhoWhere.new("Bertrand Russell", "Wales"),
  Where.new("China")
]

If the factory class is not a Struct subclass, then the extracted values will be passed to new as keyword arguments. In this case, the call to new can be thought of as looking something like

WhoWhere.new(place: match[:place], person: match[:person])

If the factory class is a Struct subclass, the extracted values will be passed to new as positional arguments in the order they appear in the extractor definition, but an explicit order can be given:

record(factory: { WhoWhere => [:person, :place] }) do
  /wherewho: #{place} #{person}/
end

The implied call to new can then be thought of as looking something like

WhoWhere.new(match[:person], match[:place])

Giving an explicit order in this way will cause positional arguments to be used even if the factory is not a Struct subclass. If you wish to use keyword arguments instead of positional arguments, pass the list of value names as a Set instead of an Array.

It's also possible to give a callable such as a Proc, Method, or any other object that responds to #call as the factory. In this case, the callable will be called with the hash of extracted values as the only argument.

If you wish to provide a default factory for every record in an extractor, you can use TextExtractor.factory:

CAPITALIZING_EXTRACTOR = TextExtractor.new do
  factory(->(r) { r.transform_values(&:upcase) })
end

Strip whitespace between lines

Some texts may use whitespace inconsistently. To ignore whitespace at the start and/or end of each line, pass the strip option. The three possible values are :left (ignore whitespace at the starts of lines), :right (ignore whitespace at the ends of lines), and :both.

For example, this extractor:

strip :left

value :this, /\w+/
value :that, /\w+/

record do
  /
  This: #{this}
  That: #{that}
  /
end

scans this text:

This: a
 That: b
 This: c
That: d

produces this result:

[
  {
    this: "a",
    that: "b"
  }, {
    this: "c",
    that: "d"
  }
]

The final newline

The record definitions in this document are all implicitly newline-terminated. This means that input documents must also have a newline after the last record, or else that last record will be unable to match. You can work around this problem by appending a newline to every input record, or you can define your extractor to do this for you with the append_newline method.

Consider a simple input document:

Char: a
Char: b

With the corresponding desired output:

[
  { char: 'a' },
  { char: 'b' }
]

This can be achieved with the following TextExtractor:

TextExtractor.new do
  append_newline true
  
  value :char, /./
  
  record do
    /
    Char: #{char}
    /
  end
end

This will work regardless of whether or not the input document contains a trailing newline. However, if append_newline is removed from the extractor definition, the trailing newline will be required.

By default, append_newline is not enabled, but this can also be changed on a system-wide basis:

TextExtractor.append_newline = true

Guarding against extraction loss

Over time, the texts an extractor processes may change without being accounted for, causing records to be lost silently. To prevent this, TextExtractor provides a guard special record type. Guards raise an exception when encountering unexpected text.

Consider a stream of place names:

Syracuse
Memphis
Waterloo

An extraterrestrial lacking experience with place names on Earth might produce an initial pass at an extractor for that stream that looks like this:

TextExtractor.new do
  value :name, /\S+/
  record do
    /
    #{name}
    /
  end
end

While the E.T. is away from the keyboard learning more about human culture, a name with a space in the middle such as La Paz might appear in the stream, but this extractor would silently ignore it. To prevent such a mistake, the extractor could have been written like this instead:

TextExtractor.new do
  value :name, /\S+/
  record do
    /
    #{name}
    /
  end

  guard(description: 'anything else') do
    /
    [^\n]+
    /
  end
end

This extractor, given this text:

Syracuse
Memphis
Waterloo
La Paz

Will raise a TextExtractor::GuardError with the message anything else near "La Paz\n". This message can be customized by using the description and factory keywords. Note that in a guard, the argument to factory will be the matched substring rather than a hash of extracted values.

TextExtractor comes with two built-in guards, one for lines of indented visible text and one for lines of visible text without indentation. TextExtractor.guards called with no arguments will place both of them at the end of the record list (after any subsequently defined records):

TextExtractor.new do
  guards
end

Filldown

Some texts may contain groups of records among which some common attribute is only specified once. For example, consider this list of people, grouped by occupation:

Philosophers:
Rene Descartes
Bertrand Russell

Chemists:
Alfred Nobel
Marie Curie

From this, we may want to extract the following data:

[
  { occupation: "Philosophers", name: "Rene Descartes" },
  { occupation: "Philosophers", name: "Bertrand Russell" },
  { occupation: "Chemists", name: "Alfred Nobel" },
  { occupation: "Chemists", name: "Marie Curie" }
]

The filldown special record type does not extract data into discrete rows, rather, when it matches, it modifies rows that follow it. Here is the TextExtractor, using filldown, that will perform the appropriate extraction:

TextExtractor.new do
  value :occupation, /\w+/
  value :name, /\w+ \w+/

  filldown do
    /
    #{occupation}:
    /
  end

  record(fill: :occupation) do
    /
    #{name}
    /
  end
end

To have the filldown results included in the main result set, call filldown with output: true, as in:

filldown(output: true) do
  ...
end

In general, filldown supports the same options as record.

Skip records

In some cases, it may be easier to separate important text from unimportant text by excluding the unimportant than by including the important. The special skip record type is used to define records to be skipped.

Consider a stream of movie information:

Matrix, The
  Genre: Science Fiction
Magnificent Seven, The
  Genre: Western
Get Out
  Genre: Horror

If we use an extractor with a skip record to omit a particular movie genre, like this:

NO_WESTERNS = TextExtractor.new do
  value :title, /[^\n]+/
  value :genre, /[^\n]+/

  skip do
    /
    #{title}
      Genre: Western
    /
  end

  record do
    /
    #{title}
      Genre: #{genre}
    /
  end
end

Then the output will look like this:

[
  { title: 'Matrix, The', genre: 'Science Fiction' },
  { title: 'Get Out', genre: 'Horror' }
]

Sections

In some cases, backtracking regular expression engines such as the one used in Ruby might have poor performance on large inputs. In some of these cases, it might be possible to mitigate the problem by dividing the input text into a number of smaller texts. If you find that the performance of a TextExtractor scales poorly, you might wish to try dividing the input into sections and scanning each section independently of the others. The section method does this using a simple section-dividing strategy based on Ruby's String#split.

  TextExtractor.new do
    # values omitted

    section(/\n\n+/, "\n")

    # records omitted
  end

The first argument is the delimiter, a pattern given to String#split. The optional second argument is the terminator, a string that will be appended to each element of the array returned by String#split. The input will be separated into sections of the text to be scanned independently, and the output of each scan will be combined to form the final output.

Line directives

Line directives are additional regular expression syntax available in record definitions. They are placed at the end of a line, and have effects on that entire line, including the trailing newline. A line directive is indicated by #. (preceeded by a space) appearing anywhere in a line of a record. Any preceeding spaces, the #., and any following characters will be ignored. To prevent a regexp fragment / #./ from being interpreted as a directive in a record definition, instead write it as /\s#./ or /[ ]#./.

Regular expressions containing line directives are compiled to standard Ruby regular expressions via TextExtractor.expand_directives.

The following directives are available:

#. - Comment. There is a space after the .. Any text can be placed after the space and it will be ignored. Comments can appear after other directives, using a chain like #.rest. blah blah.
#.begin / #.end - Grouping. Compiles to regex (?:...). Lines between #.begin and #.end will be added to a line group. Line groups do nothing on their own, but they can change the meaning of other directives. Other than directives, the lines these directives appear on will be ignored. Line groups can be nested. If a word is placed after #.begin.
#.capture(name) / #.end - Grouping with capture. Implicitly defines an inline value (see "Inline Values", above) for the record.
#.maybe - Optional. Compiles to regex ?. Make this line optional. Equivalent to #.repeat 0,1. A #.maybe directive can apply to an entire line group, using a chain like #.end.maybe.
#.any / #.end - Alternation. Compiles to regex (?:...|...). Form a group, as with #.begin / #.end, matching any one of the lines (or nested groups) in the group, but not more than one. The lines that these directives appear on will be ignored.
#.repeat(n,m) - Repetition. Compiles to regex {n,m}. Allow the line to appear the specified number of times. Note that the pattern is repeated, but the matching text might not be exactly the same each time. If only n (with no comma) is given, the line must appear exactly n times. If n, (with a comma) is given, the line must appear at least n times, but there is no upper limit. #.repeat(1,) is therefore equivalent to regex +. If both n and m are omitted, the line may appear 0 or more times (equivalent to regex *). A #.repeat directive can apply to an entire line group, using a chain like #.end.repeat.
#.rest - Ignore to end of line. Any trailing characters at the end of the line will be skipped. Equivalent to [^\n\]*.

Line directives can be used in a Regexp outside of a record definition. TextExtractor.expand_directives(regexp) will convert a regexp containing line directives to normal regexp syntax. To gain access to this method without loading all of TextExtractor, require 'text_extractor/directives'.

Outside of a record definition, #.begin will accept arguments starting with ? as special capture group syntax, allowing lookaround assertions and named capture groups to be used, for example #.begin(?<=) will place the line group in a positive lookbehind assertion. The meaning of the non-capturing group identifier, ?: is reversed here, since the default is not to capture in a line group. These features will also work inside a record definition, but beware that TextExtractor uses both named and unnamed capture groups internally, so attempting to use either kind of capture group directly can cause unexpected behavior.

If the last line of a group appears on the last line of an expression, with no trailing newline, the last literal line of the expression will also not have a newline. This means that /asdf #.maybe/ will compile to /(?:asdf)?/ and not /(?:asdf\n)?/ as one might expect.

Development

After checking out the repo, run bin/setup to install dependencies. Then, run rake test to run the tests. You can also run bin/console for an interactive prompt that will allow you to experiment.

To install this gem onto your local machine, run bundle exec rake install. To release a new version, update the version number in version.rb, and then run bundle exec rake release, which will create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/bjmllr/text_extractor. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

Copyright and License

The gem is available as free software under the terms of the GNU General Public License, Version 3.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

README.md

README.md

TextExtractor: Easily Extract Data From Text

Installation

Example And Explanation

Extracting Non-String Values

Inline Values

Factories

Strip whitespace between lines

The final newline

Guarding against extraction loss

Filldown

Skip records

Sections

Line directives

Development

Contributing

Copyright and License

Files

README.md

Latest commit

History

README.md

File metadata and controls

TextExtractor: Easily Extract Data From Text

Installation

Example And Explanation

Extracting Non-String Values

Inline Values

Factories

Strip whitespace between lines

The final newline

Guarding against extraction loss

Filldown

Skip records

Sections

Line directives

Development

Contributing

Copyright and License