You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to collect some thoughts on how we can improve the References component now that #12 is in. We can migrate some of these to separate issues as we work on them.
What should happen when we click on a reference? The two most likely actions would be to open the PDF for reading or to expand the reference to display more metadata about it. Maybe we do both, with icons? (issue Improve click behaviour on references #174)
Upload target: as the library grows, the upload target will move down the screen. Should we consider moving to a tabbed layout with "upload" as a tab next to "library"? Or some other solution? Also, I'd like to make the whole component a target for files that are dragged over it. (issue Improve upload target for references #173)
We should ultimately use a table for references that can display more metadata such as journal and publication year and allow for sorting and filtering. (issue References table view and reference detail view #159)
The ingestion pipeline should display more complete information about its status while running, and we need to display information about how references have been processed after the ingest pipeline has finished, e.g. the PDF is available in the local project directory, metadata was parsed successfully from GROBID, content has been extracted and made available for AI interactions, etc. (issue Ability to display Reference ingestion status #113) (issue UI to display ingestion status #194)
We could automatically generate a key on upload, and then allow the users to edit the key if they want. A common choice for a key is the first author's last name plus the publication year, e.g. hammerbacher1999. If there's a key collision just append a, b, c, etc. If we don't have metadata just use untitled plus 1, 2, 3, etc. (added by Generate reference citation key for ingested references #112)
I want to collect some thoughts on how we can improve the References component now that #12 is in. We can migrate some of these to separate issues as we work on them.
hammerbacher1999. If there's a key collision just appenda,b,c, etc. If we don't have metadata just useuntitledplus1,2,3, etc. (added by Generate reference citation key for ingested references #112)Also as a reminder, 3 longer-term issues we won't work on now: