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
None of these are high priority, but we could make things snappier by:
paginating the find_studies call that fills the curator front page. It's getting pretty big (33M)
storing the output of otindex's find_studies and modifying it in memory as studies get edited. Obviously this would be more of a pain.
storing the find_collections output and modifying it in memory (as in 2, but for collections)
adding a without_version_history call for getting a study and then loading the version history of a study asynchronously through a separate call. Same total time (or worse) for the curator. But the history tab could lag. We are committed to adding the history by default at least in version 3 of the APIs, but it does add a fair amount of extra work for something that not all users want/need.
The text was updated successfully, but these errors were encountered:
None of these are high priority, but we could make things snappier by:
find_studies
call that fills the curator front page. It's getting pretty big (33M)find_studies
and modifying it in memory as studies get edited. Obviously this would be more of a pain.find_collections
output and modifying it in memory (as in 2, but for collections)without_version_history
call for getting a study and then loading the version history of a study asynchronously through a separate call. Same total time (or worse) for the curator. But the history tab could lag. We are committed to adding the history by default at least in version 3 of the APIs, but it does add a fair amount of extra work for something that not all users want/need.The text was updated successfully, but these errors were encountered: