I'm expecting to rebuild the Application layer on QA at or after 9:30 pm PST (12:30 am EDT) tonight; am hoping that won't unduly disrupt anyone's testing. (If you're testing during that time, you may need to logout and log back in, but your data should still be there.) This rebuild should install fixes for these two issues, the first of these important to new functionality in v3.2: http://issues.collectionspace.org/browse/CSPACE-5767 http://issues.collectionspace.org/browse/CSPACE-5794 After these are in place, there's a new QA Test Plan for the functionality that maintains the Computed Current Location value in a Cataloging record, when related Movement records are added, changed, or deleted: http://wiki.collectionspace.org/display/collectionspace/Object+Current+Location+-+QA+Test+Plan I've assigned this to myself, but anyone else is welcome to take it on (or test it in a different browser). Please feel free to edit the Plan if you encounter any errors, as well. Thanks, Aron

The App layer has been rebuilt on QA, and the fixes for the two issues listed below - both in that layer - appear to be working properly. On Tue, Dec 18, 2012 at 8:25 PM, Aron Roberts <aron@socrates.berkeley.edu> wrote: > I'm expecting to rebuild the Application layer on QA at or after > 9:30 pm PST (12:30 am EDT) tonight; am hoping that won't unduly > disrupt anyone's testing. (If you're testing during that time, you may > need to logout and log back in, but your data should still be there.) > > This rebuild should install fixes for these two issues, the first of > these important to new functionality in v3.2: > > http://issues.collectionspace.org/browse/CSPACE-5767 > http://issues.collectionspace.org/browse/CSPACE-5794 > > After these are in place, there's a new QA Test Plan for the > functionality that maintains the Computed Current Location value in a > Cataloging record, when related Movement records are added, changed, > or deleted: > > http://wiki.collectionspace.org/display/collectionspace/Object+Current+Location+-+QA+Test+Plan > > I've assigned this to myself, but anyone else is welcome to take it > on (or test it in a different browser). Please feel free to edit the > Plan if you encounter any errors, as well. > > Thanks, > Aron

Thanks so much for the work on computed location & the new test plan. I just ran through it on Chrome and everything works like a charm (existing bug notwithstanding). Woot! On Tue, Dec 18, 2012 at 11:25 PM, Aron Roberts <aron@socrates.berkeley.edu>wrote: > I'm expecting to rebuild the Application layer on QA at or after > 9:30 pm PST (12:30 am EDT) tonight; am hoping that won't unduly > disrupt anyone's testing. (If you're testing during that time, you may > need to logout and log back in, but your data should still be there.) > > This rebuild should install fixes for these two issues, the first of > these important to new functionality in v3.2: > > http://issues.collectionspace.org/browse/CSPACE-5767 > http://issues.collectionspace.org/browse/CSPACE-5794 > > After these are in place, there's a new QA Test Plan for the > functionality that maintains the Computed Current Location value in a > Cataloging record, when related Movement records are added, changed, > or deleted: > > > http://wiki.collectionspace.org/display/collectionspace/Object+Current+Location+-+QA+Test+Plan > > I've assigned this to myself, but anyone else is welcome to take it > on (or test it in a different browser). Please feel free to edit the > Plan if you encounter any errors, as well. > > Thanks, > Aron > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > -- Megan Forbes Collection Manager Museum of the Moving Image 36-01 35 Avenue Astoria, NY 11106 movingimage.us 718 777 6800 Direct 718 777 6834