Questions institutions ask first

Frequently asked questions

Quick answers for libraries, colleges, research departments, and institutional administrators evaluating WGRID as a repository platform.

What is WGRID built for?

WGRID is built to help educational institutions publish and manage repository records such as articles, e-books, theses, serials, periodicals, technical reports, and attached documents with indexing-friendly metadata.

Is WGRID only a website, or is it a repository system?

WGRID has public website pages, but its core purpose is repository management. It supports institution-owned records, PDFs, metadata, dashboards, privacy controls, and discovery-oriented presentation.

Can an institution upload PDF files and make them public?

Yes. WGRID supports repository records with attached documents and a PDF.js based viewer. Public exposure can be controlled through WGRID Furnace privacy settings and Drupal permissions.

Can some content remain private?

Yes. WGRID can expose selected content types publicly while keeping other content protected. This allows institutions to publish open material while keeping sensitive or incomplete records away from anonymous users.

How does WGRID help Google Scholar visibility?

WGRID adds Google Scholar-oriented metadata patterns through Furnace and Metatag integration. It also encourages public full-text access, stable record pages, clear titles, author information, and document links where the content type is configured for public discovery.

Does WGRID support Dublin Core metadata?

WGRID has been designed to reuse existing content fields for Dublin Core-aligned metadata. The aim is to avoid duplicate data entry while still exposing library-friendly fields such as title, creator, date, type, identifier, publisher, and description.

What is OAI-PMH and why is it useful?

OAI-PMH is a harvesting protocol used by repository and library systems to collect metadata from participating repositories. For WGRID, it is a future-ready direction that can help institutional content become more interoperable with academic discovery systems.

What is Fluid Indexing?

Fluid Indexing is WGRID's approach to keeping repository records searchable as institutions upload or update content. It focuses on metadata, document presence, content types, and future PDF text indexing so records do not disappear inside static files.

Who manages repository content?

Institutional users can manage their own repository content through dashboards and Drupal-controlled permissions. Administrators retain platform-level control over configuration, privacy rules, metadata patterns, and site-wide behavior.

Can WGRID support multiple institutions?

Yes. WGRID is shaped around institution-level ownership, allowing different institutions to manage and present their own repository records while sharing the same platform foundation.

How are storage memberships handled?

WGRID uses storage-based membership levels so institutions can choose a plan based on the expected volume of PDFs and repository records. This keeps pricing aligned with actual repository data requirements.

What type of content can be published?

Typical repository content can include research articles, e-books, theses, journals, serials, periodicals, conference material, departmental reports, technical reports, and institutional publications.

Can WGRID help with accreditation or institutional reporting?

WGRID can support reporting indirectly by making institutional output easier to organize, count, review, and present. Dashboards and metadata quality checks can help administrators understand repository health.

Is WGRID mobile friendly?

Yes. Public pages and WGRID custom features are developed with mobile layouts in mind so students, faculty, and visitors can browse repository pages from common devices.

Does WGRID replace a library management system?

No. WGRID is focused on digital repository publishing, metadata, document access, and institutional visibility. It can complement library systems rather than replace circulation, cataloguing, or acquisition workflows.