NIH | National Cancer Institute | NCI Wiki  

Top 10... or so

Item

Gforge #

Gforge Opened Date

caDSR Release

Comments

4.0.0.0 Scope Documents

1. Complete Value Meanings as full administered components. Implement maintenance editing of all VM metadata.

1230

5/14/2006

4.0.0.0

11/09/2010: Implemented in caDSR 4.0

12199 - in Admin
12205 - in Curation

2. Keep caDSR Concepts in synch with EVS term changes; maintain original definitions as Alternate Definitions?; document when a concept is retired, merged, or replaced by EVS.

1332

6/6/2006

n/a

07/02/2009: This is being worked on in conjunction with the Metadata Cleanup activity

11/09/2010: This is being reconsidered after the Metadata Cleanup activity is completed.
09/19/2008: SA presentation: possible for 4.0.0.1

7/11/2008 - need to get off of the Oracle application server, so don't have resources to do this
DW Comment: a. Already in scope, independent of 4.0 but probably completed after

---

3. Curation: Provide full maintenance functionality for all caDSR metadata. Enhance maintenance tools to show all relationships and usages to the metadata being edited/maintained - for example: show all Value Domains using a Value Meaning, all Data Element Concepts and Value Meanings using a Concept.

---

---

Maintenance Function :
4.0.0.2 or 3 - Concepts
4.0.0.3 - CS/CSI
Show Relationships
4.0.0.3 - Curation

11/09/2010: In light of SI V2, these items are being addressed only as needed.  See current caDSR Scope items from the Core Infrastructure Scope Planning Index documents for the caDSR Curation Tool for related features.

---

4. Curation: Provide the ability to set a preferred name or definition for an administered component from the available Alternate Names and/or Definitions and have that display in the Brower

4542

3/12/2007

Curation Tool 4.1

11/09/2010: See caDSR Curation Tool 4.1 Planning Document found at the CORE Infrastructure Scope Planning Index page

7/11/2008 - DW: new technology will be used to display to create something like a stylesheet Need to be able to set in metadata.
The existing tracker only address the Definition. The preferred definition is already displayed in the CDE Browser and users can edit/change it now, however I think this may be the feature we have previously discussed that would allow users to more easily designate which definition is "preferred" without losing the system generated definition. This may require a domain model change to capture this information and also t change the UIs to be driven off the "Preferred indicator" instead of displaying the current preferredDefinition field.

---

5. Resolve business rules and methodology to add semantics to Value Domains. Remove current wizard that calls the concepts Objects and Properties. [Wizard change is in progress.] Consider using CDs to aid in identification/semantics.

---

---

Completed 3.2.0.5/6

11/09/2010 Implemented in 3.2.0.5

a. Value Domains already have the underlying capability to have semantics associated with them. Once the business rules are nailed down, this can be implemented via UI changes. But, this is unlikely for 4.0 timeframe. This will need to be carefully thought out and vetted with the community before implementation so that people understand the difference between semantics that differentiate one VD from another, without becoming confused between VD, Rep Term and CDE semantics. Better usage of the ISO 11179 Conceptual Domains needs to be evaluated as part of this request.
DW: 5b. Remove current wizard that calls the concepts Objects and Properties.
b. Already in scope for Curation Tool 3.2.0.5

---

6. Curation/Business Rules: Simplify rules for changes to PVs and VMs when they have been used on a form.

---

---

Curation Tool 4.1

11/09/2010 See Core Infrastructure Scope Planning Index for links to Curation Tool 4.1 Scope

Please document the rules in a tracker in GForge. Some may be possible for 4.0 if the rules can be vetted and agreed upon quickly, but could also be included in post 4.0 release if it takes longer...

---

7. Browser: Add ability to 'browse' CDs, DEC, VD, VM, PVs, Concepts, Object Classes, Properties, and Representation Terms. Customize the list of metadata to display in a results list. Provide ability to find of all uses of an administered component - get associated.

16748

---

Curation Tool 4.0.2 allows public users to use these features

11/09/2010  Implemented ability for public user (not logged in) to use the Get associate feature.

DW: This capability is available in the Admin Tool. For example, from a guest account (guest/guest), you can browser all CDs, see all associated Value Domains and Value Meanings. Please provide a prioritized list of which browsers are highest priority and how they might differ from the existing capabilities of the Admin Tool.

---

8. Browser: Customizable download reports - both Excel and XML - both content and order of the report. (Gforge #1333)

1333

6/6/2007

Curation Tool 4.1

11/09/2010 See CORE infrastructure Scope Planning Index for Curation Tool 4.1. Scope

DW: also a requirement for caGRID
DW: We've been waiting on SDK features for this, will look into it, if not eminent, we will figure out how best to deliver in near term.
09192008: SA presentation: Maybe customizable download in 4.0.0.1??

---

9. Curation: Add ability to subset and relate Value Domains.

---

---

---

11/09/2010  Will be addressed in SI V2

DW: a. Not 4.0, will make priority for 2008 mid year increment.

---

10. Curation: Allow download of search results or saving of file in format that can be imported into Excel.

11372

1/13/2008

---

11/09/2010: this has been raised again in light of the ability to upload content from a formatted Excel spreadsheet using the UML Loader.  Users would ike the ability to export CDEs in this format so they could modify the spreadsheet and upload CDEs in batch.
https://gforge.nci.nih.gov/tracker/index.php?func=detail&aid=11372&group_id=33&atid=205

---

11. Curation: Add ability to edit previously created Reference Documents. This should be supported for a single administered component and as a batch process for a group of administered components.

---

---

Curation Tool 4.1

See CORE Infrastructure Scope Planning Index for link to Curation Tool 4.1 Scope

7/11/2008- DW: Defect and will be corrected.
Need clarification - perhaps it's a block edit for reference documents independent of CDEs

---

12. Improve metadata batch loading - for example, provide the ability to register a list of concepts or administered item names and definitions from a text file or spreadsheet.

7043
16226

6/5/2007

PV batch load 4.0.0.2

11/09/2010 the Excel Template Loader can be modified to allow this feature - see Core Infrastructure Scope Planning Index for caDSR SI V1 Serivces 1.0 Scope

7/11/20008 DW: Align with NMDP forms, new search capabilityes, etc. https://gforge.nci.nih.gov/tracker/index.php?func=detail&aid=7043&group_id=295&atid=1243

---

13. Remove Test and Training contexts from all display and searches as the default condition.

2587

8/9/2006

Curation Tool 4.0.2

https://gforge.nci.nih.gov/tracker/?group_id=33&atid=205&func=detail&aid=2587

---

3. Curation: When searching for existing Permissible Values set default to all Conceptual Domains.

---

---

Curation Tool 4.0.2

11/09/2010 Implemented in 4.0.2

DW: The search for VMs to create new PVs in a VD is restricted to the CD associated with the DEC by design per the ISO 11179 standard. The primary purpose of CDs is to group VMs that are appropriate for the DECs associated with the CD. As the body of enumerated VDs grows, this existing feature will provide a way for end users to narrow/filter VMs to those most appropriate for usage with the selected DEC.

---

General

---

---

---

---

---

1.Sort pull-down lists alphabetically - default to top of a list.

1010
4371

2/28/2007

02/28/2007

4

Please report specific lists that are still not in order in the tracker below. Provide the tool name and version, specific list and where that list is displayed. Some fields have the most popular choices at the top. Does this supercede those prior requests?

A spot check was conducted (1 hour) and 4 issues were found and reported in the tracker below. https://gforge.nci.nih.gov/tracker/index.php?func=detail&aid=4371&group_id=295&atid=1243

A spot check found:
UML Model Browser 3.2.0.2: none

Sentinel 3.2.1.2 - none

CDE Browser 3.2.0.3 - Basic and Advanced Search "Search in the following fields" (again, most popular are at top by design, let us know if you want this changed)

Curation Tool 3.2.0.4 - "Search In" values are in reverse alpha order for DE, DEC, VD, Prop, OC, Concept, Permissible Value. This lov order brings "Public ID" to the top. The lists are short, does this really need to be changed for each
screen? No other lists were found to be out of order.

Admin Tool 3.2.0.1
- Derived DE "Type" is not alpha on Edit DE "Derived Data Element" "add new" screen
- AC Classifications Schemes "List" in "Search for Classification Schemes" for a specific component in "modify" . From the tree when clicking "Classifications", "search for Classifications at the top portion when adding/searching for CS for individual DE, DEC, VD (maybe all other ACs) CSI is alpha, CS "list" is not
- Names "List" feature when adding Contacts for all ACs
- Relationship "Type" list when adding Related "related DE" "related DEC"

09/19/2008 - TC - Lists of Persons and Organizations in create Contact Registration are not in alphabetical order.

---

2. Restrict drop-down list for representation terms. Look at linking terms to be used to datatype chosen. Provide maintenance tool to support updates to the representation term list.

---

---

3.2.0.4: Restricted rep term returned when a term is searched

Already in scope for 4.0

---

3.Add ability to related administered components to other administered components for example, a concept has been retired and a new preferred concept has been assigned - there should be a way to direct a user to use the new concept (or components created with the new concept rather than continuing to reuse items related to a retired concept).

---

---

---

11/09/2010 This ability is available in the Admin Tool but no curator conventions have been established for what/which relationships types should be used or how the tools would  make use of this additional metadata.  This can be considered in SI V1 future enhancements, or SI V2.

This is a more complex requirement and will need to be post 4.0. Should be implemented with the EVS concept maintenance feature. We will need business rules if this is to be automated. The search features in Curation tool already exclude retired concepts, but mostly based on name search. If explicit "related" concepts need to be added and used in curation activities, this will be a higher level of effort requiring cross tool coordination, cannot be fit into 4.0 release but will be addressed.

---

4. Support versioning business rules in the tools.

---

---

---

Need more explanation to understand specific issue. Generally, the ability to customize business rules external to the software is needed, but will require significant redesign whereby the rules can be authored as a customization feature and then implemented in the tools instead of the hard coded rules that we have now. This is not suitable for 4.0 as it requires a major redesign but will be factored into the MDR futures project.

----

5. Document business rules that are applied in the tools.

---

---

---

In process

---

6.Improve tools requirements management so that contents of various releases can be more easily identified and tracked.

---

---

---

See CORE Infrastructure Scope Planning Index .

Review requirements management process so customers understand where to find scope documents, identify trackers that are targeted for a release and view Release Notes. Maybe move to a general "Requirements" tracker for all caDSR tools that gets in turn reviewed and moved to individual tools as they are picked up for a particular release.

---

7. Browser/Curation: Provide the ability to create a list of CDEs and download into an xmi format that can be imported into a UML authoring tool.

---

---

---

11/09/2010 Developing services that will allow other applications to create content in caDSR. SI V2 will allow CDEs to be pulled into an authoring tool.  OSU's modified cgMDR EA plugin allows users to insert caDSR CDEs into UML Classes at design time.


Will not be caDSR 4.0 feature, but we are looking into this in conjunction with Dynamic Extensions. If this can be worked out, ti could be released as an increment, post 4.0.
09192008: SA Presentation: down load of CDEs for use in FormBuilder was referenced.

---

8.Any where CS information is provided, remove CS definition from the Classification sections. Possible link to a CS detail if more information is needed.

---

---

---

Please provide an example to clarify.

---

9.Automatically add the system-generated definition as an Alternate Definition.

3747

12/7/2006

---

https://gforge.nci.nih.gov/tracker/?group_id=33&atid=205&func=detail&aid=3747 Please provide examples to ensure we understand the requirement.

---

10. Add Registration Status for Value Domains. (Gforge 573)

573

1/12/2007

---

11/09/2010 This has not been implemented nor has it become a high priority requirement.  Currently on hold.

Which project is this GFroge reference number in?

---

CDE Browser

---

---

---

---

---

1. When you change from Basic Search to Advanced Search, refresh display should automatically to remove the previous information.

---

---

---

Currently, changing from Basic to Advanced does not clear search field, but changing from Advance to Basic does. Is this request to make these both clear the search text in the "search" field?

---

2. When searching DECs, Classifications, etc. and the Keyword search window opens, the default should not have the box checked for Restrict Search to Current Context.

---

---

---

This is working as designed, by request, to restrict the search to the Context so that it works within a 'drill-down'. What is the rationale for changing it back to not search within the current setting

---

3. Provide the ability to move Classifications/CSI's around in the tree easier (drag and drop).

---

---

---

Will investigate - there are technology limitations for web applications.

---

4. After doing a search on "All of the Words" then selecting "New Search" it takes a user back to the "Exact phrase". Preferred behavior is to be able to still search in the "All of the Words Search" not have the Browser reset to the Default.

---

---

---

This will take some additional work/discussion - probably not 4.0, but could be 4.1.

---

5. In Advanced Search the "search in the following fields" criteria automatically defaults to search in "Long Name". The default should be "All".

---

---

4.0.0.0

Will evaluate this request in terms of optimal performance on default search.

11900 - in Browser

6. Make sort of Context tree and its components alphabetical and not case dependent.

4668

3/22/2007

4.0.0.0

DW: I believe the Context tree is already alpha and not case dependent in both UML Model and CDE Browsers. Is this the list of items under Classification, Protocol and Protocol Forms Nodes? Since the order of the CSIs within a CS is *supposed* to be set by the end user using the "order" attribute, would this remove that capability?

11821 - in Browser

7. Update tree structure to make it easier for users to find UML models.

---

---

---

This could include a metadata driven design in which the Classifications are listed by TYPE instead of "Classifications". E.g. "Project", "Service", "Classification Scheme"? If this approach is taken, a review of CS Types is needed to ensure that the types are named appropriately.

---

Curation Tool++

---

---

---

---

---

1. Add a search for Value Meanings. Provide ability to find of all uses of a VM - get associated CDs, DEs, and VDs

---

---

4.0.0.0

DW: The "where used" for a VM feature is provided in 3.2.0.4, would this be to make this feature available from main menu?

---

2. When searching for a Conceptual Domain set default to "All" contexts.

---

---

---

Create GForge tracker for 4.0

---

3. When searching for existing Permissible Values set default to all Conceptual Domains.

---

---

---

The search for VMs to create new PVs in a VD is restricted to the CD associated with the DEC by design per the ISO 11179 standard. The primary purpose of CDs is to group VMs that are appropriate for the DECs associated with the CD. As the body of enumerated VDs grows, this existing feature will provide a way for end users to narrow/filter VMs to those most appropriate for usage with the selected DEC.

---

4. [Important] When you select a different option in the "Search In:" field, do not clear the screen. The use case is typing in a Public ID in the Enter Search Term: field and then selecting the Search In: field, the Public ID previously entered is cleared. The multiple screen refreshes are time-consuming when doing extended curation.

---

---

---

Already in scope. [Larry please provide GForge Tracker number).

---

5. Add ability to add Contact Person and Organization to all Administered Items - a priority is to add this information to CS and make it visible on a CS detail.

12259

2/6/2008

4.0.0.0 (partial)

Please explain? All ACs can have contact added, where does it need to be visible?
09/19/2008 TC- Registration metadata can be added to a CDE but it is not visible in the CDE Browser detail. Only place to see it is via the Curation Tool. Person information can be maintained in the Admin Tool but there is no place to maintain Organizations.

12259 - in Curation

6. Enhance batch metadata maintenance function. Use case example: Currently workflow status and registration status mismatches can occur when a CDE is being set to Released. The current batch edit proves does not recognize that related DECs or VDs have not yet been set to Released. User should be notified that related administered components have not been released and give the option to set the workflow/registration status for these components.

---

---

---

Is this the "Block Edit" feature? [Create a GForge Tracker]

---

7. Need to define what metadata gets copied from parent when creating from existing - for example, start date copying is not consistent for items.

11327

1/7/2008

4.0.0.0

a. The values to be copied for each type of component have been implemented per content team guidance. If sounds like there are a few bugs. The "Effective Date" and "End Date" for DE, DEC, VDs should not be copied - a tracker has been created for this: https://gforge.nci.nih.gov/tracker/index.php?func=detail&aid=11427&group_id=33&atid=202
b. Please document other business rules/fields that should be changed by AC type (DE, DEC, VD) and we will open trackers for them.

11427 - in Curation

8. The return of content after a search should not eliminate the search term used.

---

---

---

In the CDE Browser, content team has asked that search fields be cleared when toggling between basic and advanced, this seems inconsistent with this request. Could we ask for a common design to be implemented in all places? The search term entered is redisplayed at the top of the search results in the Curation tool, making preserving the search term in the text entry box unnecessary, but it is inconsistent, e.g. in the 'concept' search screens when creating OC, Prop, Rep term, the search field is cleared, but in a spot check, the AC component search screens the search term text is cleared.

---

9. When an alternate name or definition is added to a component, you must click on this option twice; the first time just refreshes the screen. This problem occurred in a recent iteration.

3747

12/7/2006

---

Need to Open Tracker

---

Default the short name type to System Generated rather than asking a curator to select one of the selections.

---

---

---

---

This was added 02/04/2009 to heep tract of this request.

Admin Tool

---

---

---

---

---

1. Ability to hit "enter" after any search, like in the other tools. It would be nice to have the Admin Tool function more like the Curation Tool - specifically using the Enter key to begin searches, instead of clicking on the search button.

---

---

---

Known issue

---

2. Add administered component to Classification Scheme Item by Public ID. Show Public IDs on all Detail screens.

5310

3/28/2007

---

Known issue

---

3. Improve drawing speed for the left-hand tree - some items are very slow or do not draw the tree.

4235

2/9/2007

---

Known issue

---

4. Add ability to add Contact Person and Organization to all Administered Items.

---

---

---

09/19/2008: TC - Persons list must be maintained in LOV Maintenance. A way to maintain Organizations is not provided. A way to maintain Role is not provided.

---

UML Browser

---

---

---

---

---

1. A. When searching by Project Name, display only latest version in the drop down list by default.

---

---

---

---

---

B. Set default to current UML models; all option of all or by Workflow Status of the CS.

4200
4230

02/03/2007

02/09/2007

---

---

---

2. Cleanup Back function so that a user can actually return to a previous screen and retain the information.

---

---

---

---

---

3. Update UML Browser content on a regular basis. Provide Update ability to be run as needed in addition to batch process.

1027
4650

04/07/2006

03/21/2007

---

---

---

4. Coordinate the CS type display criteria with the CDE Browser CS type display criteria.

---

---

---

---

---

Form Builder

---

---

---

---

---

1. After selecting a form to view, have the first window with only the module details, not including all the questions with permissible values. For example, it is difficult to see the questions in one of four modules - now have to look at all modules and all questions.

---

---

---

---

---

Freestyle

---

---

---

---

---

1. Hot link the CDE# to get details in the displayed list.

---

---

---

---

---

2.Set up results to display in a tabular format

---

---

---

---

---

SIW

---

---

---

---

---

1. Check for equivalent concept usage within a class when assigning CDEs for reuse. Use case example: When there are multiple choices for a concept such as 'Patient' [the Patient concept has been created in a number of contexts - each entry has a unique public id], a user can chose a concept that may have the same terms and because there is a different public id this causes problems with the model registration process (UML Loader). Preferred term (caBIG context ?) should be at the top of the list.

---

---

---

Discuss.

---

2. Ability to create relationship to a previously used CDE. Use case, concept code was changed so new DEC and new CDE was created. Need to be able to relate to previously used CDE.

---

---

---

TC: Use case comes from caTissue.

---

3. Bug: Semantic connector overwrites annotations when it is run on a file after roundtrip unless EVS verified has been checked, even if human verified has been checked. Scheduled for bug fix.

---

---

---

---

---


  • No labels