Locking a view should lock all artefacts

[Andrew Nicols]

As discussed briefly with Kristina, we should consider whether it's possible to lock all artefacts in a view and prevent them from being changed. At present, we can obviously lock all of the view-specific artefacts, but any artefact brought in from elsewhere (e.g. blog posts and resume fields) can't be locked.

http://mahara.org/interaction/forum/topic.php?id=2285

I think that, if we could get this working, it would also be worthwhile adding a Snapshot option to the views so that they can be stored permanently in whatever state they're in.

[Richard Mansfield (richard-mansfield)]

Actually blog posts *are* locked, or at least any blog posts that appear in a submitted view, but resume fields aren't. All artefacts should now have the 'locked' field set when the view they're in gets submitted, but so far I've only made the blog & file plugins respect that field and stop users from editing the locked artefacts. It would certainly be worthwhile extending this to all the other artefacts.

I'm not sure whether locking will help us to do snapshots though, because I think the point of a snapshot is that you can keep editing your stuff after taking the snapshot. I don't know about the best way to do it, but I think it might be better to use view copying or leap2a export for that.

[Andrew Nicols (dobedobedoh)]

I was wondering whether we could do some kind of COWing, but now that you mention it, exporting views should be sufficient for most purposes.