From 97ee90331e46477e7a3dfbb7548ce71355ff1543 Mon Sep 17 00:00:00 2001 From: Juha Heinanen Date: Thu, 5 Apr 2018 20:17:26 +0300 Subject: [PATCH 1/2] described required format of metadata for recording_metakeys table --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 7bc946375..465a5ec01 100644 --- a/README.md +++ b/README.md @@ -1304,7 +1304,9 @@ Optionally included keys are: * `metadata` This is a generic metadata string. The metadata will be written to the bottom of - metadata files within `/path/to/recording_dir/metadata/`. This can be used to + metadata files within `/path/to/recording_dir/metadata/` or to + `recording_metakeys` table. In the latter case, metadata needs to + be a list of `key:val` pairs separated by `|` character. `metadata` can be used to record additional information about recorded calls. `metadata` values passed in through subsequent messages will overwrite previous metadata values. From f80618869eacc5753600c82e0ceb6ed634887376 Mon Sep 17 00:00:00 2001 From: Juha Heinanen Date: Thu, 5 Apr 2018 20:22:28 +0300 Subject: [PATCH 2/2] improved metadata description --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 465a5ec01..3488787d0 100644 --- a/README.md +++ b/README.md @@ -1305,8 +1305,8 @@ Optionally included keys are: This is a generic metadata string. The metadata will be written to the bottom of metadata files within `/path/to/recording_dir/metadata/` or to - `recording_metakeys` table. In the latter case, metadata needs to - be a list of `key:val` pairs separated by `|` character. `metadata` can be used to + `recording_metakeys` table. In the latter case, `metadata` string must + contain a list of `key:val` pairs separated by `|` character. `metadata` can be used to record additional information about recorded calls. `metadata` values passed in through subsequent messages will overwrite previous metadata values.