Hello,
The name it uses is the name given inside the v1 top level project file
even if the file name is different. And that name would normally be
whatever it was called originally (since technically the project name
cannot change unless you bypass the API).
If you want a different name then I would recommend that before you do the
upgrade you either edit that v1 top level project file or in v1 Analysis
at the prompt do:
>>> top.project.__dict__['name'] = 'whatever'
(The use of the __dict__ bypasses the API.) And then do a save.
You could do related trickery in v2 but it's better to do it before
upgrading.
So inside your specific v1 top level project file it says
<?xml version="1.0" encoding="UTF-8"?>
<_StorageUnit time="Wed Aug 4 19:49:01 2010" release="1.1.a3"
packageName="memops.Implementation" root="" originator="CCPN Python
XmlIO">
<Project _ID="_1" isStored="true" isModifiable="true" name="arod_081110"
package="memops.Implementation" format="xml" url="_2">
<path>arod_100729.xml</path>
And you can see that the name is "arod_081110" but the file is called
"arod_100729.xml", so they are not necessarily related, and it is the
former that determines the name of the project (and also file name and
project directory) after the v2 upgrade.
Wayne
On Tue, 7 Sep 2010, Ben Goult wrote:
> Hi
>
> I recently used the Upgrade server, it upgraded my project successfully, however in doing so the name of the project changed. The project I uploaded was called arod_100729.xml and the converted project I got back was called arod_081110 (even tho the tgz file was called arod_100729_Cnvtd.tgz).
>
> This arod_081110 was the title of the original project from which I created the 100729 (using "save as") project so it appears that it may have grabbed the old name and used it?
>
> Cheers
>
> Ben
>
|