partial implementation of first_eid, last_eid -- I think the vals work -- they do for searches anyway, but not stored in pa_user_state yet

TODO

@@ -1,6 +1,24 @@
 ## GENERAL
+    * optimising for job scans...
+        - run_ai_on_path not finding previous job as jex path is path_prefix...
+        pa=# select * from jobextra where job_id = 45;
+         id | job_id |    name     |           value
+        ----+--------+-------------+---------------------------
+         79 |     45 | person      | all
+         80 |     45 | ptype       | Import
+         83 |     45 | path_prefix | static/Import/new_img_dir
+         84 |     45 | eid-0       | 2
+         85 |     45 | eid-1       | 31
+
+        BUT WHY 2 eids -- because we have photos and new_img_dir, interesting
+        that pp is the last one... need to do better with this on creation I think?
+
+
     * browser back/forward buttons dont work -- use POST -> redirect to GET
-        * viewlist can work out new view_eids server side, and pass them back as json data (fixes loss of fullscreen & back/fwd issues)
+        * viewlist 
+            - [DONE] can work out new view_eids server side, and pass them back as json data (fixes loss of fullscreen & back/fwd issues)
+            - [DONE] should really define the first/last of a GetEntries search and use definitive logic to show at start or end of entries (for next/prev buttons in viewer.html)
+            - need to keep "current", "first_eid", "last_eid" in pa_user_state to support back button / reloading view/<current> and better handling of next/prev
             - can consider an optim-- new_view page makes calls to viewlist to ADD json data only, so only trigger a new "viewlist" if we dont have data for that part of the eids
         job.py:@app.route("/jobs", methods=["GET", "POST"])
         job.py:@app.route("/job/<id>", methods=["GET","POST"])
@@ -8,17 +26,8 @@
         files.py:@app.route("/fix_dups", methods=["POST"])
             ???
 
-    * per file you could select an unknown face and add it as a ref img to an existing person, or make a new person and attach?
-
-    * refimg locns can lose an array idx of 0 always.
-
-    * search allow noo?
-
-    * optim to not run_ai_on_* for scan, needs to make sure last run_ai_on actually ran/worked - might have failed (or in my case was marked stale and I cancelled it)
-        -- also the case for get file details though, need to make sure last one was completed
-
-        * [DONE] order/ find face with largest size and at least show that as unmatched
-            - could also try to check it vs. other faces, if it matches more than say 10? we offer it up as a required ref img, then cut that face (with margin) out and use it is a new ref image / person
+    * [DONE] order/ find face with largest size and at least show that as unmatched
+        - could also try to check it vs. other faces, if it matches more than say 10? we offer it up as a required ref img, then cut that face (with margin) out and use it is a new ref image / person
         * on viewer: allow face to be used to create person, add to existing person, and allow 'ignore', mark as 'not a face', etc. -> all into DB
             - so need face 'treatment' -> could be matched via face_refimg_link, but also could be 'ignore' or 'not a face', in each case we could exclude those faces from
             matching for the future, and reporting on matches, etc.
@@ -26,6 +35,10 @@
                 https://stackoverflow.com/questions/31601393/create-context-menu-using-jquery-with-html-5-canvas
             - also allow joblog search from the viewer for that file...
 
+    * refimg locns can lose an array idx of 0 always.
+
+    * search allow noo?
+
     * delete folder
 
     * allow joblog search