mahara-contributors team mailing list archive

[Aaron Wells <1185211@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

If we implement https://bugs.launchpad.net/mahara/+bug/1185209 ,
allowing users to import LEAP2A files into their existing account, and
https://bugs.launchpad.net/mahara/+bug/1185188 , a button to quick-save
a single page as a LEAP2A archive, then a user may create a LEAP2A
archive just to share some pages with friends. In which case, they will
not want that archive to include their profile information.

So, we should add controls to the LEAP2A export page that let the user
determine whether or not to include their profile information, and which
parts to include.

Note that we may also need to alter the LEAP2A import functionality for
when it's used to create new accounts, so that it won't choke if profile
information is incomplete or missing.

It would also be worthwhile to check with the LEAP2A standards to see
whether these fields are required according to the standard, and if so,
maybe propose an amendment to the standard to allow this kind of usage.

** Affects: mahara
     Importance: Wishlist
         Status: Triaged


** Tags: leap2a

-- 
You received this bug notification because you are a member of Mahara
Contributors, which is subscribed to Mahara.
Matching subscriptions: Subscription for all Mahara Contrib members
https://bugs.launchpad.net/bugs/1185211

Title:
  Allow users to choose which profile information to include in LEAP2A
  exports

Status in Mahara ePortfolio:
  Triaged

Bug description:
  If we implement https://bugs.launchpad.net/mahara/+bug/1185209 ,
  allowing users to import LEAP2A files into their existing account, and
  https://bugs.launchpad.net/mahara/+bug/1185188 , a button to quick-
  save a single page as a LEAP2A archive, then a user may create a
  LEAP2A archive just to share some pages with friends. In which case,
  they will not want that archive to include their profile information.

  So, we should add controls to the LEAP2A export page that let the user
  determine whether or not to include their profile information, and
  which parts to include.

  Note that we may also need to alter the LEAP2A import functionality
  for when it's used to create new accounts, so that it won't choke if
  profile information is incomplete or missing.

  It would also be worthwhile to check with the LEAP2A standards to see
  whether these fields are required according to the standard, and if
  so, maybe propose an amendment to the standard to allow this kind of
  usage.

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