GitLab

Resume import now done!!
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This doesn't replace the mahara:profileicon check, but suppliments it.
Now, if an image is related to the persondata element, it is considered
to be a profile icon. In future, we might use a more explicit 'depicts'
relationship.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

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

At export time, we export a few links in our persondata element that
point to profile icons. The icons themselves link to the persondata
element. In lieu of anything better, we're currently using 'related' for
this.

At import time, we look at links in the persondata element, and the
first 'related' one we come across that is a profile icon, we set as the
default.

This conforms with what the list people were doing, so at least for this
version of the spec we'll be doing it consistently with the others.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

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

This might have misled Penny:
http://wiki.cetis.ac.uk/2009-03/LEAP2A_relationships#relation



I have e-mailed the list asking whether it should be renamed to
'related'.
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>

This saves needlessly checking for options when we already found one.
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>

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>

We do this by looking for whether the items are connected to one of the
special Mahara groupings. If they are, we read the display order and use
it - otherwise, the display order isn't used, as we assume the display
order is for some other selection that is irrelevant to Mahara. This
assumption might need to change in future.
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>

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

Move the 'description' field for books in LEAP export to be on the contribution entry; import it from there.

Part two of the previous commit to clarify the meaning of the
description field on books.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

This prevents confusion over whether the description field for book
artefacts is for the book description, or for the description of your
role in relation to the book.
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.

Still relying on a response from the LEAP list about how we should
represent these properly.
Signed-off-by: Nigel McNie <nigel@catalyst.net.nz>

We export an assistant entry that has this information, so there's no
need to duplicate it.

(cherry picked from commit 23670d2e5d77f930bfc79ecd5624ccf6e6b126e7)