Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Save category description in Moodle XML import/export: Difference between revisions

From MoodleDocs
Line 8: Line 8:


== Current XML structure ==
== Current XML structure ==
If current category has not parent then
<pre>
<pre>
<question type="category">
<question type="category">
   <category>
   <category>
     <text> $course$ / [ $parent category name$ / ] $current category name$ </text>
     <text>$course$/$category$</text>
   </category>
   </category>
</question>
</question>
</pre>
</pre>


The amount of block [ $parent category name$ / ] can be more or equally to zero.
else
 
<pre>
<question type="category">
  <category>
    <text>$course$/$parent$/$category$</text>
  </category>
</question>
</pre>


== Proposed XML structure ==
== Proposed XML structure ==

Revision as of 12:08, 18 October 2014

What is not saved?

At this format of import/export is not saved:

1. description of the current category,

2. description of parental category(categories).

Current XML structure

If current category has not parent then

<question type="category">
  <category>
    <text>$course$/$category$</text>
  </category>
</question>

else

<question type="category">
  <category>
    <text>$course$/$parent$/$category$</text>
  </category>
</question>

Proposed XML structure

If the category has not parent then

<question type="category">
  <category>
    <name>
      <text>$current category name$</text>
    </name>
    <description>
      <text>Description of category</text>
    </description>
  </category>
</question>

else

<question type="category">
  <category>
    <name>
      <text>$parent category name$</text>
    </name>
    <description>
      <text>Description of category</text>
    </description>
    <category>
      <name>
        <text>$current category name$</text>
      </name>
      <description>
        <text>Description of category</text>
      </description>
    </category>
  </category>
</question>

Old export compatibility problem

The proposed structure is not compatible to the old.

I consider that proposed structure is possible to use as an independent format.