Bundle Exports

The purpose of "Bundle Exports" and "Advanced Export" is to facilitate the flexible export of packaged bundles from a Metaflow project. It is only useful where a channel is not yet supporting full submission preparation and allows the exporting of the semi-prepared submission into a native directory structure ready for manual completion and subsequent delivery.

Once the user has successfully packaged a project, he may then click the bundle export link. In the vast majority of cases, this should allow the creation of a complete, exported directory structure according to the channel's requirements.

Advanced Exports and Project Exports

Advanced Exports

However, in certain circumstances, there may be a need to produce something more bespoke than the standard "Bundle Export" provides. In these cases, the "Advanced Export" should allow more flexible conditions. For example, a channel for a one-off delivery may need all of the JAD and JAR files in a single directory and the standard "Bundle Export" provides sub-directories which are not required. In this scenario, the user would package normally and use the "Advanced Export" as described below.

The user clicks on the "Advanced Export" link to open the export format, and select File system (directory) or Archive File (ZIP)

click on the "File type" button will bring the screen below

The user would then browse to or manually fill-in the target destination and click finish. Please note that in certain situations you may get overwrite warnings during "Advanced Export". These warnings need to be considered carefully so as not to lose files during this process.

Project Export

Project Export uses the same Export wizard as Advanced Export. The main difference is that Advanced Export is run from inside a plan and will pre populate itself with the contents of the plan to be exported. Project Export will populate itself with the top project node to export the entire project contents. Either may be manipulated to export what you require.