From 3370f203c3652ace357eeb69bb8828d830b3596a Mon Sep 17 00:00:00 2001
From: Bryan Newbold <bnewbold@archive.org>
Date: Thu, 13 Feb 2020 15:28:48 -0800
Subject: move pdf_trio results back under key in JSON/Kafka

---
 proposals/20200207_pdftrio.md | 33 ++++++++++++++++++---------------
 1 file changed, 18 insertions(+), 15 deletions(-)

(limited to 'proposals')

diff --git a/proposals/20200207_pdftrio.md b/proposals/20200207_pdftrio.md
index 7ad5142..31a2db6 100644
--- a/proposals/20200207_pdftrio.md
+++ b/proposals/20200207_pdftrio.md
@@ -58,24 +58,27 @@ Basically just like GROBID client for now. Requests, JSON.
 Output that goes in Kafka topic:
 
     key (sha1hex)
-    status
-    status_code
-    ensemble_score
-    bert_score
-    image_score
-    linear_score
-    versions
-        pdftrio_version (string)
-        models_date (string, ISO date)
-        git_rev (string)
-        bert_model (string)
-        image_model (string)
-        linear_model (string)
-    timing (might be added?)
-        ...
+    pdf_trio
+        status
+        status_code
+        ensemble_score
+        bert_score
+        image_score
+        linear_score
+        versions
+            pdftrio_version (string)
+            models_date (string, ISO date)
+            git_rev (string)
+            bert_model (string)
+            image_model (string)
+            linear_model (string)
+        timing (optional/future: as reported by API)
+            ...
     file_meta
         sha1hex
         ...
+    timing
+        ...
 
 
 ## SQL Schema
-- 
cgit v1.2.3