Closed bradfordcondon closed 6 years ago
The permissions on these nodes control what databases are available to the user on the blast form. For example, I use Simple Access to control my blastdb's by role. The first screenshot shows what I see with a specific role whereas the second shows what an anonymous user sees.
All of that to say that we can't just change the permissions on these nodes because they affect more then at first it seems ;-)
Is there another way to indicate to ElasticSearch that these items shouldn't be indexed?
I know that ES indexes nodes based on permissions of an anynmous user. @almasaeed2010 do we have any other options beyond explicitly filtering out these node types?
PS. My plan is for these to remain nodes in Tripal3 since they are not specifically biological content -just configuration for the blast module.
We’ll add an exception in ES to ignore them in that case.
Thanks!
Hi all, dont know if this issue will stay relevant for Tripal 3 version.
We have a problem where the blast databases are being indexed by elasticsearch. Tripal ES indexes all nodes that an anonymous user would have access to. These nodes arent really fit for end user consumption (http://160.36.205.61:8095/node/1976613).
Is it possible to change the view permissions for these nodes? It seems like permissions are only defined for CRUD