@UserEntityTypes are very similar to @UserCategories, but just not in the Tag Browser. UETs are psuedo-columns, just like UCs. Look in table preferences key field_metadata, and you will see that UCs are next to Custom Columns that are next to Standard Columns. In theory (but not in practice since the book-level values would be missing), I could add UETs to the Tag Browser where all of the Standard/Custom Column ETs already are. That is why I like the "@".
Quote:
As far as I can see there is no way to see in the Book List, that something (e.g. Publisher:Random House) has been been selected as an Entity.
Any thoughts of making that available, I'm thinking of something which I could use in a Column icon rule to show the stylised purple 'e' on cells that are entities.
|
I am not a Template person, do not ever use them, and do not know if they are limited to the GUI Cache, or can read metadata.db directly via APSW. A Template function in general program mode that could read a SQLite database directly would work. EM is outside of the GUI Cache entirely, since book ID is not anywhere within EM. That is its point; it is designed to be "above" book-level. So, the general program mode function would be reading from the physical database instead of the in-memory Cache for every book and every potential ET column at startup. Slow for large Libraries with many ET columns. If Templates can do it, I will write the general program mode function and make it available to copy-and-paste. However, if they cannot access APSW, then I know of no way to do what you ask. I am interested to know if they can.
DaltonST