Hi Tim,
just to confirm you that the content of the communities2item table and 
of the community2item view is different.
I have checked many installations and the communities2item is always 
larger than the community2item view.
I don't remember why this is needed...
Andrea

Il 02/08/2010 18:59, Tim Donohue ha scritto:
> 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
>


-- 
Dott. Andrea Bollini
Project Manager, IT Architect&  Systems Integrator
Sezione Servizi per le Biblioteche e l'Editoria Elettronica
CILEA, http://www.cilea.it
tel. +39 06-59292853
cel. +39 348-8277525

---

Disclaimer: the content of this email is confidential and may be privileged, 
and it must not be disclosed or copied without the sender's consent. If you 
have received this message in error, please notify the sender and remove it 
from your system. The content of this email does not constitute legal advice, 
nor any responsibility is accepted for loss or damage incurred as a result of 
acting upon its contents or attachments.
The statements and opinions expressed in this email are those of the author and 
do not necessarily reflect those of the employer.


------------------------------------------------------------------------------
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

Reply via email to