-
Notifications
You must be signed in to change notification settings - Fork 4
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
Uses OpenSearch for search and some reporting #649
base: develop
Are you sure you want to change the base?
Conversation
…use of 'doc' being required in some cases (upsert) but not others.
…ather than methods) in the open_search builder class.
…d the date/time an opensearch record was updated.
…nk. Default is 128.
…ings to config, tests for opensearch class
…er objects of owner, ownergroup, profile, resource
… useful even though it can be looked up the ark/doi
…ements and entire output doc.
…there is an existing python library called that and it's confusing.
…to open_search_doc
- Added to schema - Added to document generation - Added to test
…tch updates made by LinkChecker for our transition
…es' instead of 'value'
Thanks for finding the issue with the target URL search, Jing. I've fixed that. Let me know what other changes you'd like to see. You mentioned reverting the report to still use the SearchIdentifiers table? I think what I had worked when I tested, but if you want to put that back to SearchIdentifiers and separate more from that table later, that is OK with me. |
@sfisher Hi Scott, Jing |
I reverted proc-download.py to use searchIdentifier. The changes I made are in the commit history if you want to de-entangle it again later. |
Merge Develop to main for updating package-lock.json
Add instruction on how to use poetry to update packages and dependencies.
I've done a pass of cleaning up code and adding documentation to the docs repository relating to OpenSearch.
I believe this is all working on development, but it hasn't been indexed or tested on stage yet. I think all the functionality works though I have only done cursory examination of search results and exercised each advanced search field to be sure it seems to work. More thorough testing would be great before we realease.
We also need to run indexing on each environment before release (stage, production).
Please see the
docs/ezid_search_opensearch.md
file in the documentation repo for a lot of background about the search.Updated in this PR:
proc-download
)proc-search-indexer
PS. I believe this PR also incorporates everything in #604 . It hasn't been merged yet, so I may just close it.