NIH | National Cancer Institute | NCI Wiki  

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

caDSR tooling requirements arise in many settings. By using one of the means described below you will ensure your ideas have been successfully communicated and documented. Software requests for enhancements are acknowledged by the caDSR team with the creation of an item in our tracking database and assigned a reference number, making it easy to track your favorite request! If it doesn't have a GForge tracker number, we haven't yet realized it as a requirement.

Where requirements come from:

Requirements have come from the following sources, some of which are no longer valid, but many of which represent continued areas of need:

  • caDSR caCORE Software Users Meetings. Visit the caCORE Users Meetings and Forums the caDSR Content Meeting Materials wiki page for meeting information, links to past meeting presentations and meeting notes, and links to status and planning information. As the release cycle progresses we begin a public review and prioritization, drawing from variety of factors to make final "in/out" decisions. We conduct user feedback sessions throughout the design and prototype phases.
  • Subscribe to Through the caDSR Users LISTSERV. Post ideas, participate in discussions, where ideas are posted and participants can discuss them. All postings are read, and if a requirement is suggested, it's entered into our tracking system once confirmed.

  • Prior requirements initiatives, some of these are linked to the SI Requirements wiki
  • Personal communications: If you have a specific idea or suggestion you want to discuss personally with Ideas or suggestions are submitted to Dianne Reeves (Program Manager for caDSR Content),  and Denise Warzel (Program Manager for caDSR software) feel free to contact her directly.

caDSR Futures

NCI is planning to modernize the aging decade-plus old caDSR semantic metadata infrastructure and tools to simplify, streamline, and make it more useful, more accessible, easier to integrate into research and health care processes and systems, and better support community comment, curation and harmonization of content and data.  While the requirements process has been ongoing, documenting what we have been hearing began last fall, and we are already collaborating and aligning with sister NIH ICs, national, and international metadata initiatives.  We recently decided it would be very useful to seek broad community input via an RFI.  Please see CHILD PAGES below for links to the RFI document and the requirements draft, which will be updated as it evolves with community input.

...