Some more implementation details follow. Simplest solution: The easiest way to do this would be to write a PluginExport wrapper class, like PluginExportCombined and call that instead of the PluginExportLeap and / or PluginExportHtml and have that class call the other two to generate both sets of information in the normal way but PluginExportCombined has a method 'export()' that is a combination of the Leap2a and HTML ones so that the data ends up in one zip file.
To make things easier the HTML version can be in a subdir of the Leap2A one, ie under a /html/ path in zip file, so that the zip file can still be loaded back into Mahara without any other canges. Medium: This will be done similar to the approach above but will mean storing both the Leap2A and HTML under separate dirs, ie /html/ and /leap2a/ to make it easer for users to understand. That way they can delete the subdir they don't want without affecting the other. It will mean also adjusting the import mechanism so that when a user uploads the zip file it 'finds' the Leap2A data and imports that and doesn't try to import the HTML data. Best: Have the PluginExportCombined class replace the other two and export both HTML and Leap2a data combined together so that we only export the artefact files, eg images once. So that the export page only shows the one option. Note: Could make it a site setting that the site can specifiy which export type it wants to use, eg HTML only, Leap2A only, combined and have combined as default. -- 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/1415267 Title: Archive submissions in both Leap2A and HTML Status in Mahara: Confirmed Bug description: In Mahara 1.10 the experimental feature of archiving of submissions was implemented. Currently, an archive is always a Leap2A file. The idea behind it was that the portfolio can be imported back into Mahara later on for users to continue working on it. Shane Nuessler mentioned that he has problems importing a Leap2A file from an older version into a newer version of Mahara. That's another issue to look into, but shows that Leap2A may not be the best format to have for longevity. HTML files can be opened by any browser and thus are more independent of the current Mahara site being used. So it really depends on what you want to do with the archived submissions: Do you want to keep it as a record for a long time or do you want students to be able to import it back into their portfolios if needed. Thus, it would be good if the group admin could decide to either archive in HTML or in Leap2A. To manage notifications about this bug go to: https://bugs.launchpad.net/mahara/+bug/1415267/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~mahara-contributors Post to : [email protected] Unsubscribe : https://launchpad.net/~mahara-contributors More help : https://help.launchpad.net/ListHelp
