can i check with you guys if there is a workaround for this: is there a existing way/future plans to currently assign ownership of newly created glossary terms to the person who created it? this is because i have a "owners can edit ownership/edit description" policy in place for entities. I realised that UI creation does not automatically create a owner (whereas ingesting yml does, because i need to specify owner) it sounds like something that the actions framework can/should do, but if im not wrong, the actions framework does not retain information about the originating source at the moment. seems like the present way is to only grant a select group of people the rights to edit glossary terms

Also would like to report that for glossaryNodes to be editable (edit descriptions, links, ownerships), the edit ACL also needs to be loosened. This is pretty bad for my implementation. ie, to change the description of a glossaryNode, I need a "all resources, edit description Privileges" policy granted to a person. This effectively makes the person a metadata admin for all existing assets. Is there a chance that glossaryNodes can be made a targetable entity in policies?

and appreciate the heads up on the second point - we can definitely make glossary nodes targetable entities in policies as that only makes sense. also adding that to my list of glossary follow-ups and will try to get that in at the same time as point one