- Version: Snow Owl v3.5
- Start date: 23 June 2014
- End date: 1 August 2014
- Code name: Lehütö. The name has two meanings: A Léhűtő is a person who cools down liquid. The word originates from a job in breweries where some people worked as assistants who stirred the hot beer so that it gets cool faster. Nowadays it’s used to describe a person who shuns work and does nothing.
New query form
The new wizard makes it easy to specify parameters for your task queries. The query parameters are in accordance with the task list. The query form consists of three tabs: Basic parameters, Assignees, and Miscellaneous parameters.
On the tab with Basic parameters, you need to specify a name for your query and select the repository.
- Query name: Enter a name for your query, which will be used as the folder name in the task list.
- Repository: Verify that the pre-set repository is the one used for task management (e.g. Bugzilla).
The following parameters can be specified
- Task name: Query for the name of a task (or part of the name).
- Task summary/comments: Query for terms from the task summary or the comments section.
- Last changed in number of days: This is useful to restrict the query to more recent tasks (e.g. last 30 days).
In the Assignees section you query for users, it aligns with the Assignees section in the task editor. You need to enter the user name which is used in the task management system, in most cases this is the email-address of the user. If you want to create a query for all the tasks that you are assigned to simply enter your user name in the query fields for Author one, Author two, Reviewer one, Reviewer two, and Adjudicator (see screenshot). If you want to follow up with the tasks that you created, enter your user name at Reported by.
- Author one: In case of a single author scenario, you need specify the name of the author here. In case of a dual authoring, this is the team member assigned as the first author.
- Author two: In case of a dual authoring, this is the team member assigned as the second author.
- Reviewer one: In case of a single reviewer scenario, you need specify the name of the reviewer here. In case of a two reviewers, this is the team member assigned as the first reviewer.
- Reviewer two: In case of a dual authoring, this is the team member assigned as the second reviewer.
- Adjudicator: This is the team member that is specified as the adjudicator in a scenario with two reviewers.
- Reported by: User who created a task.
- Task artifact: Restricts the artifact type (e.g. ATC authoring, SNOMED CT reference set authoring)
- Priority: For example, display only tasks that have a high priority.
- Task scenario type: Restricts the search to a certain scenario (e.g. Dual authors with dual reviewers – dual blind authoring)
- Task status: You can query tasks by their status (e.g. resolved, verified)
Select the query parameters by clicking on the items in the list. Hold the CTRL (Windows) or CMD (OSX) key to select several items. To unmark an item hold the CTRL (or CMD) key and click on the item.
Enhancement on review tab
The columns in the task editor now display the user name of each reviewer. In a scenario with two reviewers, they can be distinguished more easily.
Restricted promotion in dual-blind authoring scenario
In scenarios with dual authors and dual reviewers the task status can only be set to Verified if all cases were reviewed (accepted or denied). If a case is unresolved, because the reviewer or the adjudicator did not enter a decision, the workflow can not be pushed forward. If all cases were rejected, the promotion is also disabled.
New video tutorials
Exporting reference sets
Two tutorial videos about exporting reference sets are now available. All videos are transcribed and can be watched with captions.
The following topics are covered
- Exporting reference sets to dsv shows how to export reference sets to delimiter separated values format. After the export the exported file is reviewed in Microsoft Excel.
- Exporting reference sets to SNOMED CT release formats demonstrates how to produce an RF1 and RF2 file. It also explains how historical information is incorporated when running a full RF2 export.