<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>Hi Hillel,</div><div><br></div><div>There isn't much that can be done about a request timeout, especially since it can vary by browser. The EAD download doesn't time out, as you observe, because it streams it's response. It wouldn't be too hard to do this for labels too. Perhaps we can find some time next week to chat if you are up for working on it together.</div><div><br></div><div>Brian</div><div><br></div><div><br></div><div><div style="font-size:9px;color:#575757">Sent from my T-Mobile 4G LTE Device</div></div><br><br><div>-------- Original message --------</div><div>From: "Arnold, Hillel" <harnold@rockarch.org> </div><div>Date:05/13/2015 5:14 PM (GMT-05:00) </div><div>To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org> </div><div>Cc: </div><div>Subject: [Archivesspace_Users_Group] Container label export </div><div><br></div><div><div><div>I’ve been doing a bit of tweaking to the Download Container Labels functionality, and in the process discovered that I get a timeout error when attempting to export container labels for large collections. I tried a variety of things, including commenting out everything inside the "objects.each do” loop of the generate_label_rows, but it appears that even looping through every object in the collection causes that same timeout error.</div><div><br></div><div>I’m wondering if there are any ways to avoid this error, either by improving the logic or changing the serialization mechanism. EAD exports, which are way more complex, work just fine, so there’s obviously a way to do this. Any clues would be very much appreciated!</div><div><br></div><div>Thanks,</div><div><div><div><br></div><div>Hillel Arnold</div></div><div>Lead Digital Archivist</div><div>Rockefeller Archive Center</div></div></div></div>
</body>