The CBICA center currently has 9 tools on NITRC and that will increase as we move more of our software distribution to NITRC. It's a great platform, but setting up new projects, each having multiple & similar associations (ie., each of the 9 is from the same source, they have similar dependencies, etc) is tedious via the GUI.

Some possible ways to enhance this are:

• Enable downloading of a text-based representation of the associations from project "A" (ie., a CSV file, XML, etc) and allow that to be uploaded to project "B"
• Enable associations to be copied from project "A" to "B" via the web interface
• Enable wildcard specification of associations; for example, select "is from the same source as" in the first dropdown box, then we would enter "^CBICA*" (matching the naming convention used for all of our tools on NITRC) which would be expanded into the current 9 projects

We have added the ability to modify basic project information (including project associations) through a text file; see http://www.nitrc.org/plugins/mwiki/index... for details.

We would like to extend this functionality so you don't have to log in to the web front end to update this information (but instead be able to update project information as you update your code), but hopefully this is immediately useful for your needs.

Hello,

This feature request is currently under active development and will most likely be rolled out with our next release.

The next release is scheduled to happen in mid-March.

Any update on this enhancement?

Is there anything we could do to help with the development side?

We've now got 17 projects on NITRC and will be adding at least 5 more very soon. As each project comes from the same research group (CBICA), it becomes increasingly difficult to manually set up the 'associations' between different projects.

At the same time, having our projects on NITRC and having those associations is very valuable, and something we want to maintain accurately.

Thanks for the feedback.  These are good ideas; I've opened an internal ticket for the issue.