Re:[platform-core-dev] RFC 0002 - Importing and Exporting Projects

["Greg Adams/OTT/OTI" <Greg_Adams@xxxxxxx>]

Randy's suggestion is an interesting variant on my observation. I was observing that if the meta data was just always stored as a file then no special facility/api is needed. Randy's interesting variant says if we really have to store it not as a file, then all we need is the ability to drop it into a file on export, and to create a project using the file (which we could call on import). 

I would probably use Jeff's argument from the marker article (I am not saying he would make that argument here) which is that I am concerned this feels like a point solution, which may not provide enough UI flexibility, and might be pushing on the wrong part of the solution (e.g. export api, vs. dealing with the meta data head on). Hopefully I am expressing this concern properly.

/Greg

Randy Giffen 12/04/01 11:22 AM

To:        platform-core-dev@xxxxxxxxxxx         cc:        Karice McIntyre/OTT/OTI@OTI, Greg Adams/OTT/OTI@OTI         Subject:        Re:[platform-core-dev] RFC 0002 - Importing and Exporting ProjectsLink

Tod I am copying you because you have done the most recent work on import/export. 

I summary I don't understand why core would want to get into creating a projectExportFile. It seems to be just a zip that includes some metadata. 
Why doesn't core simply add api to produce/read this metadata description? A file with this metadata could be added to the project/read from the project on export/import using existing Folder/Zip wizards. 

<snipped out the rest of randy's email >