mahara-contributors team mailing list archive

[Richard Mansfield <617376@xxxxxxxxxxxxxxxxxx>]

Collection submission now in bug #786389.

** Summary changed:

- Fix view_access redundancy / allow collection submission
+ Fix view_access redundancy

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
https://bugs.launchpad.net/bugs/617376

Title:
  Fix view_access redundancy

Status in Mahara ePortfolio:
  Confirmed

Bug description:
  We have ended up with duplicated view_access records for every view in
  a collection.  It's only the application that tries to ensure that
  every view in a collection has exactly the same access records.  This
  should be cleaned up in the database, possibly by removing the view id
  from the view_access table and replacing it with some kind of access
  list id, referenced from the view table so that several views can
  share a set of access records.

  However, it'd be easier if we did something about access for submitted
  views first.  Only individual views can be submitted to groups (and
  mnet hosts), not entire collections, so currently a collection can
  have some submitted views in it, and some unsubmitted ones.  On
  submission, teacher access to the view is ensured by a view_access
  record that's invisible to the owner and cannot be deleted by the
  owner, and the easiest way to completely remove the need for views to
  have copies of access records would be to allow submission of
  collections, and to not allow views in a collection to be submitted
  individually.