You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Dear @tematres I have been using TemaTres with my students. We have approached the problem with candidate terms. When the term is added and the "candidate term" status is selected, we cannot edit the term and change its status for a valid one.
There are no candidate terms on the alphabetical list of all terms. Candidate terms are presented only through show/candidate terms but the link is dead.
We are using TemaTres TemaTres 3.1. Any solutions will be helpful because we have many candidate terms in our projects. Best regards, Marcin
The text was updated successfully, but these errors were encountered:
Hi @mroszkowski, (please be patient with my english :)) I will try to go in order:
To change the status term: Menu term -> Options -> Change status. The status follow this workflow:
from candidate -> reject or accepted term
from accepted -> to reject
from reject -> to candidate
You can check this features in our open sandbox:
Any other behavior is a error or bug :/
Terms visibility: when the user are login, the rejected and candidate terms are enable in alphabetic browse, when the user is not logged, the candidate and rejected terms are not visible.
We are in tematres 3.3. We have free and open campus to academic and research projects, you can have 10 or 20 instances of tematres for your students :)
Dear @tematres I have been using TemaTres with my students. We have approached the problem with candidate terms. When the term is added and the "candidate term" status is selected, we cannot edit the term and change its status for a valid one.
There are no candidate terms on the alphabetical list of all terms. Candidate terms are presented only through show/candidate terms but the link is dead.
We are using TemaTres TemaTres 3.1. Any solutions will be helpful because we have many candidate terms in our projects. Best regards, Marcin
The text was updated successfully, but these errors were encountered: