Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This puts the right artefacts back into Views.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

The other base class methods had detailed descriptions, so this only
seems fair.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

We unconditionally json_encode it on the way out, so this is necessary.

Allows us to store arrays in the export, too.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This is necessary so blocks can make decisions about importing based on
the owner.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Found this bug while doing View import. Using uksort passes the keys in
for sorting, which is not what the sorting function was actually
expecting. uasort is what I meant to use.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This is so that we know all artefacts have been created, so that the
views they're in can also then be set up.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

The LEAP code now changes the XML generated at export time back into the
config to use for this method.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This is much more reliable than looking at the entry content, and means
we can easily get at the configuration for the blockinstances.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Now we just have to get their configuration right!

Ah crap, I said "just", I guess I just volunteered myself.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Imports all content into one big text box.

Manages to import title, summary, ctime and mtime too. Still have
ownerformat to do.

The next step after this is to try and detect if we're importing a
Mahara view, and if so, create the right blocks and artefact links for
it.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This should make us a little more able to find them in other exports.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Some other portfolio systems don't declare them properly. This really
harms interoperability, but it's not our fault.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Use it everywhere we're looking for category schemes.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Call it everywhere we're looking for rdf types.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

Saves a bunch of copy+pasted code.

Should be useful in many places - in particular, the resume.

Use this hook instead of hard coding a call to the Internal plugin's
import_author_data method.

This allows the resume to also hook in and grab the personalinformation
fields out.

It now works the way it worked for import. If the file exists, it has to implement the class. If the plugin doesn't want to implement it, it doesn't provide the file.