Our team discovered that serving up printable HTML guides for very large, nested files at the traffic rate generated by the AI bots was the primary source of the site performance issues experienced at launch, so we are temporarily linking to stored static HTML pages from the legacy OAC site for those specific finding aids.
As of 8/8, this applies to HTML guides for finding aids with over 300 <c0#> components. These static HTML pages served by the legacy OAC site will not include any new data submitted after June 30th, as they are limited to displaying finding aid data submitted through the legacy OAC system.
In the next few months, we will investigate new strategies to ensure that all finding aids in the new OAC system, regardless of size, feature up-to-date, single-page printable guides. We will also be engaging with the ArcLight development community to address this issue, which other institutions have also found to be very challenging.
Curious about our progress? Take a look at our work-in-progress overview page to check the status.
Status
Prioritized to begin investigation 2025 Q4
Issue
Our team discovered that serving up printable HTML guides for very large, nested files at the traffic rate generated by the AI bots was the primary source of the site performance issues experienced at launch, so we are temporarily linking to stored static HTML pages from the legacy OAC site for those specific finding aids.
As of 8/8, this applies to HTML guides for finding aids with over 300 <c0#> components. These static HTML pages served by the legacy OAC site will not include any new data submitted after June 30th, as they are limited to displaying finding aid data submitted through the legacy OAC system.
In the next few months, we will investigate new strategies to ensure that all finding aids in the new OAC system, regardless of size, feature up-to-date, single-page printable guides. We will also be engaging with the ArcLight development community to address this issue, which other institutions have also found to be very challenging.
Curious about our progress? Take a look at our work-in-progress overview page to check the status.
0 Votes
0 Comments
Login or Sign up to post a comment