Public bug reported: Currently LEAP import only work when an admin creates a new user account.
Someone was suggesting that they would need users to be able to import their porfolios into an existing account if they can move away from another portfolio site: http://mahara.org/interaction/forum/topic.php?id=1958#post8846 Here's a relevant discussion with Nigel: <waawaamilk> we didn't do it in the original work because it would have involved having to deal with merging portfolios e.g., who's profile fields count? it ended up being something else that was going to delay 1.2 so we dropped the idea but if you can think of a good way to deal with that, then go for it there's no reason why only admins can do it either other than the create user aspect the importer should work fine if a normal user triggers it <fmarier> i suppose you could have an import switch to "overwrite existing" or "ignore conflicts" <waawaamilk> you only have a problem with artefacts with is_single() = true yeah, you could not bother on a field by field basis just a global setting <waawaamilk> you'd probably be 99% of the way there if you just added everything in the import ** Affects: mahara Importance: Undecided Status: New -- Ability for users to do an import into their existing accounts https://bugs.launchpad.net/bugs/599261 You received this bug notification because you are a member of Mahara Contributors, which is subscribed to Mahara. Status in Mahara ePortfolio: New Bug description: Currently LEAP import only work when an admin creates a new user account. Someone was suggesting that they would need users to be able to import their porfolios into an existing account if they can move away from another portfolio site: http://mahara.org/interaction/forum/topic.php?id=1958#post8846 Here's a relevant discussion with Nigel: <waawaamilk> we didn't do it in the original work because it would have involved having to deal with merging portfolios e.g., who's profile fields count? it ended up being something else that was going to delay 1.2 so we dropped the idea but if you can think of a good way to deal with that, then go for it there's no reason why only admins can do it either other than the create user aspect the importer should work fine if a normal user triggers it <fmarier> i suppose you could have an import switch to "overwrite existing" or "ignore conflicts" <waawaamilk> you only have a problem with artefacts with is_single() = true yeah, you could not bother on a field by field basis just a global setting <waawaamilk> you'd probably be 99% of the way there if you just added everything in the import _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : mahara-contributors@lists.launchpad.net Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp