mahara-contributors team mailing list archive

[Aaron Wells <1376073@xxxxxxxxxxxxxxxxxx>]

It's worth noting that Mahara has a tiny bit of "soft copy" already.
Specifically, when a user copies another user's page, if the page
contains any file artefacts we don't make a copy of the underlying file
on the filesystem; instead we point the new artefact at the same
filesystem file. This does NOT come into play when you copy pages via
Leap2A though.

I've considered extending this to be the same system used by Mahara &
git, where you calculate a unique hash for the file, and then use that
hash as its name in the filesystem. Then if someone uploads or copies an
identical file, we note that there's already a file with that hash and
point the new file artefact at it instead of duplicating it. That would
cover Leap2a copying.

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contributors -- please ask on #mahara-dev or mahara.org forum before editing or unsubscribing it!
https://bugs.launchpad.net/bugs/1376073

Title:
  Soft copies of templates

Status in Mahara ePortfolio:
  New

Bug description:
  Feature idea from ePortfolio workshop:

  Make templates do soft copies (by default?), saving a link to the
  original content rather than actually copying it. Updates to the
  original template could then be automatically reflected in copies.
  When a user edits their copy, the soft link is broken so that updates
  to the template don't overwrite the modified content.

  Soft copies would also reduce the cost in time and disk usage of
  creating a copy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mahara/+bug/1376073/+subscriptions