14.11. robocop(1)#
14.11.1. Name#
robocop - find best matching sanction list entry
14.11.2. Synopsis#
robocop [-h**_|_–help**] [-v**_|_–version**] – SANCTIONSLIST
14.11.3. Description#
robocop matches KYC and KYB data against a sanctionslist. The sanctionslist must be given as the only argument. It must be a JSON file with an array of objects where each object must have an “ssid” entry that identifies the sanction list record. Furthermore, each object may have any number of keys matching the Taler attribute registry which must be mapped to an array of strings representing values to match against.
Robocop will then read JSON objects line-by-line from standard input. Each line must contain exactly one JSON object. Each JSON object must again consist of a set of attribute registry entries and their string values. For each JSON object read, Robocop will find the best matching sanction list entry and output the matching and confidence scores (on a scale of 0-1) and the “ssid” (one one line per input).
The main use of Robocop is as a RATER tool for taler-exchange-sanctionscheck.
Its options are as follows:
- -h
Print short help on options.
- -v
Print version number.
14.11.4. See Also#
taler-exchange-sanctionscheck(1)
14.11.5. Bugs#
Report bugs by using https://bugs.taler.net or by sending electronic mail to <taler@gnu.org>.