Page Comparison

...

Extract regex groups: If there is one or more groups in the regular expression and this option is enabled, then the value of the groups will be set in the destination metadata. If it is not checked, the complete match is stored in the destination metadata. The groups of a regular expression are defined between ( and ). For example, this regular expression has one group: word1 (.*?) word2. In this regular expression, we are searching for the part of a text starting with word1and ending with word2. Let's take this text: My word1 titi tata toto word2 and other words. With the chosen regular expression mentioned above, if the checkbox is enabled, then the destination metadata = gets the value "titi tata toto". OtherwiseIf the checkbox is not enabled, the destination metadata = gets the value "word1 titi tata toto word2". With several groups, the values will be added separated with spaceNow, if we change a little the regex to have several groups, for example: word1 (.?) tata (.?) word2, the result is: destination metadata = "titi toto". “titi” and “toto” are extracted and set in destination metadata, separated by a whitespace. This field is optional.

You can add as many destination metadata, regular expression and source metadata as you want by clicking on the Add button.

...

• Ignore case: (?i)searched_word: retrieves “searched_word” regardless of character case.

• Retrieve the line containing: .*searched_word.*

• Search a point: \. “\” is the escape character.

• Spaces are taken into account, so searching “word1 word2” will search the exact expression in the content.

• e-mails: ([a-zA-Z0-9_\-\.]+)@([a-zA-Z0-9_\-\.]+)\.([a-zA-Z]{2,5})

• Phone number: (\+)([\s.\(\)]*\d{1}){8,13}(-)?(\d{1,5})

• Search “word1” or “word2”: word1|word2.

• For exemples using regex groups, see the section above about the “Extract regex groups” option.

More examples of regex here : Regex typical use cases

...

But if you want to extract only the department of <part1>, this is not possible with the Regex Entity Connector as it processes a file line by line. The file above presents several lines (i.e. with return characters). The regex to extract department of <part1> could have been: <part1>\s<department>(.*?)</department>. \s is used to take into account the return to the line. But as the connector reads line by line, only <part1> will be read when the regex is applied.

However, as long as you're not in the situation where you need to extract data from tag nesting, the Regex Entity Connector is an interesting solution for, say, extracting chunks of information between tags. Let’s see this other example: <department>DEP1/COMMON-DEP/DEP2</department>, you want to extract DEP1 and DEP2. Let's say COMMON-DEP is part of the selection criteria for finding departments to extract. The regular expression will be: <department>(.*?)/COMMON-DEP/(.*?)</department>.

...