Hiding/deactivating concepts

[Carl Burnett]

Is there a way to make concepts in a Taxonomy hidden or deactivated?

 

Is there a way to do that to concepts in an EDG project (such as a Data Graph) that includes that Taxonomy?

 

Carl Burnett

Senior Ontology Engineer  |  Healthwise

cbur...@healthwise.org  |  www.healthwise.org

208.489.8485

 

[Holger Knublauch]

On 10/04/2021 4:45 am, Carl Burnett wrote:

Is there a way to make concepts in a Taxonomy hidden or deactivated?

Yes, using dash:hidden:

 

Is there a way to do that to concepts in an EDG project (such as a Data Graph) that includes that Taxonomy?

 

This mechanism works for the Taxonomy Hierarchy panel, so as long as people use that to navigate (in Data Graph or where ever) it should be fine. However, even for hidden concepts there are still other ways to navigate to them, e.g. if there are direct links to them on a form or in results of SPARQL queries.

Holger

Carl Burnett

Senior Ontology Engineer  |  Healthwise

cbur...@healthwise.org  |  www.healthwise.org

208.489.8485

 

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/CY4PR19MB15903254AE17D2BF39E5C049B7739%40CY4PR19MB1590.namprd19.prod.outlook.com.

[cbur...@healthwise.org]

Holger,

Thanks for the reply. I should've been more explicit about my use case. I know about dash:hidden, but all it seems to do for concepts is to hide them from the hierarchy. What I'm looking for is a way to:

1. prevent certain concepts from appearing as suggestions when using Quick Search in the taxonomy. (My users tell me that having retired concepts show up when they use the Quick Search is confusing and cluttered, which I have to agree with.)

2. prevent them from appearing as suggestions when mapping other resources to our concepts in an EDG Data Graph. (Again, users suggest that only active concepts should be available as possible tags. We already have a constraint in place to warn users upon saving a resource that's mapped to an inactive concept, but we would prefer to make it impossible to add such a mapping in the first place.)

Our taxonomist has taken to adding "DEPRECATED" to the beginning of deactivated concept labels so that these concepts don't get used, but there has to be a better way, right?

[Irene Polikoff]

An obvious solution is to make them a member of a different class e.g., ex:RetiredConcept. And remove the type they had previously. This class should be “stand alone” i.e., not a subclass of skos:Concept.

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/853996e9-05fc-4f58-b238-84905db0d792n%40googlegroups.com.

[Holger Knublauch]

Yes this would be the best solution. It would be too hard for all these other places (such as auto-complete widgets) to filter by some criteria. OTOH class membership is trivially supported and efficient to use.

Holger

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/171F2A11-08DD-4E2B-9AC9-74060BF28F21%40topquadrant.com.