Skip to content
This repository was archived by the owner on Jan 30, 2026. It is now read-only.
This repository was archived by the owner on Jan 30, 2026. It is now read-only.

Assigning a discipline to a package resource is confusing #40

@emetsger

Description

@emetsger

To assign a discipline to a package resource, bring up the properties box for the resource and scroll down to the Optional Properties; Discipline will be the first optional property:

screen shot 2017-04-10 at 5 24 36 pm

At first glance, Discipline appears to accommodate multiple values. The first value defaults to "Life Science" and the second value is empty. This is not the case. The second, empty value, represents a narrower discipline selection, i.e. a sub-discipline (e.g. Biotechnology, Animal Sciences, etc). The user doesn't know that until they select the empty box. If a user thought "Life Science" by itself was sufficient, they would never be inclined to click on the empty value in order to narrow the discipline.

screen shot 2017-04-11 at 9 48 06 am

What makes this worse is that the user must select a sub-discipline in order for the super-discipline to be persisted. That is, if the user thought "Life Science" was sufficient, and clicked "Apply" to persist their selection, the discipline is not, in fact, persisted!! They must select the broader discipline ("Life Science") and select a sub-discipline (e.g. "Biotechnology"), and then click "Apply". Only then will the Discipline optional property be saved on the package resource.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions