[Building Sakai] Entity References Broken During Site Import: Solution Vote (KNL-737 or SAK-16568)

[Matthew Buckett]

On Thu, Jul 28, 2011 at 3:51 PM, Bryan Holladay <holladay at longsight.com> wrote:
> So it sounds like a big difference between KNL-737 and SAK16568 is KNL only
> updates Site ID references and is contained completely in Kernel as a
> service, while SAK-16568 updates any OLD->NEW context (Site Id, Assignment
> ID, Forum ID, ect) but requires the tools to supply the refernce(old->new)
> mapping and as well as the logic to convert them inside itself by
> implementing the stubs.

Ok so inside content we can have URLs to things:

Content Hosting: /access/....
Tools (with portal): /portal/....
Tools (direct): /direct/....

I only address the first one of these, but I handle the copying of
those referenced resources for the tool if the resources tool isn't
being duplicated into the new site.
My understanding of Bryan's patch it that it asks the tool for all the
URLs that it was available under in the old site and then updates any
references for the new site, so if the tool returns URLs with /access,
/portal, /direct they will all get updated?

-- 
  Matthew Buckett
  VLE Developer, LTG, Oxford University Computing Services