Hello,
You can edit the top-level project file by hand. The paths for the
spectra data are determined by what is called in the (old) data model a
dataLocation. In terms of Python code, the actual path is
os.path.join(dataLocation.url.path, dataLocation.path)
I am pretty sure that the way things have been set up you won't need to
edit the dataLocation.path but you will need to edit the corresponding
dataLocation.url.path. As an example, in my test project file I have:
<DataLocation _ID="_62" serial="2" url="_61">
<path>edl387_5.spc</path>
</DataLocation>
and Url _61 is:
<Url _ID="_61" serial="5" protocol="file" name="dataLocation">
<path>/Users/wb104/edl387</path>
<dataLocations _IDREF="_60"/>
<dataLocations _IDREF="_62"/>
<dataLocations _IDREF="_63"/>
</Url>
It is likely that this is the path you will want to change. If there are
a lot of Urls with similar paths that need editing then a global replace
is probably the easiest option. (Backup the original project file first
just to be safe!)
Wayne
On Fri, 14 Mar 2008, Mark Pfuhl wrote:
> Is there a simple trick to deal with changed paths for spectra when a
> project was copioed between users/computers? I often copy a project of my
> students for checking into my account/my computer and then I have the
> unpleasant task of changing the paths of all the spectra in the project one
> by one oven though all the names of the datasets/spectra stay the same, only
> the basic path to the spectra has changed. This is something that could be
> changed once for all spectra and everything should be OK. Is it possible to
> edit one of the files by hand or would that spell disaster?
> thanks,
> mark
>
|