The time to implement previously-used-id constraints is within the boundary for the 1.4.0 release.
I'm working on fleshing out the details of the long-term, proper world delete solution, which will take the form of a couple more JIRAs which I'll link here. One way or another, I want this fixed (for real) not later than the 1.5.0 release. Zach On Jul 16, 2012, at 1:41 PM, Jon Hays wrote: > I'm not quite ready to assume that the proposed solutions have equal costs > (as measured by effort, time, and risks associated to the build-up of "crud > data") and was purposely vague in defining solutions as I am expecting the > project team to offer those up. The calculus before the project at the > moment seems to be: > > Immediacy & intensity of the need for world deletion functionality by > piloting institutions as expressed by URG members balanced against the > relative costs to the project for the various possible remedies. > > For Berkeley's part, we can live without the delete functionality in the > short term, which is why we would error toward the least "costly" route. I > agree, it will be important to hear from other piloting institutions so the > team can quickly assess how great the need actually is for deleting worlds.
_______________________________________________ oae-dev mailing list oae-dev@collab.sakaiproject.org http://collab.sakaiproject.org/mailman/listinfo/oae-dev
