Feature #432

categories in cpo-export

Added by Anonymous over 10 years ago. Updated over 9 years ago.

Feature implemented
Sven Vanpoucke
Target version:
Start date:
Due date:
% Done:


Estimated time:


Now categories are lost in a cpo-export.
As this is the only way for a user to back-up his data, it is important to keep the category structure intact, esp. as categories will be very important to keep the repository well organized.



Updated by Sven Vanpoucke over 10 years ago

  • Assignee set to Sven Vanpoucke
  • Target version changed from 1 to 2

Updated by Sven Vanpoucke over 10 years ago

  • Status changed from New to Needs testing
  • % Done changed from 0 to 100

Added categories in cpo export and import (the categories will be created from the top of the selected category. To keep the integrity of the category structure, we have not done a name check to avoid losing a parent in a tree structure)


Updated by Anonymous over 10 years ago

There is still a problem when importing a cpo: the status of the publication links is (of course) that of the export.
When importing it is a real possibility that these are no longer relevant. I understand that is is not easy to automate a solution to this, but it should not be too difficult to offer the user the choice to keep or do away with the 'publications' on import.
The problem now is that there is no easy way to 'unpublish' (delete, etc.) those imported items, esp. if those are 'false' publications, i.e. publications that are traces from the export but no longer real facts after import.


Updated by Sven Vanpoucke over 10 years ago

Publications aren't exported, nor are they imported again. The reason why a delete is impossible sometimes is because it is either an attachment, an included object, a child from a complex learning object or an object who has children. In those cases you first need to unlink those objects from each other (remove attachments, includes and disband complex learning objects)


Updated by Anonymous over 10 years ago

Of course as a user I do not know what precisely is exported and imported. I can only see that there are problems after import.
As far as I as a user can judge, there is more to it then what you state. There are documents that as far as I know were only published in courses, that cannot be deleted after import in e.g. a new category: doing so there should not be any interference with existing objects and their links & publications.
Anyhow, whatever the cause, the user has no way to see whether a specific object is part of a complex entity: it is not shown in the item's properties, nor anywhere else, at least as far as I have discovered. In fact you have the know the complex entity or publication place to check whether an object is linked there are not. This is unworkable for a user with even a limited number of (complex) objects .


Updated by Sven Vanpoucke over 10 years ago

  • Status changed from Needs testing to Feature implemented

The links are not visible at the moment this is a feature that still needs to be created. I don't think this is a real issue of the importer / exporter but rather a lack of possibility to view links to an object. Therefore i'll close this object for now and if there are new problems with the import/export we can open it again


Updated by Stefaan Vanbillemont over 9 years ago

  • Project changed from Chamilo LCMS Connect to Repository
  • Category deleted (4)

Updated by Stefaan Vanbillemont over 9 years ago

  • Target version changed from 2 to 1.0.0

Also available in: Atom PDF