<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Supporting Vertical Web Search and Customized Search Applications with the Modular and Open Framework MOSAIC</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sebastian Gürtl</string-name>
          <email>sebastian.guertl@tugraz.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Alexander Nussbaumer</string-name>
          <email>alexander.nussbaumer@tugraz.at</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christian Gütl</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Graz University of Technology</institution>
          ,
          <addr-line>Rechbauerstraße 12, 8010 Graz</addr-line>
          ,
          <country country="AT">Austria</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <fpage>14</fpage>
      <lpage>25</lpage>
      <abstract>
        <p>Web search plays a crucial role in retrieving information, yet many existing search engines limit transparency and customization. Open-source frameworks provide alternatives but often require extensive configuration and lack direct support for openly available web indexes. This paper introduces MOSAIC, a modular opensource search framework designed for vertical web exploration. MOSAIC enables domain-specific search by integrating index partitions downloaded from the Open Web Index (OWI). Its modular architecture supports vertical search applications by allowing customization of query execution, filtering mechanisms, metadata management, and result representation. A development study and expert focus groups evaluated MOSAIC's applicability and modularity, identifying both strengths and areas for improvement. The results showed that the framework's modularity, OWI partition integration, and metadata management are key strengths. However, the study also revealed limitations in OWI partition updates, unified ranking, and documentation, which require further refinement. Furthermore, a science search application demonstrated its potential for enriching structured research repositories with web content. Future work will address improved OWI partition management, re-ranking mechanisms, and AI-assisted enhancements such as conversational search to refine usability and adaptability in vertical search applications.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Web Search Engine</kwd>
        <kwd>Modular Search Framework</kwd>
        <kwd>Search Engine Customization</kwd>
        <kwd>Open Web Index</kwd>
        <kwd>Vertical Web Search</kwd>
        <kwd>Information Retrieval</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        In today’s digital landscape, web search is essential for retrieving information across various domains,
from academia to industry. However, the majority of widely used search engines are proprietary, which
restricts transparency and customization. This lack of openness hinders the development of customized
search solutions that meet specific requirements. In addition, artificial intelligence (AI)-assisted search
and information retrieval systems have gained attention recently, as generative AI (GenAI) expands
into web search engines and domain-specific retrieval tasks. While these advancements enable new
interaction modes, concerns persist regarding the lack of transparency, the reliability of generated
responses, and the dificulty of verifying sources [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. This underscores the necessity for open-source
frameworks that ofer both flexibility and transparency.
      </p>
      <p>
        Open-source search frameworks ofer an alternative that focuses on these characteristics. Unlike
proprietary search engines, which limit access to their index data, indexing, and ranking mechanisms,
open-source solutions allow developers to customize and adapt search functionality to meet specific
needs. Yet, an open-source search framework by itself is not suficient—it also depends on comprehensive
and reliable index data to function efectively [
        <xref ref-type="bibr" rid="ref2 ref3">2, 3</xref>
        ]. Without such index data, developers are often
forced to rely on proprietary datasets or create their own indexes, which can be both costly and
resourceintensive. A key resource in this space is the Open Web Index (OWI) [
        <xref ref-type="bibr" rid="ref4 ref5">4, 5</xref>
        ]. It ofers openly accessible
index data to support a wide range of search applications. By incorporating open index data such
as the OWI, these frameworks enable developers to build tailored search solutions while minimizing
reliance on proprietary search infrastructure. However, existing open-source search frameworks often
require technical expertise for setup and configuration, and lack native integration with index partitions
downloaded from the OWI [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>To address these challenges, we introduce the open-source framework Modular Search Application
based on Index Fractions (MOSAIC), designed to facilitate vertical web exploration. It provides a
readyto-use solution that can be deployed and used immediately via its API. The framework provides a
configurable approach to natively incorporate OWI partitions, query processing, and result
representation. In contrast to general-purpose search engines, MOSAIC focuses on domain-specific retrieval
and allows search functionalities to be customized and extended with custom modules. Therefore, this
paper examines its modular architecture and applicability in vertical web search exploration.</p>
      <p>We outline the design and implementation of MOSAIC, explain its modular and extensible structure,
and highlight advantages for vertical search applications. Additionally, we present findings from
a development study and focus groups that illustrate MOSAIC’s applicability from a developer’s
perspective, integration potential, and areas for improvement. Eventually, we examine future directions
and open challenges of MOSAIC, focusing on integrating GenAI to improve query processing, result
re-ranking, and interactive user interaction.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Related Work</title>
      <p>
        The rise of search engines such as Google led to significant advancements in large-scale web indexing
and retrieval, which enabled eficient access to vast amounts of online information [
        <xref ref-type="bibr" rid="ref6 ref7">6, 7</xref>
        ]. These
search engines introduced centralized infrastructures capable of crawling, processing, and organizing
unstructured web content. Before centralized search engines became dominant, distributed systems
such as Harvest explored alternative architectures for indexing and retrieval and therefore ofered an
early approach to decentralized, modular and scalable search [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ].
      </p>
      <p>Building on these concepts, modern open-source search frameworks, such as Apache Solr1, Terrier2,
OpenSearch3, and Elasticsearch4 have been widely adopted for a variety of indexing and search tasks.
In general, these frameworks are flexible and extensible, which makes them suitable for a wide range of
applications. However, they often require considerable configuration to meet domain-specific search
needs [9, 10, 11]. Infret, another open-source information retrieval framework, features eficient retrieval
and is particularly beneficial in educational and learning environments, but has limitations in scalability
and adaptability to diverse domain-specific requirements [12, 13].</p>
      <p>
        Additionally, open-source search frameworks commonly depend on proprietary or self-built indexes
of web pages, which introduces challenges in acquiring and maintaining comprehensive web data.
Although Common Crawl5 provides a large-scale open web corpus, maintaining an index of its full
collection is often less practical than crawling and indexing a smaller, domain-specific subset [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        The OpenWebSearch.eu6 project addresses this issue by providing the OWI, a structured and openly
accessible web index, consisting of several partitions. Its construction follows a structured pipeline. First,
OWLer, a Stormcrawler-based distributed web crawler, collects raw web data [14]. Next, the collected
data is preprocessed and analyzed by the web content analysis pipeline Resilipipe, which is based on
Resiliparse7 [15]. This results in structured metadata of crawled web pages such as extracted content
and language information [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. The subsequent indexing process uses Apache Spark8 and utilizes the
information extracted from the preprocessing step. The resulting OWI partition consists of structured
1https://solr.apache.org
2https://github.com/terrier-org/terrier-core
3https://opensearch.org/
4https://elastic.co/elasticsearch
5https://commoncrawl.org/
6https://openwebsearch.eu/
7https://resiliparse.chatnoir.eu/
8https://spark.apache.org/
metadata and document representations stored in Apache Parquet9 files, along with the inverted index
in the Common Index File Format (CIFF). Regarding metadata, the columnar storage format of Parquet
is well-suited for large-scale data processing [16]. The use of CIFF allows for the eficient exchange
of index data, subsequently facilitating more accurate and fair comparisons between diferent search
systems [17]. Existing search frameworks lack direct support for OWI partitions and therefore require
additional efort to preprocess and integrate this data into search infrastructures. This limitation may
complicate the development of open and adaptable search applications that leverage OWI partitions,
particularly for those aiming to leverage web indexes without relying on proprietary solutions.
      </p>
      <p>Nussbaumer et al. addressed this gap and demonstrated through a prototype application10 that
OWI partitions created by the OpenWebSearch.eu index generation pipeline can be used for searching
and retrieving information [18]. However, this prototype application stored all OWI partition data
in memory, thus problems occurred as soon as the OWI partitions became too large. Therefore, the
primary motivation is to demonstrate the efective utilization of OWI partitions in search engines as
they provide a technological foundation for custom applications while maintaining a modular and
configurable framework.</p>
      <p>In addition, recent advancements in large language models (LLMs) and GenAI have introduced new
methods in search, such as retrieval-augmented generation (RAG). This approach combines traditional
document retrieval with LLM-based response generation. Therefore, LLMs base their outputs on
structured and verifiable data sources [ 19]. By combining an open and modular search architecture
with AI-assisted retrieval and ranking, such a framework could help connect open search with GenAI
while maintaining control over index data and search transparency.</p>
    </sec>
    <sec id="sec-3">
      <title>3. The MOSAIC Framework</title>
      <p>The web search engine framework MOSAIC provides a modular and configurable component-based
architecture that overcomes the limitations of in-memory index data storage approaches. The framework
follows the core idea of enabling domain-specific search by integrating modular components. It utilizes
Apache Lucene11 for indexing and query processing, and DuckDB12 for metadata management. This
enables both storage and retrieval of web pages contained in an OWI partition. The framework allows
selective inclusion of one or multiple OWI partitions and provides direct access to the index data for
customizable metadata filtering mechanisms. MOSAIC is an open-source software and available via an
OpenWebSearch.eu project’s GitLab repository13.</p>
      <sec id="sec-3-1">
        <title>3.1. Architecture and Functionalities</title>
        <p>9https://parquet.apache.org/
10https://opencode.it4i.eu/openwebsearcheu-public/prototype-search-application
11https://lucene.apache.org/
12https://duckdb.org/
13https://opencode.it4i.eu/openwebsearcheu-public/mosaic
14https://opencode.it4i.eu/openwebsearcheu-public/mosaic/container_registry
15https://quarkus.io/
16https://github.com/informagi/lucene-cif</p>
        <p>After importing OWI partitions, users can submit search queries through the web interface, REST
API, or external services. Queries may be rewritten or analyzed using custom analyzers. Additionally,
users can integrate LLMs to refine search terms. The Lucene IndexSearcher processes the queries using
the BM25 ranking function [20]. Additionally, MOSAIC supports re-ranking after retrieval, with a
demonstration implementation that adjusts ranking based on the word count of a web page’s extracted
main content.</p>
        <p>MOSAIC refines search results by applying metadata filtering and enrichment. Users specify filtering
parameters to refine results based on metadata attributes, while developers implement advanced filtering
methods. The system enriches results by adding relevant metadata to provide comprehensive and
contextually informative output. It also generates text snippets by extracting key sections from metadata.
When necessary, an on-demand mechanism retrieves full extracted document text from Parquet files to
improve snippet accuracy.</p>
        <p>Additionally, MOSAIC provides a REST API for handling search queries and returning results in
either JavaScript Object Notation (JSON) or Extensible Markup Language (XML) format. The /search
endpoint processes queries across one or multiple OWI partitions and returns results in JSON format,
while /searchxml follows the OpenSearch protocol17 and formats responses as XML documents. If no
specific OWI partition is defined, MOSAIC searches all available partitions and structures the response
accordingly. Additionally, the /index-info endpoint provides metadata about the available partitions,
including the number of documents and languages that occur in the partition respectively.</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Metadata Modules</title>
        <p>To utilize metadata in the search process, MOSAIC provides a structured metadata management system
that enables customized filtering, enrichment, and retrieval. The framework follows a modular plugin
architecture that allows flexible integration of metadata modules and optional system components.
Developers can customize their MOSAIC-based vertical search engine by enabling or disabling specific
modules without modifying the core system. It relies on Apache Maven18 for dependency management,
build processes, and module lifecycle handling. Metadata modules interact with the core system through
defined interfaces and are configured via a dedicated settings file.</p>
        <p>Metadata modules in MOSAIC improve search results by adding contextual information such as
titles, URLs, language, extracted topics, and geolocation data. Advanced filtering operates through
metadata fields in Parquet files, processed via DuckDB. For example, users can further limit search
results using geographic coordinates. Each module defines metadata columns and filter parameters,
which enable search refinements and enrichment. The framework provides an API for query validation,
SQL filter clause generation, and result serialization in JSON and XML. Developers extend MOSAIC by
defining custom metadata attributes in Parquet files, making them accessible for filtering, retrieval, and
enrichment without requiring changes to the core framework.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Evaluation</title>
      <p>Assessing the applicability, modularity and integration potential of MOSAIC involved a development
study, focus groups, and a domain-specific use case. The development study provided insights into the
developer experience and examined how efectively developers can configure and extend the framework.
Focus groups with domain experts helped to identify strengths and areas for improvement, particularly
regarding modularity and metadata integration. Eventually, a science search application illustrated
MOSAIC’s use in a specific domain and demonstrated its applicability in vertical search.</p>
      <sec id="sec-4-1">
        <title>4.1. Development Study</title>
        <p>The development study took place during a one-day hackathon, organized by the Cognitive and Digital
Science (CoDiS) Lab at Graz University of Technology as part of the OpenWebSearch.eu initiative.
The hackathon provided a structured, hands-on environment where participants explored MOSAIC.
Participants engaged with MOSAIC and delved into its modular architecture, metadata management,
and integration with OWI partitions. The study aimed to determine how efectively users could install,
configure, and extend MOSAIC, while also identifying strengths and areas for improvement.</p>
        <sec id="sec-4-1-1">
          <title>4.1.1. Participants</title>
          <p>The study involved 13 participants, including 11 computer science students (84.62%) from Graz
University of Technology (6 bachelor’s students (46.15%) and 5 master’s students (38.46%)) and 2 external
participants (15.38%) with master’s degrees in computer science. The gender distribution included
2 women (15.38%) and 11 men (84.62%). Participants were divided into four teams, with one team
participating online. At the end of the hackathon, 11 participants (84.62%) completed a questionnaire
designed to capture qualitative and quantitative feedback on MOSAIC’s installation, applicability, and
potential improvements.</p>
        </sec>
        <sec id="sec-4-1-2">
          <title>4.1.2. Materials and Methods</title>
          <p>The hackathon began with a presentation on web search fundamentals, the OpenWebSearch.eu project,
and MOSAIC’s architecture. Participants received access to the technical documentation, a developer
guide, and example use cases to support development. Collaboration and communication was facilitated
through cloud storage, a dedicated Discord server, and a Jitsi meeting room for online participants.</p>
          <p>Throughout the hackathon, participants worked locally on their own notebooks. To streamline the
development process, pre-prepared OWI partitions were provided. Teams explored predefined tasks,
such as creating new OWI partitions, modifying the front-end, integrating MOSAIC as a service, and
performing web data analysis.</p>
          <p>At the end of the hackathon, participants completed a questionnaire designed to collect structured
feedback on their experience with MOSAIC. The survey assessed applicability, modularity, and the
integration process.</p>
        </sec>
        <sec id="sec-4-1-3">
          <title>4.1.3. Procedure</title>
          <p>Following the introductory session, participants formed teams and brainstormed potential applications
of MOSAIC. Each team presented its initial concept in a plenary session and received feedback before
proceeding to the development phase, which lasted approximately five hours. The organizers provided
technical support and facilitated discussions to refine project implementations. The development study
as part of the hackathon concluded with final project presentations, a voting session, and participant
questionnaires, which assessed the applicability, modularity, and integration potential of the framework.
Rating all aspects of MOSAIC asked in the questionnaire was not mandatory.
4.1.4. Results
The responses of the questionnaire ofered information on the applicability of MOSAIC and the
developer experience. As indicated in Figure 2, participants responded positively to the technical concept
and modularity of MOSAIC, all participants agreeing that it supports the development of vertical
search engines. However, installation and integration aspects received more mixed ratings, with 4
participants (36.36%) rating the ease of installation process as "Neutral" or lower. This suggests areas
for improvement in applicability and installing MOSAIC.</p>
          <p>These results align with qualitative feedback, highlighting the need for enhanced documentation
and onboarding resources. The framework’s API for search queries and result retrieval was noted as a
strength, as it ofers transparent and reliable means of accessing the index data. In addition, participants
expressed interest in continuing the development with MOSAIC, particularly in the areas of AI-assisted
information retrieval, search result ranking improvements, and expanded metadata support.</p>
        </sec>
      </sec>
      <sec id="sec-4-2">
        <title>4.2. Focus Groups</title>
        <sec id="sec-4-2-1">
          <title>4.2.1. Participants</title>
          <p>While the development study provided insights into MOSAIC’s applicability from a developer’s
perspective, additional feedback from domain experts was gathered through focus group discussions. These
sessions aimed to evaluate the technical design, modularity, and applicability of MOSAIC in real-world
search scenarios and complement the findings from the development study.</p>
          <p>The focus group discussions involved 10 experts, divided into 5 groups, from the OpenWebSearch.eu
consortium. The participants represented institutions such as Radboud University, the University of
Passau, the German Aerospace Center (DLR), CERN, and the Webis research group. Among the experts,
7 (70%) held a master’s degree, and 3 (30%) had a doctoral degree. Overall, the groups included four
PhD students (40%), four researchers (40%), and three professors (30%), and therefore provided a
diverse range of expertise. The gender distribution consisted of 3 women (30%) and 7 men (70%).</p>
        </sec>
        <sec id="sec-4-2-2">
          <title>4.2.2. Materials and Methods</title>
          <p>The focus groups were conducted online using BigBlueButton, where participants selected a 30-minute
session to join. Discussions were structured into three categories: i) the technical approach, ii) the
modular architecture, and iii) the applicability of MOSAIC. The moderators asked predefined questions
to guide the discussion and cover aspects such as system applicability, the efectiveness of the modular
design, and potential applications. At the end of each session, participants completed an online
questionnaire to provide quantitative feedback on the framework. To analyze qualitative feedback from
the focus groups, thematic coding was applied to identify recurring patterns and categorize responses
into strengths, weaknesses, and areas for improvement.</p>
        </sec>
        <sec id="sec-4-2-3">
          <title>4.2.3. Procedure 4.2.4. Results</title>
          <p>Before the sessions, participants received an email invitation outlining the study’s objectives. During
the discussions, moderators ensured a structured dialogue and collected qualitative insights while
taking notes. The sessions were audio-recorded with participant consent and deleted after analysis.
Following the discussion, participants rated various aspects of MOSAIC, such as the system’s technical
design, modularity, and its suitability for custom search applications.</p>
          <p>Experts provided insights into MOSAIC’s strengths, weaknesses, and areas for improvement, as
summarized in Table 1. The focus groups identified MOSAIC as an efective domain-specific search engine
with satisfactory performance and speed. Its modular architecture allows developers to customize
components as needed. Participants valued its seamless integration with OWI partitions and its
compatibility with the OpenWebSearch.eu project. The framework also supports prototyping and low-code
development, which enables a user-friendly installation process and potential for community-driven
creation and sharing of modules.</p>
          <p>Despite the strengths, certain weaknesses became evident during the discussions. Participants
noted that MOSAIC does not yet support dynamic updates, additions, or removals of OWI partitions,
which limits adaptability in evolving search applications. Although the framework provides a strong
foundation, it remains more of a demonstrator than a fully production-ready system. Concerns were
also raised about the increasing complexity as more features are introduced. The ranking process
currently operates on a per-partition basis rather than providing a unified ranking across partitions.
Additionally, reliance on CIFF was seen as a constraint, as the format is not widely recognized in search
engine development.</p>
          <p>To address these issues, participants proposed several improvements. Enhancing support for multiple
metadata versions and enabling CIFF file combinations could increase adaptability. Simplifying module
• Efective as a basic search engine, performing as expected with satisfactory</p>
          <p>performance and speed.
• Modular architecture allows flexible plugin functionality and enables
devel</p>
          <p>opers to add, remove, or customize components.
• Easy integration of OWI partitions and compatibility with the
OpenWeb</p>
          <p>Search.eu project.
• Well-suited for prototyping and low-code development, which simplifies the</p>
          <p>creation of custom search engines.
• Includes a user-friendly installation process and has the potential for a</p>
          <p>community-driven exchange mechanism of modules.
• Lacks support for OWI partition updates, additions, and removals.
• More suited as a demonstrator than a production system, with a risk of</p>
          <p>increasing complexity.
• Ranks results separately for each partition rather than using a unified ranking.
• Relies on CIFF, which is not widely adopted as an index exchange standard.
• The web user interface lacks advanced search result presentation and requires</p>
          <p>improvements to better match user expectations.
• Better suited for specific use cases based on the OWI schema (CIFF and</p>
          <p>Parquet) rather than broader applications.
• Need to combine CIFF files and handle diferent metadata versions.
• Improve accessibility of modules by enabling easy addition via APIs.
• Expand advanced search functionalities with additional filters and improved</p>
          <p>ranking across multiple OWI partitions.
• Introduce automated module and OWI partition management.
• Provide blueprints and detailed documentation to assist in developing and</p>
          <p>integrating custom modules.
integration through APIs and expanding search functionalities, including additional filters and a
unified ranking mechanism, would improve usability. Furthermore, automating module and OWI
partition management could reduce maintenance eforts. Eventually, providing more comprehensive
documentation and structured development blueprints would make the framework more accessible to
new users.</p>
        </sec>
      </sec>
      <sec id="sec-4-3">
        <title>4.3. Science Search Application</title>
        <p>Beyond evaluating MOSAIC’s modularity and applicability, a science search application examined its
role in scientific information retrieval. While traditional academic search engines provide structured
datasets, they often lack real-time context on emerging research topics. To address this, MOSAIC was
integrated into a hybrid search system that combined structured scientific metadata with web-based
content from OWI partitions [22].</p>
        <p>The application focused on earth observation and environmental research by combining structured
datasets from DLR with relevant web content from a custom OWI partition of over 500 natural
disasterrelated web pages. A federated search interface enabled simultaneous querying of both sources, ranking
results by semantic relevance and geographic attributes. Metadata modules in MOSAIC facilitated
cross-source alignment and enabled filtering and refinement of search results. Figure 3 illustrates the
application’s dashboard with keyword-based search, metadata filtering, and a geographical map view
to explore environmental events concerning scientific publications.</p>
        <p>MOSAIC integrated structured scientific metadata with web content and therefore enabled hybrid
retrieval. The system connected datasets from digital libraries with web documents on environmental
events. Metadata alignment across diferent sources remained a challenge, particularly in standardizing
metadata between MOSAIC and scientific repositories. Future improvements could explore metadata
harmonization and automate extraction methods [22].</p>
      </sec>
      <sec id="sec-4-4">
        <title>4.4. Limitations</title>
        <p>While the evaluation provided valuable insights into MOSAIC’s modularity and applicability, certain
limitations should be considered. The development study included 13 participants, primarily computer
science students from a single institution, which limits the generalizability of findings. Although their
technical background allowed for a focused assessment of MOSAIC’s framework, the study did not
capture perspectives from non-technical users or professionals from diverse fields who might engage
with MOSAIC diferently.</p>
        <p>Similarly, the focus groups consisted of ten experts, all afiliated with the OpenWebSearch.eu project.
While this ensured informed discussions, it also meant that participants were already familiar with
MOSAIC and its objectives. As a result, feedback may have been influenced by prior knowledge and
project alignment, rather than reflecting perspectives from independent stakeholders or search engine
operators who have not interacted with the framework before.</p>
        <p>Another constraint was the availability of OWI partitions during the evaluation. Participants worked
with pre-prepared partitions, which restricted their ability to assess dynamic partition updates, the
integration of new metadata attributes, or real-time indexing scenarios. Although the study confirmed
that MOSAIC can integrate OWI partitions modularly, future evaluations should examine how well the
framework handles continuously evolving datasets and broader indexing configurations.</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Future Directions and Open Challenges</title>
      <p>Building on the findings from the development study, focus groups, and science search application, this
section outlines directions for future development, explores potential applications leveraging GenAI,
and discusses remaining challenges in the framework.</p>
      <sec id="sec-5-1">
        <title>5.1. Technical Improvements</title>
        <p>MOSAIC integrates OWI partitions, although several areas could benefit further refinement to enhance
its flexibility and performance. One key aspect is improving OWI partition management, particularly in
supporting dynamic updates, additions, and removals. While the current system enables OWI partition
imports natively, it lacks mechanisms for updating index data incrementally. Introducing automated
synchronization methods or incremental indexing could address this limitation without requiring full
re-indexing [23]. A strategy to implement improved index data management could be the integration
of the OWI partition management tool owilix19.</p>
        <p>Another important focus is on refining the modular architecture to improve ease of integration
and extensibility. The framework’s modularity allows developers to add or remove components,
but managing dependencies between modules can result in challenges. MOSAIC could benefit from
simplified module configuration, improved API accessibility, and blueprints for metadata modules.
These improvements would lower the barrier for adoption and facilitate the creation of own modules.</p>
        <p>Furthermore, clear and comprehensive documentation is essential for ensuring MOSAIC’s accessibility
to a wider audience. Therefore, enhancing the developer guide with detailed examples, step-by-step
tutorials, live and pre-recorded trainings, and best practices for module integration would support
developers in setting up and extending the framework.</p>
      </sec>
      <sec id="sec-5-2">
        <title>5.2. Future Applications and AI Opportunities</title>
        <p>Apart from technical improvements, MOSAIC’s current architecture ofers a basis for AI-assisted
search applications, with potential enhancements in querying, ranking and re-ranking, retrieval, and
result representation. One promising direction is RAG, where LLMs retrieve relevant documents from
MOSAIC before generating responses. This approach could improve the search and retrieval process by
helping generative models ground their responses in transparent and structured index data, such as
OWI partitions [19]. Eventually, this could lead to multi-turn and interactive conversations with users
to refine and clarify their search intents [24].</p>
        <p>Beyond retrieval augmentation, AI could further improve query understanding, ranking, and result
summarization. Integrating LLM-based query rewriting could refine user queries and therefore increase
retrieval accuracy, as well as satisfying the user’s needs [25]. Similarly, AI-assisted re-ranking could
leverage semantic similarity models to improve search result relevance [26]. MOSAIC could also serve
as a foundation for automated summarization tools to extract key insights from web pages.</p>
        <p>Another possible future direction for MOSAIC is mobile-based local search, where OWI web content
is accessed entirely ofline on a mobile device. This approach allows retrieval without an internet
connection and benefits environments with limited connectivity or strict privacy requirements.</p>
        <p>Following a low-code approach, a customization tool such as MOSAIC2go20 could help simplify
the creation of domain-specific vertical search applications by providing an interactive interface for
configuring MOSAIC-based search engines. This approach would reduce the need for manual setup and
therefore allow non-technical users to develop and manage their own search solutions. Additionally,
integrating AI-driven features, such as query expansion, RAG, or summarization, into such a
customization platform would further extend its capabilities and could bridge the gap between technical and
non-technical MOSAIC users.</p>
      </sec>
    </sec>
    <sec id="sec-6">
      <title>6. Conclusion</title>
      <p>This paper presented MOSAIC, an open-source web search framework designed for modular, vertical
search applications that integrate OWI partitions to improve search accessibility. MOSAIC’s
componentbased architecture enables customizable search solutions without relying on proprietary infrastructures.
Moreover, the framework’s plugin-based modularity allows developers to configure and extend its
functionality, which makes it adaptable to various domain-specific search scenarios.</p>
      <p>The evaluation through a development study, expert focus groups, and a science search application
provided insights into MOSAIC’s applicability, modularity, and integration potential. Participants
19https://opencode.it4i.eu/openwebsearcheu-public/owi-cli
20https://mosaic.ows.eu/mosaic2go/
identified the modular design, metadata management, and ease of OWI partition usage as key strengths.
However, challenges remain in OWI partition updates, unified ranking, and metadata alignment, which
requires further refinement. The science search application demonstrated MOSAIC’s potential to enrich
structured scientific search with web-based contextual information. The evaluation faced limitations in
sample size, participant familiarity with MOSAIC, and the restricted number of OWI partitions. Broader
testing with diverse user groups and datasets would help address these constraints.</p>
      <p>In contrast to other modular search systems, MOSAIC integrates directly with OWI partitions, which
simplifies working with large-scale open web indexes. While general-purpose search frameworks often
require extensive configuration or rely on proprietary index data, MOSAIC ofers a transparent and
customizable approach to search infrastructure.</p>
      <p>Future work will focus on improvements in OWI partition management, modularity enhancements,
and ranking refinements. Additionally, MOSAIC’s open and extensible design may enable potential
applications in AI-assisted retrieval, including query rewriting, RAG features, re-ranking and
conversational search. While further improvements are necessary, its modular architecture provides a flexible
framework that could support advancements in open search and GenAI for vertical search applications.</p>
    </sec>
    <sec id="sec-7">
      <title>Acknowledgements</title>
      <p>This work has received funding from the European Union’s Horizon Europe research and innovation
program under grant agreement No 101070014 (OpenWebSearch.EU, https://doi.org/10.3030/101070014).</p>
    </sec>
    <sec id="sec-8">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used Grammarly in order to: Grammar and spelling
check. After using these tool, the authors reviewed and edited the content as needed and take(s) full
responsibility for the publication’s content.
[9] M. A. Akca, T. Aydoğan, M. İlkuçar, An analysis on the comparison of the performance and
configuration features of big data tools solr and elasticsearch, International Journal of Intelligent
Systems and Applications in Engineering 4 (2016) 8–12. doi:10.3390/app112411590.
[10] I. Ounis, G. Amati, V. Plachouras, B. He, C. Macdonald, D. Johnson, Terrier information retrieval
platform, in: Advances in Information Retrieval: 27th European Conference on IR Research,
ECIR 2005, Santiago de Compostela, Spain, March 21-23, 2005. Proceedings 27, Springer, 2005, pp.
517–519. doi:10.1007/978-3-540-31865-1_37.
[11] S. Papadopoulos, P. Saiz, U. Schwickerath, E. Kleszcz, Architecting the opensearch service at cern,
in: EPJ Web of Conferences, volume 295, EDP Sciences, 2024, p. 07006. doi:10.1051/epjconf/
202429507006.
[12] A. Bobić, C. Cheong, J. Filippou, F. Cheong, C. Guetl, Infret: Enhancing a tool for explorative
learning of information retrieval concepts, in: The Impact of the 4th Industrial Revolution on
Engineering Education: Proceedings of the 22nd International Conference on Interactive Collaborative
Learning (ICL2019)–Volume 1 22, Springer, 2020, pp. 67–78. doi:10.1007/978-3-030-40274-7_
7.
[13] A. Bobić, C. Gütl, C. Cheong, Infret: preliminary findings of a tool for explorative learning of
information retrieval concepts, in: Cross Reality and Data Science in Engineering: Proceedings
of the 17th International Conference on Remote Engineering and Virtual Instrumentation 17,
Springer, 2021, pp. 849–865. doi:10.1007/978-3-030-52575-0_70.
[14] M. Dinzinger, S. Zerhoudi, M. Al-Maamari, M. Istaiti, J. Mitrović, M. Granitzer, Owler: Preliminary
results for building a collaborative open web crawler (2024). doi:10.5281/zenodo.10581840.
[15] S. Heineking, I. Zelch, G. Hendriksen, Resilipipe, 2024. URL: https://doi.org/10.5281/zenodo.</p>
      <p>13784624. doi:10.5281/zenodo.13784624.
[16] D. Vohra, D. Vohra, Apache parquet, Practical Hadoop Ecosystem: A Definitive Guide to
Hadoop</p>
      <p>Related Frameworks and Tools (2016) 325–335. doi:10.1007/978-1-4842-2199-0.
[17] J. Lin, J. Mackenzie, C. Kamphuis, C. Macdonald, A. Mallia, M. Siedlaczek, A. Trotman, A. de Vries,
Supporting interoperability between open-source search engines with the common index file
format, in: Proceedings of the 43rd International ACM SIGIR Conference on Research and
Development in Information Retrieval, 2020, pp. 2149–2152. doi:10.1145/3397271.3401404.
[18] A. Nussbaumer, R. Kaushik, G. Hendriksen, S. Gürtl, C. Gütl, Conceptual design and implementation
of a prototype search application using the open web search index, in: 5th International Open
Search Symposium, Sl: Open Search Foundation, 2023. doi:10.5281/zenodo.10636166.
[19] P. Lewis, E. Perez, A. Piktus, F. Petroni, V. Karpukhin, N. Goyal, H. Küttler, M. Lewis, W.-t. Yih,
T. Rocktäschel, et al., Retrieval-augmented generation for knowledge-intensive nlp tasks, Advances
in Neural Information Processing Systems 33 (2020) 9459–9474.
[20] S. Robertson, H. Zaragoza, et al., The probabilistic relevance framework: Bm25 and beyond,</p>
      <p>Foundations and Trends® in Information Retrieval 3 (2009) 333–389. doi:10.1561/1500000019.
[21] L. J. Cronbach, Coeficient alpha and the internal structure of tests, psychometrika 16 (1951)
297–334. doi:10.1007/BF02310555.
[22] A. Nussbaumer, S. Gürtl, J. Honeder, T. Hecking, C. Gütl, Enriching science search with the
open search framework mosaic, in: 6th International Open Search Symposium, 2024, pp. 49–52.
doi:10.5281/zenodo.13871624.
[23] W. Xia, H. Jiang, D. Feng, F. Douglis, P. Shilane, Y. Hua, M. Fu, Y. Zhang, Y. Zhou, A comprehensive
study of the past, present, and future of data deduplication, Proceedings of the IEEE 104 (2016)
1681–1710. doi:10.1109/JPROC.2016.2571298.
[24] J. Gao, C. Xiong, P. Bennett, N. Craswell, Neural approaches to conversational information retrieval,
volume 44, Springer Nature, 2023. doi:10.1007/978-3-031-23080-6.
[25] Y. Zhu, H. Yuan, S. Wang, J. Liu, W. Liu, C. Deng, H. Chen, Z. Liu, Z. Dou, J.-R. Wen, Large language
models for information retrieval: A survey, arXiv preprint arXiv:2308.07107 (2023).
[26] S. Xu, L. Pang, J. Xu, H. Shen, X. Cheng, List-aware reranking-truncation joint model for search
and retrieval-augmented generation, in: Proceedings of the ACM on Web Conference 2024, 2024,
pp. 1330–1340. doi:10.1145/3589334.3645336.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>W.</given-names>
            <surname>Hersh</surname>
          </string-name>
          ,
          <article-title>Search still matters: information retrieval in the era of generative ai</article-title>
          ,
          <source>Journal of the American Medical Informatics Association</source>
          <volume>31</volume>
          (
          <year>2024</year>
          )
          <fpage>2159</fpage>
          -
          <lpage>2161</lpage>
          . doi:
          <volume>10</volume>
          .1093/jamia/ocae014.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>C. D.</given-names>
            <surname>Manning</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Raghavan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Schütze</surname>
          </string-name>
          , Introduction to Information Retrieval, Cambridge University Press,
          <year>2008</year>
          . doi:
          <volume>10</volume>
          .1017/CBO9780511809071.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>W. B.</given-names>
            <surname>Croft</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Metzler</surname>
          </string-name>
          , T. Strohman,
          <article-title>Search engines: Information retrieval in practice</article-title>
          , volume
          <volume>520</volume>
          ,
          <string-name>
            <surname>Addison-Wesley</surname>
            <given-names>Reading</given-names>
          </string-name>
          ,
          <year>2010</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>M.</given-names>
            <surname>Granitzer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Voigt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Fathima</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Golasowski</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Guetl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Hecking</surname>
          </string-name>
          ,
          <string-name>
            <given-names>G.</given-names>
            <surname>Hendriksen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hiemstra</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Martinovič</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Mitrović</surname>
          </string-name>
          , et al.,
          <article-title>Impact and development of an open web index for open web search</article-title>
          ,
          <source>Journal of the Association for Information Science and Technology</source>
          <volume>75</volume>
          (
          <year>2024</year>
          )
          <fpage>512</fpage>
          -
          <lpage>520</lpage>
          . doi:
          <volume>10</volume>
          .1002/asi.24818.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>G.</given-names>
            <surname>Hendriksen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Dinzinger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. M.</given-names>
            <surname>Farzana</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N. A.</given-names>
            <surname>Fathima</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Fröbe</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Schmidt</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Zerhoudi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Granitzer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Hagen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Hiemstra</surname>
          </string-name>
          , et al.,
          <article-title>The open web index: Crawling and indexing the web for public use</article-title>
          ,
          <source>in: European Conference on Information Retrieval</source>
          , Springer,
          <year>2024</year>
          , pp.
          <fpage>130</fpage>
          -
          <lpage>143</lpage>
          . doi:
          <volume>10</volume>
          .1007/978-3-
          <fpage>031</fpage>
          -56069-9_
          <fpage>10</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>S.</given-names>
            <surname>Brin</surname>
          </string-name>
          ,
          <string-name>
            <surname>L. Page,</surname>
          </string-name>
          <article-title>The anatomy of a large-scale hypertextual web search engine, Computer networks</article-title>
          and
          <source>ISDN systems 30</source>
          (
          <year>1998</year>
          )
          <fpage>107</fpage>
          -
          <lpage>117</lpage>
          . doi:
          <volume>10</volume>
          .1016/S0169-
          <volume>7552</volume>
          (
          <issue>98</issue>
          )
          <fpage>00110</fpage>
          -
          <lpage>X</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>L.</given-names>
            <surname>Page</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Brin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Motwani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Winograd</surname>
          </string-name>
          , et al.,
          <article-title>The pagerank citation ranking: Bringing order to the web (</article-title>
          <year>1999</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>C. M.</given-names>
            <surname>Bowman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P. B.</given-names>
            <surname>Danzig</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D. R.</given-names>
            <surname>Hardy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>U.</given-names>
            <surname>Manber</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. F.</given-names>
            <surname>Schwartz</surname>
          </string-name>
          ,
          <article-title>The harvest information discovery and access system</article-title>
          ,
          <source>Computer networks and ISDN Systems</source>
          <volume>28</volume>
          (
          <year>1995</year>
          )
          <fpage>119</fpage>
          -
          <lpage>125</lpage>
          . doi:
          <volume>10</volume>
          . 1016/
          <fpage>0169</fpage>
          -
          <lpage>7552</lpage>
          (
          <issue>95</issue>
          )
          <fpage>00098</fpage>
          -
          <lpage>5</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>