mahara-contributors team mailing list archive

[Steven <stevens@xxxxxxxxxxxxxxx>]

==== How to Test ====
1. create a couple portfolio pages with a text box that has attachements to it 
2. Under portfilio tab click the export link in menu
3. select export format Leap2A and generate export - save to somewehre locally 
4. log in as an admin and add user  
5. Import the newly created Leap2A file using the creation method upload Leap2A -fill all other required fields
6. confirm that the new user has been created 
7. confirm that all artifacts have been created 
8. confirm that file attachments in text boxes are also created for the new user profile

=== Test Results  ===
6. confirmed that the new user has been created 
7. confirmed that all artifacts have been created 
8. confirmed that file attachments in text boxes are also created for the new user profile

Note: the attach files to Resume was not working at the time of testing
- functionality for the resume attachments being exported and imported
cannot be confirmed

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