[daisy] [JIRA] Updated: (DSY-450) allow to define collections and document-types to be exported (even if no documents in the export-set are using them)

[Bruno Dumon (JIRA)]

     [ http://issues.cocoondev.org//browse/DSY-450?page=all ]

Bruno Dumon updated DSY-450:
----------------------------

    Fix Version: 2.1

> allow to define collections and document-types to be exported (even if no documents in the export-set are using them)
> ---------------------------------------------------------------------------------------------------------------------
>
>          Key: DSY-450
>          URL: http://issues.cocoondev.org//browse/DSY-450
>      Project: Daisy
>         Type: New Feature
>     Reporter: Marc Portier
>     Priority: Minor
>      Fix For: 2.1

>
> Currently the export-set format can only describe the documents to be included in the export
> Automatically this will pull related definitions for collections and document-types (and parts and fields) into the export so they get created during import (actually, collection-definitions are not even part of the export, they are just created as needed during import)
> When using the export in a 'project development' scenario however it is useful if document-types and collections could be created during import even if the imported set doesn't actually contain any documents for those types or collections.
> Implementing this would therefore assume
> 1/ a change to the export-set.xml file format (see [1]) so it can list extra collections and document-types to be included in the export, and
> 2/ a change to the export format [2] so it can contain collections to be explicitly created
> [1] http://cocoondev.org/daisydocs-2_0/impexp/335-cd.html
> [2] http://cocoondev.org/daisydocs-2_0/impexp/332-cd.html

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira