Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not obvious requires keywordindex + metadata col create a new filter #98

Open
djay opened this issue Feb 18, 2020 · 2 comments
Open

not obvious requires keywordindex + metadata col create a new filter #98

djay opened this issue Feb 18, 2020 · 2 comments

Comments

@djay
Copy link
Member

djay commented Feb 18, 2020

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.

@djay djay changed the title currently requires keywordindex + metadata col to work not obvious requires keywordindex + metadata col create a new filter Feb 18, 2020
@woolyseal
Copy link
Member

Hi. Ran into a similar problem and wanted to add:

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.

@agitator
Copy link
Member

@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 ;-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants