Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecating terms #89

Open
olufine opened this issue Feb 22, 2024 · 6 comments
Open

Deprecating terms #89

olufine opened this issue Feb 22, 2024 · 6 comments

Comments

@olufine
Copy link

olufine commented Feb 22, 2024

Hi,
Does TemaTres offer a way to deprecate terms without deleting them from the database? I am thinking about marking terms as deleted rather than actually deleting them. Some such method is necessary to keep our thesaurus backward compatible, I believe.

@tematres
Copy link
Owner

Hi @olufine :), Tematres have terminological workflow. The terms can be acepted (green), rejected (red) or candidate (blue). From accepted status you can turn to rejected status. From rejected status you can turn tu candiate status, from candidate status you can turn to accepted or rejected status.
Only accepted terms are public and can have terminological relations.

You can change the term status in Term menu: Options-> Change status.
image

Please let me know if this solve the problem :)

best regardsss!

@olufine
Copy link
Author

olufine commented Feb 28, 2024

It doesn't solve the problem, no, since rejected terms are not included in the SKOS export. Moreover, it looks to me as only free/unrelated terms are open to status change - am I right?
I have solved the problem on my side by comparing 2 versions of the export, so I think it's OK now.
One other thing: If a term is deleted in Tematres, is there a danger that Tematres will reuse its ID for future new terms?

@tematres
Copy link
Owner

Hi @olufine I go in order:

  1. SKOS export and deleted or rejected terms: There are tag in the SKOS-Core schema to store and expose deleted labels ? If we can expres the status using skos schema may be we can add this feature
  2. Change term status: the rejected terms or terms in candidate status do not can have terminological relations. You are right
  3. Terms ID: Any term ID are unique and never will wll be reuse in future terms

@MDemir81
Copy link

MDemir81 commented Apr 10, 2024

Hi, I would also be interested in 'deprecating terms'. We would be happy if deprecated terms would still be findable to non-editors also but just with some visual hint, that the term is deprecated.

Right now we are trying to solve it via historical and definitions note. But the user would not see any deprecated flag in the overview of the broader term. Also right now there would be no deprecated flag, if the user opens the deprecated term.
He can only see the info, if he look in the definition or historical note of the deprecated term.
Example: https://digilab.ptb.de/dkd/refType/vocab/index.php?tema=91&/serialno

So I would be happy, If I could deprecate terms but these terms still would be visible and would have a flag 'deprectated' in the boarder term (overview of subordinate terms) and a flag, if the deprecated term is opened. For Example as follows, but maybe better vizualization is possible:
BroaderTermOfDeprecatedTerm
DeprecatedTerm

@tematres
Copy link
Owner

Hi @MDemir81 you can enable the public access to rejected and candidate terms if you config as TRUE the CFG_VIEW_STATUS value in config form (Menu -> Admin-> Configuration). The rejected terms are RED, candidate terms are BLUE.
The rejected and candidate terms can have notes but not terminological relations (in your excample the term have BT relations).

We can add the legend "deprecated" or "rejected" as supindex, like the image, is more informative.

thanks!

@MDemir81
Copy link

Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants