NIH | National Cancer Institute | NCI Wiki  

Contents of this Page

Tired of waiting for implementation of your favorite feature or bug fix? The NCI CBIIT Open Development Initiative solicits contributions to caDSR from external development teams!

The primary mission and descriptions of the caDSR components are found on the caDSR overview page. Projects for which we are accepting proposals may pertain to one component only or span several, or may pertain to an integration of caDSR tools or caDSR and other CBIIT applications. The expectations for a "unit" of contribution are described in the Unit of Contribution Section in more detail but essentially a contribution can be an extension to the caDSR UML Model, an architecture or code change, a functional enhancement, a documentation enhancement or a training module. The specific caDSR components for which we are accepting proposals are:

See below to find out how to participate.

Wish List

We will accept and review all proposals from potential developers, but we also have a 'wish list' for which we would really like to receive proposals.

  • Enhanced search algorithms for finding the best content
  • Bulk import – Web enabling Excel loader and XML loader
  • Registry to Registry Exchange/interoperability
  • "Read Only" caDSR
  • Multi-language support
    • Application level – display UI in other languages
    • Content Level – display content in other languages but UI in English
  • HTML UI bugs Display
  • MAC compatibility for Excel Addin
  • Web service CDE matching functionality similar to that found in the CBIIT CRT desktop application
  • Enhance and extend Form Builder to allow users to create eForms with persistence tier
  • Data mining and analytic tools based on the ISO 11179 metamodel and NCI Thesaurus for finding related CDEs
  • Update caDSR UIs to the official NCI User Interface Standard. This includes 508 compliance, menu placement and content, and the header and footer banners.

How do I participate?

We will evaluate proposals as they are received and work with you on a plan to incorporate accepted ideas into the caDSR code base. Once the idea is slated for a release, enhancement or change order and prior to moving from the development environment to quality assurance and integration testing, OSDI contributors along with caDSR core team will reach a "go" "no-go" decision on each item based on unit testing results, the same as we do with internally developed code.

  • Virtual Software Development team meetings are held regularly. These informal communications meetings are an opportunity to discuss software development issues, ideas and release plans. Contributors will be invited to attend. This is where you ask for and get help and feedback on specific development items, exchange ideas or demonstrate prototypes, and have direct contact with the caDSR development team.
  • The caDSR Software Developers Listserv offers an opportunity to discuss caDSR specific issues with other caDSR developers.

Join us in our exploration of semantic interoperability and the future of bioinformatics computing!

Contact the caDSR development team through Application Support to begin the process. Be sure to include "caDSR OSDI" in the subject line. You are invited to subscribe to the caDSR Users list and to send a message to the list to discuss your ideas, garner consensus, or gather requirements. For email correspondence to the listserv, use "OSDI" in the subject line to help make these types of email threads easily identifiable.

Contributor Skills

  • Model Driven Architecture (MDA) is expected to be understood and utilized by contributors.
  • For suggested caDSR model extensions, an understanding of the ISO 11179 is expected and should serve as the launching point.
  • Demonstrated skills are needed in appropriate programming languages.
  • Understanding is needed of existing applications and functionality and role of caDSR within caCORE.

Unit of Contribution

A unit of contribution can be as small as a bug fix or be a new feature or whole new tool. Contributors will be asked to describe the requirements their proposal is intended to meet in the form of a use case. A proposed unit of contribution will be evaluated based on contributor skills and fit within each of following areas:

UML Model Extensions

  • caDSR model extensions including addition of new objects, new relationships or modification of existing objects

Architecture/Code Changes

  • New search or search paradigm
  • Extension to existing architecture or interoperability with other applications (that is, interaction with other ISO 11179 registries)
  • User interface changes
  • Bug fixes

Functional Enhancements

  • Extension to an existing tool (that is, take existing functionality and add additional capabilities to it)
  • New data source for an existing function (for example, creation and access of non-EVS vocabulary source for concept searches)
  • New functionality (for example, display content in different language based on existing model attributes; role based “Portals”)

Documentation Enhancements

  • New or enhancements to Users Guides or Technical Documentation

Training Enhancements

  • New training module or tutorial
  • Enhancements to existing training modules such as a series of exercises or creation of 'gold standard' caDSR content

 

 

  • No labels