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
It's not obvious that you can't use fieldindex, or that you have to have both metadata + index to work.
It would be good to either reduce the requirements or perhaps use validation or descriptions in the portlets instead to highlight whats required and why.
The text was updated successfully, but these errors were encountered:
djay
changed the title
currently requires keywordindex + metadata col to work
not obvious requires keywordindex + metadata col create a new filter
Feb 18, 2020
It seems you have to name the index and the metadata column exactly like the field you are indexing. I tried a index and metadata named "is_something" and was indexing the field "something". In the catalog everything seemed fine, but the filter wouldn't work.
@wkbkhard both are needed, the metadata column is the easiest way to produce a meaningfull filterentry.
only a limited amount of indexes make even sense the way we are using it for filtering based on "words"
filtering by path (there's a pr) and date for example have totally different requirements to make it work.
Documentation enhancements are always welcomed PRs ;-)
It's not obvious that you can't use fieldindex, or that you have to have both metadata + index to work.
It would be good to either reduce the requirements or perhaps use validation or descriptions in the portlets instead to highlight whats required and why.
The text was updated successfully, but these errors were encountered: