-
- 330 Posts
I'm just curious as to how someone would go about this.
A while back I made a site for a furniture company that had about 300 individual items (note this was not an ecommerce site). I taught the admin people how to manage and create resources and they have since added another 100 items, with potential thousands more being added over the years. The problem is it's getting hard to locate individual items within the resources structure. Exposing trees of resource is also very laggy.
Just curious, what would your approach to this be?
-
- 5,888 Posts
I would put stuff like that allways into custom-tables
-
- 932 Posts
Using the collections extra is probably the best way to go to be honest. Biggest site that I manage has around 11,000 resources and I just split and organised everything into collections.
-
- 5,888 Posts
don't let opengeek hear that!
[ed. note: Bruno17 last edited this post 6 years, 4 months ago.]
-
- 932 Posts
The "purist" argument for using custom tables, is that resources are not meant as a data store, but for, well, resources. If you're going to manage real estate listings for example, the resources model isn't optimized for that, but a custom table would be.
As for the question in the first post - I'd second @LK's recommendation of using Collections. It's very useful for managing lots of resources. Search function helps to find what you're looking for, too.
-
- 24,544 Posts
Don't forget the search function at the top of the resource tree.