Uploaded image for project: 'Sakai'
  1. Sakai
  2. SAK-22293

need to call updateEntityReferences from all site copy / import operations



    • Type: Bug
    • Status: OPEN
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.8.2, 2.9.0
    • Fix Version/s: None
    • Component/s: Site Info
    • Labels:


      There are many ways to copy content in Sakai: In site info, duplicate site, import content from site, using a site as template when creating a new one, and archive / restore.

      When a tool (I'm thinking specifically of Lessons) refers to instances of another tool, those references need to be updated to refer to the copies in the new site. Duplicate site calls each tool twice. The first time it copies itself. The second time is updateEntityReferences. This causes the tool to update any references to other tools. It is called as part of a second pass, after all tools have copied themselves.

      Unfortunately updateEntityReferences is only called by the duplicate site code. None of the other import or restore mechanisms use it. Furthermore, it passes a map of old to new references, which only a few tools build.

      Currently Lessons depends upon updateEntityReferences to update references. I use an approach that makes use of the map where there are entries, but uses another approach where there are not. But still, this only works for Duplciate Site. It was quite clear at the Conference that users want it to work for all the cases.

      I'd like to see updateEntityReferences called for all types of content copy / import.

      Some content copying only copies some of the content. It's certainly possible that someone could import just Lessons content from another site, and not any of the other tools. Obviously there are some problems we can't solve. If there's a reference to something that doesn't exist, we can't update it. But I'd like updateEntityReferences to be called with the best information it has. Let the tool fix up what it can.

        Gliffy Diagrams



              Issue Links



                  maintenanceteam Core Team
                  hedrick Charles Hedrick
                  2 Vote for this issue
                  8 Start watching this issue



                      Git Integration