Great to see you here and thanks for your feedback.
Cheers
Kristina
]]>Currently, we do not have the possibility to import into an existing account. What Craig meant was that a new account is created and then you copy the pages into the existing account manually.
Cheers
Kristina
]]>The only place I can see Mahara accepting a LEAP2a file is on account creation.
I would consider the development of this functionality a high priority also.
]]>To me backup does suggest that the portfolio can be restored –currently the restore is not able to be done by the owner of the portfolio but it is still able to be done. This reassures the portfolio owner that their portfolio pages are safe if something goes wrong with them or they are deleted.
Export suggests that the portfolio is being converted into a different format which may not be able to be restored into Mahara. This is true if they choose the html format.
So maybe use the term Export for the html format and Backup for the LEAP2A format (most users probably don’t know what LEAP2A is but would know what backup is) .
I agree that making the restoration process easier would be a great feature.
Craig
]]>
Thanks for your feedback. We already have some basic specs for the user's own import at https://blueprints.launchpad.net/mahara/+spec/improve-portfolio-import-export (goes to the wiki page for more info).
I'm totally with you that this would be a great enhancement.
Cheers
Kristina
]]>But I am also with you Dominique-Alain. A backup needs to be able to be restored in a convenient and effective way. Choosing of what needs to be restored from a backup and placing it into the existing portfolio would a great feature to have.
For the time being and until all the great feature requests have been implemented, how about a button called 'Backup/Export' :)
]]>For me it means that behind the question of changing the name of the button, it more changing the way Mahara does the things that is the center of the reflexion.
-dajan
]]>Thank you for your feedback. The institutional backup is out of the question and should definitely happen. However, in this case it was users who deleted their pages and can't recover them now (unless you dig in the server backup). Backup instead of export seemed to be sparking their thoughts more of doing a backup themselves before deleting the page.
Cheers
Kristina
]]>My position is that I am awaiing from my institution to backup my data not me. Opening an account with my University as as student also gives them the obligation to protect my privacy and my data. So for me Backup is something on the institution side.
On the other hand, Export, is something I will do at the end of my relationship with the institution, when I leave it and want to take all my data with me (as a web site or as a transferable Leap2A file, and mabe later as ad PDF or Word document, as the roadmap will go).
I personnaly would give my voice for keeping Export in Mahara instead of Backup.
Cheers,
-dajan
]]>In one of our Mahara installations, users would favor the term "Backup" to "Export" to be prompted more easily of what you can do there. Sometimes users delete content that they then wish to not have deleted, but they can't get it back easily. If they saw "Backup" as menu option they might click on it more and actually make a backup of their data for save keeping. "Export" doesn't seem to work so well for them.
I was wondering if others think the same and that we should change it to "Backup" in general.
Thanks already in advance for your input.
Cheers
Kristina
]]>