Simplest way of moving an entire project from one Xnat server to another.
James Allsopp
Herrick, Rick
It really depends on what you mean by “move” and what kind of data is already on the server to which you want to move the project.
There are a couple of relatively easy ways to duplicate the project structure on the target system:
- The XSync plugin can maintain a project on one system by initially copying the project from the source to the target, then updating the target with changes on the source
- You can write a “project crawler” type of application using something like pyxnat or xnatpy to pull the project, subjects, data, etc. from the source and then push those to the target
The drawback with these approaches is these really are shallow copies, i.e. you’d have the project, all the subjects, sessions, etc., but you’d lose the history and provenance of the data on the original system. You’d also have different underlying metadata, such as unique identifier properties that aren’t normally exposed, like row IDs for experiments and associated metadata rows.
If you want a “deep copy”, with the same data, history, metadata, etc., the only way to do that is to dump the database on the source system and import it on the target system, along with copying the actual data files (i.e. the archive folder). This is a very blunt instrument, since you’re copying the entire XNAT system rather than just the desired project (once the copy is completed, you could go in and delete all the other projects), and means that the target system is an entirely new deployment, i.e. you can’t integrate this approach into an existing XNAT.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
Phone: +1 (314) 273-1645
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
xnat_discussi...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/xnat_discussion/CAD3_CNNFDJhSPJtUpZKKn6sNK8D%2B8sPAVKn1dmAXkpqh0rJYpQ%40mail.gmail.com.
The materials in this message are private and may contain Protected Healthcare Information or other information of a sensitive nature. If you are not the intended recipient, be advised that any unauthorized use, disclosure, copying or the taking of any action in reliance on the contents of this information is strictly prohibited. If you have received this email in error, please immediately notify the sender via telephone or return mail.
Elijah Rockers
On Friday, March 6, 2020 at 9:21:00 AM UTC-6, Herrick, Rick wrote:
It really depends on what you mean by “move” and what kind of data is already on the server to which you want to move the project.
There are a couple of relatively easy ways to duplicate the project structure on the target system:
- The XSync plugin can maintain a project on one system by initially copying the project from the source to the target, then updating the target with changes on the source
- You can write a “project crawler” type of application using something like pyxnat or xnatpy to pull the project, subjects, data, etc. from the source and then push those to the target
The drawback with these approaches is these really are shallow copies, i.e. you’d have the project, all the subjects, sessions, etc., but you’d lose the history and provenance of the data on the original system. You’d also have different underlying metadata, such as unique identifier properties that aren’t normally exposed, like row IDs for experiments and associated metadata rows.
If you want a “deep copy”, with the same data, history, metadata, etc., the only way to do that is to dump the database on the source system and import it on the target system, along with copying the actual data files (i.e. the archive folder). This is a very blunt instrument, since you’re copying the entire XNAT system rather than just the desired project (once the copy is completed, you could go in and delete all the other projects), and means that the target system is an entirely new deployment, i.e. you can’t integrate this approach into an existing XNAT.
--
Rick Herrick
Sr. Programmer/Analyst
Neuroinformatics Research Group
Washington University School of Medicine
Phone: +1 (314) 273-1645
From: "xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com>
Reply-To: "xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com>
Date: Tuesday, March 3, 2020 at 7:45 AM
To: "xnat_di...@googlegroups.com" <xnat_di...@googlegroups.com>
Subject: [XNAT Discussion] Simplest way of moving an entire project from one Xnat server to another.
Hi,
I need to move an entire project from one Xnat server to another, is there a relatively painless way of doing that?
Thanks
James
--
You received this message because you are subscribed to the Google Groups "xnat_discussion" group.
To unsubscribe from this group and stop receiving emails from it, send an email to xnat_di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/xnat_discussion/CAD3_CNNFDJhSPJtUpZKKn6sNK8D%2B8sPAVKn1dmAXkpqh0rJYpQ%40mail.gmail.com.