Bug #6635
Disable nested set on digital_object table
| Status: | Verified | Start date: | 04/23/2014 | |
|---|---|---|---|---|
| Priority: | Medium | Due date: | ||
| Assignee: | Mike Gale | % Done: | 0% | |
| Category: | Performance / scalability | |||
| Target version: | Release 2.1.0 | |||
| Google Code Legacy ID: | Tested version: | |||
| Sponsored: | No | Requires documentation: |
Description
Investigate if actively keeping a nested set is even needed on digital_object. If not, it's a free optimization :)
History
#1 Updated by Mike Gale about 8 years ago
- Category set to Performance / scalability
#2 Updated by Jesús García Crespo about 8 years ago
Mike, thanks for taking care oft his! At some point when you think it's ready please submit a pull request in github! Thanks.
#3 Updated by Mike Gale about 8 years ago
- Status changed from New to Feedback
#4 Updated by Mike Gale about 8 years ago
- Status changed from Feedback to QA/Review
#5 Updated by Jessica Bushey about 8 years ago
- Status changed from QA/Review to Verified
I tested using numerous JPEGs, PDFs and MOVs.
I linked URLs, single digital objects and multiple digital objects.
I created fonds-level and series-level and item-level descriptions and attached digital objects.
I moved item-level descriptions.
I deleted series with numerous children and digital objects (VERY FAST)!
I created relationships.
I changed draft and published status.
I searched.
I viewed browse digital objects page.
I added access points and authority records.
And I made sure everything worked properly in the cover flow viewer depending upon the number of images, the level of description etc..
Looks GOOOOOD!
#6 Updated by Mike Gale almost 8 years ago
The site has been up for a month with both Dan, myself and Jessica testing it. I've merged into 2.x since I think it's tested enough to try now.
#7 Updated by Dan Gillean almost 8 years ago
- Target version set to Release 2.1.0