Why doesn’t Project Center have an archive routine to move outdated/finished projects to another server?  Some sort of archive integration???

Project data doesn’t need to live forever on the production server.  It would be very nice to have a archive routine to move the project from one server to another.  The data could then still be availible to newforma and would also be moved off of the main server to an archive server.

I can’t imagine too many happy customers trying to archive by having to move data manually then having to go back and update data, check to make sure it’s working, etc…

What are the plans for help with archiving?

Good afternoon,

Thanks for your post on the Newformant!

You are asking an excellent question and your point is well taken.

I’m not sure that we are looking to go down the road of moving files. We take the approach of targeting certain functionality that is not being offered in other solutions. There are other tools like Robocopy that will allow you to mass-migrate your files, so we are not looking to manage the actual movement of the files. There’s a lot of liability there.

Having said that…from the Newforma project meta-data perspective, we are looking to improve the process when moving projects and we are going to offer some much improved processes and tools in our next major release. File movement will still be a process outside of Newforma, but moving Newforma Project Center data will be much easier.

At this time, we do have 2 batch processes for updating the Project Center when projects have been moved.
If you would like to get more background around the process, we can set up some time to take a closer look at the 2 tools.

I hope this is helpful.

Regards,

Eric

I am interested in this process too.  I checked out “Move a project to a New Location on the Network and Repair Broken Links”; got the project location, and found the .NPR file and the associated hidden files.  Under “To move the project to its new location and open it”, copied .NPR & hidden folders (step #3), but step 4 - delete the .NPR and hidden folders from the original location generated an error, as these items are currently being used.  How do you avoid this?

Also, in the “n4 project move” step, the example has both locations on the same system (\\xia).  I assume these can be different (e.g. \\alberti and \\palladio).

Thanks,
Mark

Hi Mark,

It sounds like the Project Center Server or a user(s)may have been accessing the files.
The n4 project move will open the project move tool and you will enter the old and the new paths.

We can talk about this further, please send a note to .(JavaScript must be enabled to view this email address), provide your contact info and a case will be opened. We’ll take this off the forum for the time-being.

I hope this is helpful.

Eric

eric

Support has just explained the Project Move/Project RePath situation to me with the N4 tool.  I misunderstood the terminology of “move” and “repath” in Newforma’s eyes and even though it’s not my first choice of terms it makes sene and it’s definitely sufficient. 

But going along with what the thread owner started, what I would like to see is the NPCS Project Status controlling the tool to achieve what the tool does when a Newforma Admin sets the project status to Archive. 

We typically mass-Archive projects so admittedly the irony of my input is I’d probably still prefer using N4 to batch it all.

Perhaps I’m demonstrating our stupidity, but the Project Status of Archive seems totally arbitrary without the tool being integrated into it.?  I don’t grasp its use/function otherwise.?

Thanks all.

Good afternoon,

Your point is well taken.  I will add this as a +Feature.

Marge