Project

General

Profile

Actions

Story #14393

closed

Provide support for using controlled vocabulary/terminology service when setting properties on collections

Added by Tom Morris almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
-
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Story points:
3.0

Description

Provide the equivalent support as was done for the existing workbench in #12479.

Some other details:
  • behavior is triggered by presence or absence of vocabulary file ("vocabulary.json" in existing implementation, but could be controlled by a configuration parameter
  • design center was 10-15 groups of terms (ie "vocabularies") with numbers of items for each ranging from a couple of dozen to a few thousand
  • there's an example file at arvados/apps/workbench/public/vocabulary-example.json

Related issues

Related to Arvados - Story #12479: [Workbench] Extend tag/property editing to support a structured vocabularyResolvedLucas Di Pentima10/24/2017

Actions
Blocked by Arvados Workbench 2 - Feature #14554: [Config] Config files deploymentClosed

Actions
Blocks Arvados Workbench 2 - Feature #14587: [Vocabulary] Disable default use of vocabulary.json.In Progress

Actions
Actions #1

Updated by Tom Morris almost 4 years ago

  • Related to Story #12479: [Workbench] Extend tag/property editing to support a structured vocabulary added
Actions #2

Updated by Moritz Gilsdorf almost 4 years ago

Using the terminologies when setting the properties is not enough. It should then also be used when using properties in the search.

Actions #3

Updated by Chrystian Klingenberg almost 4 years ago

  • Target version set to sprint 13 (lucky number)
Actions #4

Updated by Michał Kłobukowski almost 4 years ago

Behavior is triggered by presence or absence of vocabulary file ("vocabulary.json" in existing implementation, but could be controlled by a configuration parameter
1. So should we expect vocabulary.json to placed by default for example under `c97qk.arvadosapi.com/vocabulary.json`?
2. Does configuration mean a config.json file the same that is currently used for `API_HOST`?
3. Would that be the way to check if vocabulary should be enabled:
3.1 Get vocabulary from default path end enable the feature,
3.2 If default not available check config file for vocabulary URL - if present fetch it end enable the feature,

there's an example file at arvados/apps/workbench/public/vocabulary-example.json
1. Does the truthy strict property mean, that we won't be able to type other values that the ones from vocabulary.

Actions #5

Updated by Michał Kłobukowski almost 4 years ago

  • Status changed from New to Feedback
  • Assigned To set to Michał Kłobukowski
Actions #6

Updated by Michał Kłobukowski over 3 years ago

  • Status changed from Feedback to In Progress
Actions #7

Updated by Daniel Kos over 3 years ago

  • Target version changed from sprint 13 (lucky number) to sprint 14
Actions #8

Updated by Michał Kłobukowski over 3 years ago

Actions #9

Updated by Michał Kłobukowski over 3 years ago

  • Related to deleted (Feature #14554: [Config] Config files deployment)
Actions #10

Updated by Michał Kłobukowski over 3 years ago

Actions #11

Updated by Michał Kłobukowski over 3 years ago

  • Status changed from In Progress to Resolved
Actions #12

Updated by Michał Kłobukowski over 3 years ago

  • Status changed from Resolved to In Progress
Actions #13

Updated by Michał Kłobukowski over 3 years ago

  • Status changed from In Progress to Resolved
  • Story points set to 3.0
Actions #14

Updated by Michał Kłobukowski over 3 years ago

  • Blocks Feature #14587: [Vocabulary] Disable default use of vocabulary.json. added
Actions #15

Updated by Michał Kłobukowski over 3 years ago

From https://dev.arvados.org/issues/14554:

However the vocabulary.json is more dynamic and it needs to be possible to change it between Installations.
In our case the vocabulary.json is generated every couple of hours from an API and replaces the previous one
In a way the vocabulary.json is like an external API itself. One possible way could be to configure the URL of the vocabulary.json in the config.json which would allow us to use a rest API directly instead of a static json file

Actions #16

Updated by Michał Kłobukowski over 3 years ago

Currently vocabulary file is loaded once when the application starts. To load a new vocabulary user has to refresh the page. Should that behaviour stay for now, or should it be more dynamic, so that vocabulary endpoint would be called when typing into properties form. A drawback of more dynamic behaviour is that the vocabulary file can be quite large and loading it very often would cause some lags.

Actions #17

Updated by Michal Komorowski over 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF