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
Added support for full text search of database fields and PDF/XML galleys #2908
Conversation
mauromsl
commented
Jun 7, 2022
•
edited
edited
- There is a feature flag to enable disable this feature (ENABLE_FULL_TEXT_SEARCH)
- When the full text search is disabled, the old search interface and backend are used
- Includes management commands for creating database index and populating an index of the PDF/XML files into the database.
- Includes a new search interface that allows users to control what fields are included in the search.
- The backend interface includes support for both MySQL and Postgres
- Postgres support is enhanced in that it can weight search results and also persists only a GIN index of the full text (in MySQL we store the entirety of the text + we buid a FULLTEXT index)
- closes Add support for Full Text Search #2876
- closes Sort by date ascending and date descending in article search #2204
- closes Add ability to search by ORCID #2728
- closes Add abstract to current Articles search #2795
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally, this is great. Good work! I've added some, mostly ignorable, comments inline!
🎖️ 🎖️ 🎖️ 🎖️ 🎖️
|
||
|
||
@receiver(models.signals.pre_save, sender=File) | ||
def update_file_index(sender, instance, **kwargs): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we document that when calling .update() files will not be indexed?