Hi, last week we fixed the bug DS-1860. In DS-1860 was reported that community-list does not show all communities. To generate the list of all communities and collections JSPUI uses the CommunityListServlet which traverses all communities and collections. Some days later we asked ourselves why this is done by a servlet and if it would be easier to reuse the code when done in a method of a normal class. Next step was to look for a list of communities and collections used elsewhere in DSpace. While looking around, we saw that community-home shows the subcommunities and collections of a community, but only the subcommunities and collections of the next level.
To give an example, we look on the following graph: Community A, +-> Subcommunity B +---> SubSubCommunity C +-----> Collection 1 +-----> Collection 2 +->Subcommunity D +---> Collection 3 +-> Collection 4 (So the Collections 1 and 2 are childs of SubSubCommunity C, Collection 3 is a child of subcommunity D and Collection 4 is a child of Community A). The community-home of Community A would list Subcommunity B, Subcommunity D and Collection 4, but not the other communities and collections. Collection-home of Subcommunity B would show SubSubCommunity C, but not Collection 1 and 2. Etc, etc. This brings up two questions: - Shouldn't all subsequent communities and collections be shown on community-home? - If we would move the functionality that CommunityListServlet provides to a normal class: in which class should it be done? In org.dspace.content.Community? I would appreciate every idea. Regards, Pascal ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
