mahara-contributors team mailing list archive

[Aaron Wells <1185209@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

In a similar vein to https://bugs.launchpad.net/mahara/+bug/547987
(which allows users self-registering to upload a LEAP2A file), I think
users with existing accounts should be able to import LEAP2A content
into their portfolio. There are a few additional concerns related to
this, so I'm opening a separate bug for it:

1. Profile information: For an existing user, you want to either ignore
profile information in the LEAP2A, or provide an interface for them to
selectively choose which bits of their existing profile to override

2. Duplicate content: When you're using LEAP2A to create accounts, you
don't have to worry about duplicate Pages & Content, because there isn't
any. But, when you're dealing with existing accounts, what do you do if
someone imports the same LEAP2A file twice? The easy answer is, don't
sweat it and just create duplicate pages, adding "Copy of" or the like
if you need to.

(If we wanted to get fancy we could implement a sync system, but that
could get trick, and it would require adding a "fingerprint" value to
Pages when they get created, and including that in the LEAP2A, so that
on import you can detect whether two Pages are different versions of
each other.)

** 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/1185209

Title:
  Allow existing users to import LEAP2A content into their portfolio

Status in Mahara ePortfolio:
  Triaged

Bug description:
  In a similar vein to https://bugs.launchpad.net/mahara/+bug/547987
  (which allows users self-registering to upload a LEAP2A file), I think
  users with existing accounts should be able to import LEAP2A content
  into their portfolio. There are a few additional concerns related to
  this, so I'm opening a separate bug for it:

  1. Profile information: For an existing user, you want to either
  ignore profile information in the LEAP2A, or provide an interface for
  them to selectively choose which bits of their existing profile to
  override

  2. Duplicate content: When you're using LEAP2A to create accounts, you
  don't have to worry about duplicate Pages & Content, because there
  isn't any. But, when you're dealing with existing accounts, what do
  you do if someone imports the same LEAP2A file twice? The easy answer
  is, don't sweat it and just create duplicate pages, adding "Copy of"
  or the like if you need to.

  (If we wanted to get fancy we could implement a sync system, but that
  could get trick, and it would require adding a "fingerprint" value to
  Pages when they get created, and including that in the LEAP2A, so that
  on import you can detect whether two Pages are different versions of
  each other.)

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