Handling of deprecated concepts

[acka47]

This came up in the context of the latest upate of Hochschulfächersystematik, see also the respective paragraph of this week's meeting notes of OER-Metadatengruppe.

I suggest to follow the lead of SKOSMOS which came to the same results that started to emerge in the discussion of the Tuesday meeting: https://github.com/NatLibFi/Skosmos/wiki/Data-Model#deprecated-concepts

We could move on in two steps:

Step 1

• Clearly mark concepts as deprecated when its description contains owl:deprecated true
• Include links to successor concept(s) indicated with dct:isReplacedBy
• Exclude deprecated concepts from the hierarchy view
• Exclude deprecated context from the search index
• Add info in README

Step 2

Include a configuration option that triggers:

• inclusion of – grayed-out – deprecated concepts in the hierarchy view
• inclusion of deprecated contexts in search index with – per default off – switch in the search configuration

[sroertgen]

@acka47 how do we want to proceed here?

I implemented the first tasks, resulting in something like

The information is also available in the machine readable part.
Should I continue working on the other steps or do we first want to get feedback on this from people who had problems with deprecated concepts?

[acka47]

Thanks, this looks good. One minor thing: To be consistent with "In Scheme" etc., we should use "Is replaced by".

Should I continue working on the other steps or do we first want to get feedback on this from people who had problems with deprecated concepts?

Yes, let's first await the discussion next Tuesday. But we should already deploy this at least to test to show how it looks with the Hochschulfächersystematik.

[sroertgen]

Ok. Will fix headline and merge into dev for testing.

[acka47]

Exclude deprecated concepts from the hierarchy view
Exclude deprecated context from the search index

As discussed today in the meeting of OER-Metadatengruppe, we won't do this for now.