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

[Bryan Holladay]

My understanding, after learning more about KNL-737, was that it
wasn't in competition of SAK-16568 so they could be handled separately
and not interfere with each other.  Just append it to the new
resources transfer copy entity function.

+1 for putting in KNL-737

-Bryan


On Wed, Aug 17, 2011 at 9:41 AM, Matthew Buckett
<matthew.buckett at oucs.ox.ac.uk> wrote:
> On Thu, Jul 28, 2011 at 4:39 PM, Bryan Holladay <holladay at longsight.com> wrote:
>> So it sounds like it may be a good idea to mix parts of KNL-737 and
>> SAK-16568.  Have KNL-737 do all it's resources magic and use SAK-16568 to
>> handle entity references inside tools.  Would this be feasible/logical?
>
> Did you look at how SAK-16568 would work together?
>
> --
>   Matthew Buckett
>   VLE Developer, LTG, Oxford University Computing Services
>