What the "save as" tries to do (not that successfully I guess) is to
rename any url path that starts the same as the project path, then it
renames it. I have a feeling it must be getting confused in certain
circumstances. With the new API we are definitely going to try and reduce
the number of URLs, and then the user will specify how each of those
should (or should not) get moved. In fact this is what "detailed save"
currently does. You are supposed to go in and edit the URL paths by hand
that you want moved. It's just that there are a lot more URLs than we'd
like floating around.
Wayne
On Thu, 17 May 2007, Patrick van der Wel wrote:
> Since I encountered the same directory copying 'feature' during the Save As of
> a project again (and now it also copied some data files too), I looked into
> it a bit.
>
> My guess is that it tries to relocate all files from within the same path as
> where the XML file is located, or perhaps within the same path as where you
> started the Analysis program (upon doing a Save As to a different location).
> If this is indeed the case, I would propose that it would be better to only
> move those files and directories that are within the Analysis-generated
> project directory?
>
> Patrick
>
>
> On Thursday 17 May 2007 09:47, Patrick van der Wel wrote:
> > Ok. I won't try to rename and relocate the project at the same time any
> > more :)
> >
> > Concerning the 'extra' empty directory: is there a way I can try to figure
> > out why it would be doing this? Some sections in the XML file I should
> > examine?
> >
> > Previously I thought that it could be due to the fact that I usually have
> > the ccpnmr program and the data in subdirectories relative to the location
> > from which I start the program, and that the algorithm figuring out the
> > directory structure gets confused by this. For example:
> >
> > CCPNMR program and files in: /home/user/ccpnmr/...
> > Data files in: /home/user/research/data/....
> > Starting Analysis from /home/user/
> >
> > Could this play a role? Note that I do think that this particular case
> > seems less easy to explain though.
> >
> > Patrick
> >
> > On Thursday 17 May 2007 06:19, Wayne Boucher wrote:
> > > Hello,
> > >
> > > This whole "save as..." doesn't work the way we'd really like it to work,
> > > but we didn't want to spend time sorting it out properly because with the
> > > new API (hopefully the next release of Analysis) the storage mechanism is
> > > different.
> > >
> > > I just tried the "save as..." and it seems if you want to change the
> > > directory and the project file at the same time it does't like it. Note
> > > that even if you change the project file the project name stays as it was
> > > because it is frozen in the data model. (We could have put something in
> > > to work around that but didn't.) The "simple save" is intended for the
> > > situation where you want to just move that one directory or rename the
> > > project file (and it looks like doing both is not working). "Detailed
> > > save" is if you need to go in and do fine surgery, so should generally be
> > > avoided.
> > >
> > > With the current API there has been a proliferation of URLs being
> > > created, more than we would have liked. So the chemComp data and the
> > > chemElement data (for example) each get their own URL although they share
> > > most of their path. This already starts to make moving things a pain.
> > > With the new API we are planning on having two main URLs to start with,
> > > the project one and the reference data one. Then we expect there to be a
> > > third URL for user spectra. And possibly more, if the users want more
> > > for their data, but we're going to encourage as few as possible. Because
> > > when you move things you have to change the corresponding URLs. There
> > > will also be the option for additional URLs for user-specific reference
> > > data (e.g. your own chemical compounds).
> > >
> > > One more thing. Currently there is a top-level project file,
> > > MyProject.xml and an associated directory MyProject, with sub-diretories
> > > ccp and ccpnmr which contain most of your project information. In the
> > > new API the top-level project file will be moved into the MyProject
> > > directory. So in future you will only need to pack up one thing instead
> > > of two if you want to copy to another computer.
> > >
> > > Wayne
> > >
> > > On Wed, 16 May 2007, Patrick van der Wel wrote:
> > > > Hello,
> > > >
> > > > I keep noticing that whenever I copy a project via the Save As.. menu
> > > > item, the program creates some subdirectory in the new location. This
> > > > empty directory has the same name as part of the path of existing data
> > > > or file locations in the original project. The funny thing is that it
> > > > does not actually copy any files into this directory. I assume this is
> > > > related to the 'smart feature' of trying to guess new related paths,
> > > > but I can't figure out a clear pattern that would explain it in this
> > > > case.
> > > >
> > > > The other thing I noticed is that when I click the 'simple save'
> > > > button, the program erases the proposed new Project file name and
> > > > resets it to the original name, but does proceed to copy the project
> > > > under that name to the newly selected directory. Actually, even the
> > > > Detailed Save button seems to cause this type of behavior.
> > > >
> > > > Any ideas? Is any of this the expected behaviour?
> > > > Patrick
> > > >
> > > > PS. I do notice that the new empty directory is referenced as a
> > > > "movedirurl" item like: <Url _ID="_165" serial="11" protocol="file"
> > > > name="movedDirUrl">
>
|