roed314
roed314
Instead of using cookies to track peoples filters, we should store the browse and search information in the database. This lets us be persistent across devices.
We're currently backing up every 5 minutes. We should reduce this at some point.
When an organizer returns to their manage page, we should prompt them to add slide and video links for recently past talks.
When we have questions about UI, we might add survey questions that get info back from users.
It would be useful to have the ability to check whether the external homepage of any seminar that you're curating has changed. Maybe a button (shown only to subject admins...
We should use Postgres' capabilities: https://www.postgresql.org/docs/10/datatype-textsearch.html This will allow us to create indexes for searching.
We've mostly changed our terminology in the content of the site. But there are still a lot of changes to be made in urls, function and variable names, and table...
For a non-endorsed user, we're currently making 21 database queries to load the browse page. This isn't too bad on the production site, but it's pretty annoying when developing on...
Currently we show conferences in ascending order of `start_date`. Eventually this will get unwieldy.
We currently depend on the LMFDB, and through it on Sage. This is ridiculous. One option would be to factor out the database backend from LMFDB into a separate project...