As part of #109 we need to revisit the references list to be a table view. We also need to consider a reference detail view where we display all known metadata about a reference and allow the user to edit metadata. Metadata includes both scholarly metadata as well as application metadata such as whether we have the PDF, whether GROBID is parsing or was able to parse metadata, whether the PDF contents are available for chat, etc.

Let's collect screenshots and sketches of the potential UX for each of these components here.

At a high level we discussed whether the references table view should be in the left sidebar where it currently resides or if it might be better handled by a "terminal view" that comes up from the bottom.

For the reference detail view, we discussed either having a collapsible section drop down below a reference in the table when it is clicked or opening up an editor window to view details for an individual reference.

Tasks (added by @cguedes) after meeting

• "List view" of many references in left sidebar: list view with sort, filter, add, export functionality at the top ("List view" of many references in left sidebar #202)
• "Table view" of many references in editor area: full table with add/remove columns, sort/filter/tag/organize, bulk modifications, etc. ("Table view" of many references in editor area #200, References "Table view" actions #201)
• "Detail view" of one reference in editor area: edit metadata for a single reference. In the future: add notes, full text, tags, etc. ( Add sidecar endpoint so UI can pass Reference metadata updates to backend #182, [Frontend] Edit metadata for a single reference #199)