Feature request: BTR tables

[keara-soloway]

Submitting this request on Arthur's behalf:

"""
Starting from the home page, I suggest a button that has the function, “my BTRs” which would return a list of all BTR’s (file IDs) associated with the user, by default arranged by date from most recent to oldest. (I notice that my home page already shows all of the BTRs, but not in tabulated form). That list would be similar to the one currently generated on the home page [...], but with only one entry per BTR - e.g. listing beamline and cycle, but also start date, number of DID records, number of scans. [...]

In the table view generated above, the user could then select / click on a particular row. Maybe there could be two ways to click — one that would go to all DID records associated with that BTR. But the other would display a list of all scan records associated with the BTR.
"""

@vkuznet I think I have a plan, but not sure if interacting with BeamPASS from FOXDEN in this way is sound (particularly for non-CHESS instances) -- let me know if I can proceed with this as is:

• In golib/config:
  • add a CHESSBeamPASSAPIURL field to the Services struct (is there a better / clearer way to name this field?)
• In BeamPass API service:
  • add support for getting BTR records by their file IDs to the existing "/btr" endpoint
• In Frontend service:
  • add a "/btrs" endpoint whose handler returns a page with the interactive btr, dataset, and scan tables described above (if CHESSBeamPASSAPIURL field is present in srvConfig.Services -- otherwise return an error message page)
  • add a hyperlink to "/btrs" endpoint somewhere -- maybe in dyn_dstable.tmpl as Arthur suggested, close to the current list of user BTRs.

[vkuznet]

@keara-soloway , Keara the plan is correct and I'll only clarify few additional points to you:

• You will need to add new end-point /btrs and handler BtrsHandler to Frontend
• Your BtrsHandler should provide output in both HTML and JSON forms, see how it is done in SyncHandler over here
• Please use standard template error.tmpl when your handler will return error in HTML format, e.g. see this part. This will provide consistency across other error pages
• Arthur asked to provide all rows of scans for given BTR, so you should use a new API like /scans?btr=my_btr. The handler serving this end-point should contact with SpecScan services to fetch appropriate list of scan records and properly format it. This is more complicated than you may think since you don't know a-priory how many rows will be returned and don't know your browser wait to render thousands of those. A better approach is to add pagiantion which means that your spec scan service should accept /scans?btr=my_btr&idx=0&limit=10 (idx and limit parameters along with btr). Then you can use similar approach representing in pagination function and pagination.tmpl template.
• Arthur also mentioned sorted order of BTRs results. This implies that the BeamPass API should accept order parameter or already has hard-coded order. You should verify that too.

Apart from that I think you have a clear view how to proceed and can accomplish this task.