This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 198138 - Export needs button to select related resources
Summary: Export needs button to select related resources
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Cosmos (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: David Whiteman CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-27 13:32 EDT by David Whiteman CLA
Modified: 2012-01-03 13:47 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Whiteman CLA 2007-07-27 13:32:19 EDT
Based on a call we had with the SML/CML workgroups, one requirement I heard was to have only related resources exported.  I think of this like the Eclipse feature where you can select required plugins when you select a plugin.  So, in the export interface, if you select Student1 for example, and click the select related button, all other instances referenced by Student1 and all schema files necessary for Student1 and its related instances would be selected.

The round trip scenario, with a twist, I think is what drives this requirement.

1. Import SML-IF file A into repository folder B
2. Import SML-IF file C into repository folder B
3. Open SML-IF export wizard, and export folder B.  The resultant SML-IF contains resources from both file A and file B.

I believe they would like something like this (we'd of course want to clarify with them before implementing):
3. Open SML-IF export wizard, select folder B.
4. Select one resource originally from SML-IF file C
5. Select button named "Select related resources"
6. Other resources are now checked that are related

We could accomplish this two ways.  One is to walk all the references and schema imports for a file to find related resources.  Another is we keep a list on import what set of resources go together in the metadata, and use that information when we export.  I.e. when we import SML-IF file C, we mark all <file> elements in the metadata that they came from file C, and therefore when related resources are checked, it is based on this information.