XNAT News & Events

As most of you are probably aware, we released XNAT 1.7 a little while back. We're working on releasing 1.7.1 very soon, with a number of small but important fixes and enhancements from what we've learned installing, configuring, and updating XNAT with the 1.7 release. Here's the beg: if you have any experience with 1.7 and have found any issues that have caused trouble, inconvenience, or worse, please let us know!…
There’s a bug in the latest release of Vagrant that can affect VMs built with the XNAT Vagrant project. The immediate symptom is that you won’t be able to reach a newly created VM through its IP address. The cause is a screw-up in the network interface management code inside of Vagrant that inserts the Ethernet device for the private network IP (that is, the IP that gets set through the Vagrant configuration) with the same ID eth0 as the already existing Ethernet device. Every once in a while,…
XNAT 1.7.0 official release
It's been quite a while coming, but it's finally here: XNAT 1.7.0 is available for general download!
XNAT Workshop 2016 Home Attendees got a first look at XNAT 1.7, hands-on experience building and customizing their own XNAT instance, and a preview of new technologies including Vagrant builds and Docker container services.  Click Here to enter the dedicated Workshop Wiki. Quick links:  Workshop Agenda Workshop Practical Sessions Workshop Attendees
For the IT section of the 2016 XNAT Workshop, Chip Schweiss is releasing a white paper on using ZFS for research data storage. You can download it here: ZFS for Research Data Storage – White Paper 1.0 http://xnat.org/blog/wp-content/uploads/2016/05/ZFS-for-Research-Data-Storage-White-Paper-1.0.pdf Chip is the senior IT architect on the XNAT team and has written previously about XNAT and ZFS storage a number of times. Here are his collected blog entries: 
The XNAT development team will be hosting a 5-day workshop in St. Louis, Missouri, June 6 – 10, 2016. The workshop will include presentations and hands-on practical sessions covering the full range of XNAT functionality. We invite everyone from XNAT novices to experts to join us for a week of lectures, practicals, breakouts, and coding sessions. By the time of this workshop, the new XNAT 1.7 version will have been released.…
Due to the deprecation of the Java plugin on many of the newer browser platforms, we've been working on getting a stand-alone application version of the XNAT Upload Assistant applet going for a while. We have finally succeeded, with the help of install4j https://www.ej-technologies.com/products/install4j/overview.html and the gracious donation of an open-source project license to the XNAT team from the kind folks at ej-technologies GmhB http://www.ej-technologies.com. As a great side effect,…
The XNAT Developer Teleconference for September 2015 will be held this Wednesday, 16 September, 2015 at 10:00 AM CDT. This is a chance for developers, administrators, and users of the XNAT platform and server to chat with the XNAT development team. Topics for this edition include: XNAT 1.6.5 Future development efforts and roadmap Updates from the XNAT sphere Join the teleconference through the XNAT Google+ event page https://plus.google.com/events/cehujrqgaigflcghgguc29d7c3g.…
XNAT 1.6.5 is now available
We're happy to announce the release of XNAT 1.6.5, code-named Lemon Curd. You can download the latest XNAT release here http://xnat.org/download-xnat.html. lemon-curd.png For the 1.6.5 release, we're not sending out separate release notes. Instead we've created a filter on the XNAT issue tracker http://bit.ly/xnat165 that lists all of the issues closed or resolved for the XNAT 1.6.5 release. These cover a large portion of the work done for 1.6.…
The signing certificate we've been using to sign the XNAT applets recently expired. We recently started adding a digital timestamp to the signature process, but this didn't happen before we'd already released a few versions of the applets without timestamps. These timestamps allow digital signatures to remain valid even after the signing certificate expires. Since we didn't have them on earlier releases, the Java security manager no longer considers those releases to be validly sign and,…