Okay, with http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/dbs/conjoined_tpac the display time for record #97 is down to an average display time of 0.95 seconds, and record #15 (which has to display the four linked child bibs) is around 1.05 seconds given repeated tests. I restructured the bib retrieval code to cache bibs that we already had retrieved in this page display request and to short-circuit in some cases. I also fixed up whitespace.
Also, I modified the display a fair bit, if you're displaying a child bib (like record #97), the top of the copy table displays the foreign items, as follows (with new CSS):
I think that before this branch gets pushed, we should probably just squash all of the commits down into one commit; no sense in bringing the churn into mainline repo. Bill, would my branch meet GRPL's needs?
Okay, with http:// git.evergreen- ils.org/ ?p=working/ Evergreen. git;a=shortlog; h=refs/ heads/user/ dbs/conjoined_ tpac the display time for record #97 is down to an average display time of 0.95 seconds, and record #15 (which has to display the four linked child bibs) is around 1.05 seconds given repeated tests. I restructured the bib retrieval code to cache bibs that we already had retrieved in this page display request and to short-circuit in some cases. I also fixed up whitespace.
Also, I modified the display a fair bit, if you're displaying a child bib (like record #97), the top of the copy table displays the foreign items, as follows (with new CSS):
[Branch name] (foreign item)
* [Peer type]: [foreign bib title] / [foreign bib author]
I think that before this branch gets pushed, we should probably just squash all of the commits down into one commit; no sense in bringing the churn into mainline repo. Bill, would my branch meet GRPL's needs?