@paul We should use this space as a place to note where OCL TermBrowser would benefit most from performance improvements. What workflows or pages are users running into slowness? What needs to run quickly to make sure we don’t lose user interest? Let’s try to answer these questions in this thread.
Global search seems to be the most obvious one right now, but let’s try to go deeper than that.
On the issue of general application performance, performance is UX and we should absolutely bake measures to understand this into our QA process… right down to whether certain interaction patterns are detrimental to our users UX due to poor connection etc.
It is possible to perform tasks with poor connections mimicked in the browser, so maybe we start there?
I am hearing that the speed/availability of Exports is also causing some problems too. PIH (Ellen Ball and others) and @gracepotma are part of this discussion and might be able to add more details.
A potential fix would be to show the incremental changes that happened in a version since the last one, even if the full export itself isn’t yet available.
This should benefit a “code reviewer” who would check that the changes from one version to the next are actually correct and relevant for their implementation. Note that this does overlap with the checksum work i.e. “Compare two versions of a source/collection”