Allow existing users to import LEAP2A content into their portfolio
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Wishlist
|
Son Nguyen |
Bug Description
In a similar vein to https:/
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.)
Changed in mahara: | |
assignee: | nobody → Son Nguyen (ngson2000) |
tags: | added: nominatedfeature |
Changed in mahara: | |
milestone: | none → 1.8.0 |
status: | Triaged → Fix Committed |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
Leap2a specification here: http:// wiki.leapspecs. org/2A/ specification