All, Hopefully someone more familiar with this area of the DSpace code can help me figure this out because I'm a bit confused about something I've never noticed before.
In our DB, we have a table named 'communities2item' and a view named 'community2item'. From what I can tell, they are used as follows: * communities2item table Used by the org.dspace.browse.BrowseEngine and org.dspace.search.Harvest -- so, essentially it is used by our Browse & Search UIs. * community2item view Used by Item.getCommunities() to determine all the communities that a particular item is held in. This method is in turn used by the DSIndexer (in buildItemLocationString()) to add to the Search Index. What is the big difference between these two sets of data? I've noticed locally that 'communities2item' is actually larger than my 'community2item' -- it seems some items never make it into the latter (not sure why, as they are 'in archive' and not deleted). Anyone know why this repetition of data is necessary? At a quick glance, it seems like these are serving the same purpose -- but, I haven't dug deep enough to be certain. - Tim -- Tim Donohue Technical Lead for DSpace Project DuraSpace.org ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
