Fluid Indexing turns static repository files into discoverable institutional knowledge.
Fluid Indexing is WGRID's direction for keeping repository search useful as institutions add PDF-based records, metadata, authors, departments, content types, and publication details over time.
Why indexing matters
A repository becomes valuable when users can find the right material quickly. If users only see file names or a short title list, useful knowledge remains buried. Indexing connects titles, authors, abstracts, subject hints, dates, content type, institution ownership, and document availability into a more meaningful discovery experience.
What can become searchable
WGRID can organize search around repository fields such as title, author information, publication details, content type, institutional owner, status, attached document presence, and other metadata. Where technical extraction is available, PDF text can also become part of the discovery layer.
How the indexing flow works
Record is created
The institution uploads or edits a repository record with structured fields and attached documents.
Metadata is prepared
Important fields such as title, author, content type, institution, publication year, and document state become the foundation for discovery.
Search index is refreshed
Scheduled tasks and cache/index refreshes keep the public discovery layer aligned with the latest repository records.
Reader discovers content
Visitors can reach content through search, internal links, metadata snippets, direct URLs, and external discovery routes where enabled.
For students
Faster access to papers, e-books, theses, serials, and institutional documents that may otherwise be hard to locate.
For librarians
Better control over how records are organized, exposed, corrected, and improved as repository content grows.
For institutions
A stronger public knowledge layer that helps institutional output become visible beyond a single department or physical library.
Designed to stay practical
WGRID's indexing approach should remain realistic for institutions with limited technical teams. The priority is to make repository discovery better without making content management fragile, heavy, or difficult to maintain during Drupal upgrades.
