USE 256 - Add fulltext field to TimdexRecord model #265
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Why these changes are being introduced: Decisions have been made to move incrementally into supporting full-text search in TIMDEX. The first known use case is for the mitlibwebsite source, where we'll store the full-text of websites for searching. While it's possible a single record may have multiple full-texts associated with it, our initial requirements are only for a single, root level, simple field. How this addresses that need: Adds new root level, simple, field called 'fulltext' to TimdexRecord model class. This field is not yet used by any sources. Side effects of this change: * Eventually, sources will begin to populate this. Relevant ticket(s): * https://mitlibraries.atlassian.net/browse/USE-256
ghukill
force-pushed
the
USE-256-new-fulltext-field
branch
from
07b25e2 to
dbb6f5c
Compare
ehanson8
approved these changes
Dec 8, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose and background context
This PR adds a new field
fulltextto theTimdexRecordmodel class.This field is not yet used by any sources, but the first planned will be
mitlibwebsitewhich will store the full-text of library websites.This work falls under epic USE-260 which has a few tightly coupled tickets, with this being the first work performed. Next steps include:
fulltextfieldfulltextfield in TIM's Opensearch mapping, which we could then test withmitlibwebsiterecords withfulltextvaluesHow can a reviewer manually see the effects of these changes?
Nothing really to see! A field has been added, but no sources using it yet.
Please see this section in a confluence write-up on this with spike examples: https://mitlibraries.atlassian.net/wiki/spaces/D/pages/4989517825/2025-12-03+-+Full-text+search+spike+for+mitlibwebsite+source#Changes-in-Transmogrifier.
Includes new or updated dependencies?
NO
Changes expectations for external applications?
NO
What are the relevant tickets?