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

Advanced Search: Technical Metadata -> Elasticsearch Exception #1114

Open
hofmannc opened this Issue Jan 30, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@hofmannc
Copy link

hofmannc commented Jan 30, 2019

Browser: ff
Version: 4.4-SNAPSHOT - build date2019-01-24 18:18:12
User: admin

Actions: "Advanced Search" -> "select technical metadata name" -> enter existing value

Observation: exception
grafik
tried it with old metadata and added new (meta:last-author -valid value: Catherina Hofmann / publisher - valid value: Max-Planck-Gesellschaft / Application-Version - valid value: 14.000)

Expected Result: results are available as soon as new metadata added in admin's section

@haarli haarli self-assigned this Jan 30, 2019

@haarli haarli added this to the imeji 4.4 milestone Jan 30, 2019

@hofmannc hofmannc changed the title Advances Search: Technical Metadata -> Elasticsearch Exception Advanced Search: Technical Metadata -> Elasticsearch Exception Feb 6, 2019

@hofmannc

This comment has been minimized.

Copy link
Author

hofmannc commented Feb 6, 2019

Testserver: qa imeji
Browser: ff
Version: 4.4-SNAPSHOT - build date2019-02-05 09:36:40
User: admin
Result: nok -> although given examples are findable now.

wrong result for:
Admin -> "Configuration" -> "Search/Technical Metadata" -> enter "Application Record Version" -> "save all"

Advanced search -> select technical metadata "Application Record version" -> enter "2" -> "Search"

Given result: http://qa-imeji.mpdl.mpg.de/imeji/item/Z_SfU0vZSfzBxpby?q=%28technical%5B+Application+Record+Version%5D%3D2%29&fq=&filter=&pos=0#pageTitle
Expected result: at least
http://qa-imeji.mpdl.mpg.de/imeji/collection/DzEOe5rGZzLwvQKz/item/ryi0bZcwbRc4Vrf?q=&fq=&filter=&pos=1#pageTitle

--> or should this be a new ticket?

@hofmannc

This comment has been minimized.

Copy link
Author

hofmannc commented Feb 7, 2019

There were Technical metadata statements with spaces in use earlier, see screenshot. Currently there are no matching items available, so I cannot retest.

grafik

But there could be indeed an issue with the space, since the newly created statement "Resolution units" [inch] did not show the expected result either.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment