Moodle Portfolio plugin for Mahara creates a bunch of identically-named journals in the Mahara side

Bug #794364 reported by Dirk Meyer
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mahara
Triaged
Wishlist
Unassigned

Bug Description

The titles of journals that were exported from moodle are the same for all. They read 'data Imported from Leap2A export from Moodle for Admin User.'
It would be great if the original tile for the moodle post would come across. Sceen shot is attached.

Moodle 2.o
Mahara 1.4RV2

Tags: moodle
Revision history for this message
Dirk Meyer (dirkca68) wrote :
Revision history for this message
François Marier (fmarier) wrote :

Hi Dirk,

Could you please attach (if possible) a sample exported file?

Cheers,
Francois

Changed in mahara:
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Dirk Meyer (dirkca68) wrote :

Hi,

I came across this on the moodle tracker. The Mahara_Journal.png seems similar to what happens to me. http://tracker.moodle.org/browse/MDL-28022
Which export file should I be looking for?

Changed in mahara:
milestone: none → 1.7.0
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.7.0 → 1.8.0
Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.8rc1 → 1.8.0
Aaron Wells (u-aaronw)
Changed in mahara:
importance: Low → Wishlist
milestone: 1.8.0 → 1.9.0
assignee: nobody → Aaron Wells (u-aaronw)
summary: - Non unique titles for moodle forum exports
+ Moodle Portfolio plugin for Mahara creates a bunch of identically-named
+ journals in the Mahara side
Revision history for this message
Aaron Wells (u-aaronw) wrote :

I've noticed this as well. There is a Moodle "portfolio" plugin that allows data from Moodle to be exported to Mahara. Each time you do this, it creates a new Journal in Mahara with the name "data Imported from Leap2A export from Moodle for {firstname lastname}".

It would be non-trivial to fix this, so it's not on our roadmap at the moment unless we get some funding or there is a community contribution for it.

I recently looked into fixing this for a client (who unfortunately declined to fund its fixing). It turns out to be quite tricky. The way the portfolio plugin works, is that it just generates a leap2a file with the Moodle content, and then Mahara imports that fragmentary leap2a file. Mahara's failsafe mode for importing a leap2a, when it's not able to figure out any other content type to map it to, is to import it as a new journal following that naming title.

There are a few possible fixes. Maybe the easiest would be to structure the leap2a in a way that allows Mahara to process it into a Page or something, or a journal with a better title.

Another way to go, according to my notes, there's a "steal_control()" method one could use during the Moodle->Mahara export process which would allow Mahara to drive the process a bit. Using this Mahara, could present the user with a list of journals, and let the user pick which one the content should wind up in. Then you'd need to add some metadata to the leap2a file to indicate this, and then alter the Mahara leap2a import process to pick up on that metadata and use it.

Aaron Wells (u-aaronw)
Changed in mahara:
milestone: 1.9.0 → none
tags: added: moodle
Changed in mahara:
assignee: Aaron Wells (u-aaronw) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers