<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.0 20120330//EN" "http://jats.nlm.nih.gov/publishing/1.0/JATS-journalpublishing1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:mml="http://www.w3.org/1998/Math/MathML" article-type="research-article" xml:lang="en">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">IR</journal-id>
<journal-title-group>
<journal-title>Information Research</journal-title>
</journal-title-group>
<issn pub-type="epub">1368-1613</issn>
<publisher>
<publisher-name>University of Bor&#x00E5;s</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">ir31263125</article-id>
<article-id pub-id-type="doi">10.47989/ir31263125</article-id>
<article-categories>
<subj-group xml:lang="en">
<subject>Research article</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Workplace user engagement with a semantic AI-based search tool</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>Lykke</surname><given-names>Marianne</given-names></name><xref ref-type="aff" rid="aff1"/></contrib>
<contrib contrib-type="author"><name><surname>Bygholm</surname><given-names>Ann</given-names></name><xref ref-type="aff" rid="aff2"/></contrib>
<contrib contrib-type="author"><name><surname>Svarre</surname><given-names>Tanja</given-names></name><xref ref-type="aff" rid="aff3"/></contrib>
<aff id="aff1"><bold>Marianne</bold> Lykke is a Professor at the Department of Culture and Communication, Denmark. She holds a PhD from &#x00C2;bo Academy in Finland. Her research is focused on user practice studies and user-centred methods to the design and evaluation of information design and knowledge organisation systems. She is particularly interested in information design in workplace environments and museum settings. She can be contacted at <email xlink:href="mlykke@ikk.aau.dk.">mlykke@ikk.aau.dk.</email></aff>
<aff id="aff2"><bold>Ann Bygholm</bold> is a Professor in Human Centered Informatics at Aalborg University. Her research focuses on how people adopt and adapt IT technologies in their everyday (work) practices, what role these technologies play in people&#x2019;s activities, and how IT can support and enable collaboration, knowledge sharing, and learning in specific situations.</aff>
<aff id="aff3"><bold>Tanja Svarre</bold> is an Associate Professor and co-lead of the research group Purposeful Technology Lab at the Department of Communication and Culture at Aalborg University. Her research interests include professionals&#x2019; information searching, use, and practice, and evaluation of interactive information retrieval systems. She can be contacted at <email xlink:href="tanjasj@ikk.aau.dk.">tanjasj@ikk.aau.dk.</email></aff>
</contrib-group>
<pub-date pub-type="epub"><day>25</day><month>05</month><year>2026</year></pub-date>
<pub-date pub-type="collection"><year>2026</year></pub-date>
<volume>31</volume>
<issue>2</issue>
<fpage>1</fpage>
<lpage>25</lpage>
<permissions>
<copyright-year>2026</copyright-year>
<copyright-holder>&#x00A9; 2026 The Author(s).</copyright-holder>
<license license-type="open-access" xlink:href="http://creativecommons.org/licenses/by-nc/4.0/">
<license-p>This is an Open Access article distributed under the terms of the Creative Commons Attribution-NonCommercial 4.0 International License (<ext-link ext-link-type="uri" xlink:href="http://creativecommons.org/licenses/by-nc/4.0/">http://creativecommons.org/licenses/by-nc/4.0/</ext-link>), permitting all non-commercial use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
</license>
</permissions>
<abstract xml:lang="en">
<title>Abstract</title>
<p><bold>Introduction.</bold> This study investigates non-professional searchers&#x2019; engagement with and challenges in using an AI-based workplace search tool. The tool included twelve AI-assigned, domain-specific metadata types and information from internal and external sources. Drawing on AI literacy perspectives, the study identifies competencies and support needed for effective workplace use.</p>
<p><bold>Method.</bold> A case study was conducted using an exploratory sequential mixed-methods design. Data included an interview with a corporate information specialist responsible for AI metadata development, a questionnaire with seventy searchers, and semi-structured interviews with nine searchers.</p>
<p><bold>Analysis.</bold> Preparatory interviews provided context for analysis. Questionnaire data were examined using uni- and bivariate statistics, while interview data were thematically analysed to explore searcher engagement and challenges.</p>
<p><bold>Results.</bold> The metadata types were found relevant for both exploratory and known-item searches. Users generally found the tool easy to use but identified challenges: domain knowledge was required; associated information needed enrichment; AI metadata roles were not immediately clear; and some routines had to be adapted.</p>
<p><bold>Conclusions.</bold> Searchers demonstrated AI competencies and were able to manage challenges. Effective use of AI-based search tools requires experience, domain knowledge, an explorative mindset, and continuous interaction. AI competence development can be understood as the coordinated deployment of tangible, intangible, and human resources supporting advanced information-seeking practices.</p>
</abstract>
</article-meta>
</front>
<body>
<sec id="sec1">
<title>Introduction</title>
<p>Artificial intelligence (AI) is currently a major topic in both society and research, not least since the dawn of end-user generative AI in 2022. AI has the potential to disrupt human life, e.g., how we work, live, communicate, and get medical help (Elliott, 2019). One task that can be handled by AI is classifying text by means of machine learning, which can take the form of being either supervised (<xref ref-type="bibr" rid="R20">Kadhim, 2019</xref>) or unsupervised (<xref ref-type="bibr" rid="R41">Thangaraj &#x0026; Sivakami, 2018</xref>), or a combination of the two (<xref ref-type="bibr" rid="R46">Wu et al., 2025</xref>).</p>
<p>Search and metadata assignment are among the scientific areas that have explored the potential of AI for various text-based tasks (<xref ref-type="bibr" rid="R10">Corrado, 2021</xref>; <xref ref-type="bibr" rid="R17">Golub, 2021</xref>; <xref ref-type="bibr" rid="R19">Jha, 2023</xref>; <xref ref-type="bibr" rid="R29">Mwantimwa &#x0026; Msoffe, 2025</xref>; <xref ref-type="bibr" rid="R44">Vrindha &#x0026; Syamili, 2025</xref>), and within different contexts, such as libraries (<xref ref-type="bibr" rid="R2">Asula et al., 2021</xref>), scientific databases (<xref ref-type="bibr" rid="R28">Moulaison-Sandy et al., 2021</xref>), academic papers (<xref ref-type="bibr" rid="R47">Yang et al., 2023</xref>), university repositories (<xref ref-type="bibr" rid="R24">Lowe et al., 2021</xref>), datasets (<xref ref-type="bibr" rid="R5">Chen et al., 2020</xref>), and tweets (<xref ref-type="bibr" rid="R36">Samuel et al., 2020</xref>).</p>
<p>However, little is known about how AI can assist in text-based enterprise search. Contrary to the examples given above, text-based enterprise information is characterised by being heterogeneous, existing in a plethora of formats, and being stored across a diversity of information systems (<xref ref-type="bibr" rid="R18">Gunadi &#x0026; Albayrak, 2015</xref>; <xref ref-type="bibr" rid="R22">Kruschwitz &#x0026; Hull, 2017</xref>). At the same time, enterprise search differs from information searching in established databases, such as library databases, and on the Internet by having a larger share of people search, shorter queries, and few advanced queries (<xref ref-type="bibr" rid="R11">Domke et al., 2018</xref>; <xref ref-type="bibr" rid="R40">Svarre, Lykke, &#x0026; Bygholm, 2024</xref>).</p>
<p>Enterprise search has been associated with various challenges in previous research. Language use is a significant issue. In corporate settings, there are often multiple professional languages involved, and since information for problem-solving is often combined with information from multiple professional groups and corporate information sources, it can be difficult to find a comprehensive set of search terms, due to domain-specific language use, geographical variations, and changes over time (<xref ref-type="bibr" rid="R7">Cleverley &#x0026; Burnett, 2015</xref>; <xref ref-type="bibr" rid="R15">Furnas et al., 1987</xref>; <xref ref-type="bibr" rid="R32">Nielsen, 2005</xref>; <xref ref-type="bibr" rid="R37">Schuff et al., 2016</xref>). Metadata quality is another frequent problem. <xref ref-type="bibr" rid="R39">Stocker et al. (2015)</xref> identified barriers related to adequacy and completeness of metadata. Other challenges are related to the information searcher. <xref ref-type="bibr" rid="R14">Freund (2015)</xref> identified challenges, such as searchers&#x2019; awareness of information and sources, the abundance of information available, access control, and the amount of time available to search and use information.</p>
<p>The purpose of this study was to get insight into how enterprise searchers used and assessed the support provided by a search tool that is based on AI-generated metadata and contextual information from a diverse set of corporate sources linked to the metadata. The study took place in an international biotechnology company that conducts research, development, and production of industrial biotechnological products. Through several user studies, a need was identified for a tool to support searchers with domain-specific, contextual metadata that could guide searchers to relevant information and extend the search across time and academic domains (<xref ref-type="bibr" rid="R25">Lykke, Bygholm, S&#x00F8;ndergaard, &#x0026; Bystr&#x00F6;m, 2022</xref>; <xref ref-type="bibr" rid="R40">Svarre, Lykke, &#x0026; Bygholm, 2024</xref>). Using Scibite, an ontology-based text-mining search engine, a set of twelve company-specific, as well as general biotechnological metadata types, was added to the display of retrieved documents in the form of clickable metadata linking to internal and external information sources. The study examined the functionality of (a) the AI-generated metadata and (b) the information that the metadata linked to in internal and external resources.</p>
<p>Specifically, the aim was to get insight into</p>
<list list-type="bullet">
<list-item><p>how corporate searchers understood, used, and valued the AI-generated metadata,</p></list-item>
<list-item><p>how they judged the usefulness and transparency of the information that searchers were directed to when they clicked on one of the twelve AI metadata types,</p></list-item>
<list-item><p>and what literacy challenges they met in the AI-based search.</p></list-item>
</list>
</sec>
<sec id="sec2">
<title>Related work</title>
<p>Here, we first outline the importance of metadata in enterprise search to elaborate on the specific role of metadata in this particular context. Next, we present AI-based solutions for handling metadata to provide a framework for the case presented later. We focus on AI solutions based on machine learning, since LLM-based solutions represent a very different approach in working with metadata. Lastly, we provide studies that have presented evaluations or user studies to set the stage for the potential of AI-based metadata from an end-user perspective.</p>
<sec id="sec2_1">
<title>Enterprise search and metadata</title>
<p>Enterprise search differs from general Web search, because of the differing characteristics of internal platforms (<xref ref-type="bibr" rid="R13">Fagin et al., 2003</xref>; <xref ref-type="bibr" rid="R38">Schymik et al., 2015</xref>). This often leads to reduced satisfaction among users, since they are accustomed to rapid improvements in Web search (<xref ref-type="bibr" rid="R43">Townsend &#x0026; Mathieu, 2018</xref>). While many studies have been conducted to understand general search behaviour (e.g., <xref ref-type="bibr" rid="R16">Given et al., 2023</xref>), less attention has been given to enterprise search (<xref ref-type="bibr" rid="R45">White, 2020</xref>).</p>
<p>Various studies have investigated the characteristics of employees searching for information as part of solving work tasks in their workplace. Departing from different types of internal systems, the literature confirms that different sources are used to locate relevant information for a task. <xref ref-type="bibr" rid="R27">Mathieu (2022)</xref> identifies how a diversity of internal and local sources are used on the path towards relevant information for a task.</p>
<p>Several authors point towards the need for contextual information and metadata, when conducting a search. <xref ref-type="bibr" rid="R1">Allard et al. (2009)</xref> identified how it is important to engineers that contextual information is available for the information they are looking for, since the context explains and elaborates on the needed information. To illustrate, <xref ref-type="bibr" rid="R14">Freund (2015)</xref> showed how document genres could be used to identify documents that would have specific contextual requirements, such as purpose, restrictions, and the like. However, according to <xref ref-type="bibr" rid="R27">Mathieu (2022)</xref>, metadata initiatives, if existing at all, are often unstructured or ad hoc, and mostly capture limited fields, such as date, version, project affiliation, or authors and/or modifiers.</p>
<p><xref ref-type="bibr" rid="R8">Cleverley &#x0026; Burnett (2019)</xref> showed how bad or even missing metadata caused dissatisfaction among searchers and emphasised the importance of good titles and metadata for enterprise search. In an earlier paper, <xref ref-type="bibr" rid="R9">Cleverley et al. (2017)</xref> identified how unclear metadata can have an impact on the understanding of information quality.</p>
<p>When too many sources are gathered in an internal system, they can cause retrieval challenges for employees. <xref ref-type="bibr" rid="R27">Mathieu (2022)</xref> found that many sources cause overlaps between information units, as well as information overload. Furthermore, she identified issues with employees being presented with information in search results that had restricted access for some users, which was also a source of frustration. By contrast, <xref ref-type="bibr" rid="R8">Cleverley &#x0026; Burnett (2019)</xref> identified dissatisfaction, when users were looking for known information that could not be found, because it was not indexed at the time of retrieval. While trustworthiness of internal information is highly valued, the same is the case for easy access (<xref ref-type="bibr" rid="R1">Allard et al., 2009</xref>). Thus, restricted access can be one among several factors that lead users to enter the Internet for information that, in some cases, can be easier to access.</p>
</sec>
<sec id="sec2_2">
<title>AI for enterprise search</title>
<p>As identified in the introduction, AI has been used for a variety of text-based tasks. However, it has also been suggested as a solution for supporting and improving enterprise search. Pointing out the necessity of search expertise to succeed in searching, <xref ref-type="bibr" rid="R9">Cleverley et al. (2017)</xref> conclude their paper, by pointing towards machine learning, semantic networks, and tagging as possible approaches to improving employees&#x2019; ability to locate information. Later work has made these suggestions more specific. From the literature on the potential in libraries in general, <xref ref-type="bibr" rid="R33">Oyighan et al. (2024)</xref> mentions natural language processing (NLP) as a tool for metadata extraction and generation, which can handle fast growing collections, as well as make metadata more responsive to specialised needs.</p>
<p><xref ref-type="bibr" rid="R21">Kandepu and Harry (2023)</xref> focus on content management systems (CMS) in organisations and identify several solutions for supporting users, out of which some are particularly relevant to the current context of enterprise search. One is the use of semantic clustering, as well as different natural language processing (NLP) analyses, for identifying topics and establishing relationships for discovery. Another is using knowledge graphs to identify content relationships on the basis various data, including metadata and user data.</p>
</sec>
<sec id="sec2_3">
<title>Evaluations and use of AI in the context of search and metadata</title>
<p>Different studies examine how AI-based solutions are being accepted and used. One line of studies focusses on information professionals and how they accept using AI for tasks that were previously manual. <xref ref-type="bibr" rid="R42">Togia et al. (2026)</xref> used a questionnaire to identify differences in use and acceptance among Greek librarians. They reported that only very few librarians used AI for creating and enhancing metadata, and for automated subject indexing. Academic librarians reported to have a higher readiness to incorporate AI in their work, as well as a higher frequency of use, when compared to public librarians. Similar findings were made by <xref ref-type="bibr" rid="R6">Chen and Li (2024)</xref>, who conducted a survey of metadata professionals&#x2019; use of AI for cataloguing and metadata creation. The authors found that AI did not have an important role in respondents&#x2019; work with metadata, and that the majority did not find AI helpful in the quality of their work or in terms of efficiency. On the other hand, <xref ref-type="bibr" rid="R34">Pinar &#x0026; Cox (2025)</xref> used a literature review with fifty-four papers to identify the biggest challenges in using AI in libraries and archives. They found that the challenges related to finances, data management, and ethics were the most frequent, while metadata and indexing occurred less, but was still observed in twenty-five out of fifty-four papers. It appears that AI is still being integrated in work routines, where it has potential, but metadata professionals also see challenges in its use. While libraries and archives are well covered in the literature, no papers have been identified that cover the corporate perspective.</p>
<p>While we have presented the use of AI for various metadata tasks from the metadata professional&#x2019;s perspective, another highly relevant view is to understand the end-user&#x2019;s perspective. How are end-users searching with the help of AI generated metadata? Does it change their search practices? Little focus has been put on this perspective in the literature. No papers report on library or archive end-users. In the enterprise context, two papers were located: one experiment, and one study that included end-users.</p>
<p><xref ref-type="bibr" rid="R26">Marques &#x0026; Murphy (2022)</xref> conducted an experiment in which they tested how semantic techniques could identify relevant passages for software engineers. Based on variations of word3vwc and BERT, the authors used fifty randomly selected Android development tasks and 133 artifacts to perform the experiment using AnswerBot as the baseline. Precision and recall were used as measures of evaluation. The experiment showed that the alternative approaches, and particularly BERT, achieved similar levels of recall as the baseline approach, and thus could hold potential within the software domain.</p>
<p><xref ref-type="bibr" rid="R48">Zhou et al. (2023)</xref> evaluated an inhouse Q&#x0026;A system in a large tech company, that is based on two BERT models: one for reranking and one for extracting answer spans. The solution was evaluated using logs and interviews with employees. Qualitative evaluation showed that responses could not be assessed from their strict textual expression. Rather, currency, trustworthiness, context, and situation affected the assessment. Further, contingent answers improved the user experience, even though they were not perfect. Thus, the answers contributed with additional information and alternative access beyond search engine results. The evaluation emphasised the importance of updated datasets for this type of solution, as well as multiple answers, because single answers can lack nuance.</p>
<p>Enterprise search research shows that metadata is crucial for providing context, supporting relevance judgments, and enabling effective information access. AI has been proposed as a way to scale and improve metadata creation and enrichment. Existing studies mainly examine AI use from the perspective of metadata professionals, especially in libraries and archives. These studies report low adoption rates and highlight concerns about quality, ethics, and organisational readiness. The enterprise or corporate context is largely missing from this body of research. End-user studies in enterprise search are rare and mostly focus on AI-supported retrieval or question-answering systems, rather than on metadata itself. Nevertheless, these studies indicate that users value contextual relevance, trustworthiness, and informational cues over strict accuracy. To date, no empirical studies have directly examined how AI-enhanced metadata influences enterprise end-users&#x2019; search practices, a gap this paper seeks to address.</p>
</sec>
</sec>
<sec id="sec3">
<title>Conceptual framework</title>
<p>Because AI applications gain traction in many areas, the interest in AI literacy, i.e. what is required to use these applications in a sensible and productive way, also increases. Within recent years, a number of papers and reviews have been published with the aim of identifying what the concept of AI literacy might involve and how best to afford the competencies concerned. In this paper, we drew on different conceptualisations of AI literacy to understand the challenges employees experience when using AI metadata in their search practice. Focus was on AI literacy for non-AI professionals in a workplace setting.</p>
<p>The concept of literacy, traditionally understood as the ability to read and write, also includes numerical literacy, health literacy, financial literacy, media literacy, and digital literacy, to name but a few. An often-used reference to the notion of AI literacy is <xref ref-type="bibr" rid="R23">Long &#x0026; Magerko (2020)</xref>, who mention the need to investigate &#x201C;what new competencies will be necessary in a future in which AI transforms the way we communicate, work, and live with each other and with machines&#x201D; ( p. 1), and they refer to this set of competencies as AI literacy. In their review of the AI literacy of employees at digital workplaces, Cetidamar et.al. (2024) distinguish between studies focusing on AI literacy in education and AI literacy at workplaces, and, furthermore, between AI literacy at the individual level and AI literacy at the organisational level. They note that most studies of AI literacy have been conducted at the individual level and around education. In our attempt to understand employees&#x2019; challenges and then discuss what can be done to support employees, we need both the individual and the organisational level. The individual level is about the competencies needed for individual members of the workforce to use AI applications in a productive way and the organisational level is about what it takes for an organisation to benefit from applying AI in their business.</p>
<p>An example of a conceptualisation of AI literacy at the individual level is <xref ref-type="bibr" rid="R30">Ng et al. (2021)</xref> which, based on a literature review and inspired by Bloom&#x2019;s taxonomy, proposed four types of competencies to characterise different kinds of capabilities required in interaction with AI applications. Bloom&#x2019;s taxonomy (<xref ref-type="bibr" rid="R3">Bloom, 1956</xref>) classified cognitive skills into six hierarchical levels, with each level building upon the previous one, and is a widely used framework within the educational area to identify learning objectives that target different levels of complexity independently of specific learning domains. The taxonomy has been revised and expanded several times (Krathwohl 2002; Huitt 2011). The first three aspects of the AI literacy concept proposed by <xref ref-type="bibr" rid="R30">Ng et al. (2021)</xref> cluster the six levels from Bloom into three, that is 1) know and understand, 2) use and apply, and 3) evaluate and create. With the fourth aspect, ethical issues, they add an ethical dimension to the concept and include issues, such as transparency, accountability, and fairness.</p>
<p>Based on a revised version of the conceptual framework, <xref ref-type="bibr" rid="R31">Ng et al. (2024)</xref> also developed a questionnaire emphasising not only cognitive but also behavioural and attitudinal issues to measure student learning outcomes in AI learning programmes. Other authors working within the educational and individual field have also developed questionnaires and instruments to measure AI literacy. What they had in common was that they were based on some core constructs identified through literature review, sometimes supported by various theoretical constructs, expert testimony, and testing with students or citizens. For example, Laupiciler et al. (2023) based their scale for the assessment of non-experts in AI literacy on &#x201C;technical understanding,&#x201D; &#x201C;critical appraisal,&#x201D; and &#x201C;practical application.&#x201D; Wang et al. (2023) used &#x201C;awareness,&#x201D; &#x201C;use,&#x201D; &#x201C;evaluation,&#x201D; and &#x201C;ethics&#x201D; as basic concepts in a scale for measuring AI literacy. Pinski and Benlian (2023) aimed to develop a scale for measuring general AI literacy, and, based on concepts drawn from the information science domain, they suggested seven dimensions grouped in three categories, that is AI actor knowledge, AI process knowledge, and AI experience. There were then a number of suggestions as to what should be included in the education of students and citizens in the field of AI and how this knowledge could be measured. Common to these was that knowledge of the technology was not enough; you also need practical experience and skills that allow you to assess the consequences of using the AI application critically.</p>
<p>Moving to the organisational level, the findings may be considered somewhat similar. That is, acquiring AI technology in itself does not necessarily make a difference to an organisation. In spite of the potential that AI technologies offer, organisations are faced with a number of challenges that prevent them from realising the benefits. AI is far from being a plug-and-play technology, as Fountaine et al. (2019) put it. They emphasised that it is equally important to align culture, structure, and ways of working to support AI adoption. Thus, there is a need for understanding what such an alignment might involve, that is how organisations build AI capability. Mikalef &#x0026; Gupta (2021) aimed at identifying the necessary organisational resources that will enable a company to build their AI capabilities. They drew on resource-based theory, the basic idea being that &#x201C;the building of resources facilitates the formation of organisational capabilities, which, in turn, drive performance gains&#x201D; (Mikalef &#x0026; Gupta, 2021, p. 2). Building on theoretical insight from resource-based theory, as well as studies outlining the challenges related to AI adoption, Mikalef &#x0026; Gupta (2021) proposed eight resources that allow organisations and companies to obtain AI capabilities. Using a classification scheme from the resources-based theory domain, the eight resources were grouped in three main categories: 1) Tangible resources, including data, technology, and basic resources, 2) Human resources, including technical skills and business skills, and 3) Intangible resources, including fostering inter-departmental coordination, organisational change capacity, and risk proclivity. The authors underscored that although both tangible and human resources are necessary and a prerequisite, the intangible resources are extremely important for obtaining AI capabilities. These are characterised as more difficult to identify and also more unique because they are developed through a mix of history, people, and processes that characterise the specific organisation.</p>
<p>Cetidamar et al. (2024) focused on employees and aimed at developing a model of the competences needed to utilise AI technologies for achieving company goals. The idea was that strengthening employees&#x2019; AI literacy would enable them to participate in the design and use of AI technologies. Furthermore, they stated that AI literacy is &#x201C;...an organisational-level capability where individual capabilities add up to an organisational level strength.&#x201D; (Cetidamar et al., 2024, p. 810). Thus, they argued that employees&#x2019; collective AI literacy builds an organisational capacity. Based on a literature search and a bibliometric analysis, they suggested that AI literacy for employees should consist of four capabilities, that is technology-related, work-related, humanmachine related, and learning-related.</p>
<p>To sum up, AI literacy can be considered from an individual as well as an organisational perspective. The individual view focuses on employees&#x2019; capabilities in using and interacting with AI-based systems. Although there may be overlaps, the corporate view differs in including how organisations build capabilities and company goals, and how employees can be included in the design and use of AI. Together, the two perspectives offer a complete view on human AI capabilities in workplace contexts.</p>
</sec>
<sec id="sec4">
<title>The case study and the AI-based search tool</title>
<p>The study took place in an international biotechnology company that conducts research, development, and production of industrial biotechnological products and biopharmaceutical ingredients. The search tool was developed to support search for internal information available in a corporate research archive. The digital research archive was established in the 1980s and contained internal documentation about the company&#x2019;s products and R&#x0026;D work, e.g., lab test reports, memos, guidelines, and project reports. In general, the research archive was used to find information about previous R&#x0026;D work and historical information about, for example, products, projects, techniques, and industry applications. Specifically, it was used by the searchers to find new application areas for specific products; look up previous results for certain test techniques or materials; or experience with the application of a product in a specific industry.</p>
<p>The documents were uploaded to the research archive, and metadata were registered by the authors. The registration was based manually assigned metadata: document type, title, author(s), project number, industry, product name, external relations, and internal source. It was also possible to attach related documents in the form of PDF files. Access restrictions were specified by indicating allowed readers or groups. The metadata document category (for example, author, project number, industry, and product names) were registered using controlled drop-down lists. The research archive was accessible by the enterprise search system, which was based on SharePoint and, in addition to the research archive, provided access to the corporate information sources intranet, people directory, news, quality documentation database, laboratory system, and social media. The research archive could be searched as part of the enterprise search interface, and via an independent search interface. The search interface facilitated commandbased keyword searching and filtering by metadata.</p>
<p>The development of the search tool was initiated in 2020, where a local interview study with eight informants showed that the employees from R&#x0026;D had difficulty both searching for and assessing the relevance of retrieved documents. The metadata registration was optional and, therefore, all metadata categories were not necessarily linked to all documents. The document titles were not always designed appropriately and contained neither relevant search terms nor words that could be used to assess the content and relevance of the document.</p>
<p>The findings of the interview study were supported by a larger study of enterprise searching practices across different work areas and work tasks in the enterprise search system (<xref ref-type="bibr" rid="R25">Lykke, Bygholm, S&#x00F8;ndergaard, &#x0026; Bystr&#x00F6;m, 2022</xref>). The main finding of the study was the identification of an explorative, tracing search technique, where searchers, by use of historical and contextual knowledge, interactively tried out different search paths through the enterprise search system and its sources to put together a set of information that jointly provided the needed information. The needed contextual and historical information could, for example, consist of information about previous research projects or laboratory results or about earlier business application areas where an enzyme has been used or tested. The searchers did not always possess the necessary historical or contextual knowledge and often had to take a detour by consulting a colleague to get the needed information to continue the search and find the desired information for the search task (<xref ref-type="bibr" rid="R40">Svarre, Lykke, &#x0026; Bygholm, 2024</xref>). Thus, an important finding was the need for a tool to support searchers with specific contextual and historical information about, for example, research projects, lab results, and business application areas to support the tracing search strategy.</p>
<p>Based on these results, the company chose to use machine-learning categorisation to add highly contextual metadata to retrieved information, to make it easy for the searchers to orient themselves quickly in document content and information relevance and to guide the searcher through the added metadata to the needed contextual and historical information to extend the search strategy. By using Scibite, an ontology-based text-mining search engine, a set of twelve company-specific, as well as general biotechnological, metadata types were added to the display of retrieved documents in the form of clickable metadata links (see <xref ref-type="fig" rid="F1">Figure 1</xref>).</p>
<fig id="F1">
<label>Figure 1.</label>
<caption><p>Display of retrieved document with assigned AI-based metadata</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="c1-fig1.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>The twelve metadata categories were selected by information specialists in collaboration with the vendor (Scibite). Their selection was informed not only by their perceived importance for internal search processes, but also by considerations of practical applicability. One information specialist characterised this approach as &#x201C;<italic>the art of the possible</italic>&#x201D;. Consequently, certain types of information recognised as valuable for contextual searching, such as personal names, were excluded from the metadata schema. Within the organisation, individuals are identified primarily by their initials, and the inclusion of such identifiers would have generated an excessive number of non-discriminatory results. By contrast, entities, such as product names and enzymes, proved more amenable to systematic organisation and were, therefore, more readily incorporated into the metadata categories.</p>
<p>The aim was, through machine-learning assigned metadata, to highlight information from the retrieved document that was important both in terms of relevance assessment and formulation of search queries. When the searcher clicked on the assigned metadata, different types of either internal or external information were displayed depending on the metadata category. The added metadata led, for instance, to internal lab data reports and results for lab study identification numbers appearing in the retrieved document, to taxonomic information about organisms mentioned in the retrieved document from the external NCBI National Center for Biotechnology Information database, to project information and application areas from the internal R&#x0026;D project database when a project name and/or number was mentioned, or to predefined Google searches for companies whose names were found in the retrieved document. When a searcher clicked on the added metadata for, for example, the ELN lab test database, first a list of related tests was displayed. When the searcher clicked on one of the test numbers, information about the test was shown. The type of information shown was different for the twelve metadata categories (see <xref ref-type="table" rid="T1">Table 1</xref>). Some information came from internal sources, i.e., the lab database or the corporate product database, and from external sources, i.e., well-known nomenclatures or taxonomies, such as the NCBI. The choice of associated sources and information was decided by the corporate information specialists.</p>
<table-wrap id="T1">
<label>Table 1.</label>
<caption><p>The twelve machine learning metadata and related taxonomies.</p></caption>
<table>
<thead>
<tr>
<th align="center" valign="top">AI metadata</th>
<th align="center" valign="top">Description and related taxonomies</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">Companies</td>
<td align="left" valign="top">All companies we work with, based on data from <bold>SalesForce</bold></td>
</tr>
<tr>
<td align="left" valign="top">ELN</td>
<td align="left" valign="top">Matching on <bold>ELN</bold> numbers</td>
</tr>
<tr>
<td align="left" valign="top">Enzymes</td>
<td align="left" valign="top">Based on names/synonyms from <bold>EC nomenclature</bold></td>
</tr>
<tr>
<td align="left" valign="top">Lab Equipment</td>
<td align="left" valign="top">Matching on data from <bold>Labservice</bold></td>
</tr>
<tr>
<td align="left" valign="top">Luna numbers</td>
<td align="left" valign="top">Matching references to other Luna records</td>
</tr>
<tr>
<td align="left" valign="top">My MS</td>
<td align="left" valign="top">Matching references to <bold>My MS</bold> records</td>
</tr>
<tr>
<td align="left" valign="top">NN Numbers</td>
<td align="left" valign="top">Matching on NN numbers</td>
</tr>
<tr>
<td align="left" valign="top">Patent number</td>
<td align="left" valign="top">Matching on patents from main authorities</td>
</tr>
<tr>
<td align="left" valign="top">Products</td>
<td align="left" valign="top">Matching on product names from <bold>Promis</bold></td>
</tr>
<tr>
<td align="left" valign="top">Projects</td>
<td align="left" valign="top">Matching on project numbers + their stage e.g. DEV or OPT</td>
</tr>
<tr>
<td align="left" valign="top">Sequoia identifiers</td>
<td align="left" valign="top">Matching on valid <bold>Sequoia</bold> identifiers</td>
</tr>
<tr>
<td align="left" valign="top">Organism</td>
<td align="left" valign="top">Based on bacterial and fungal species from <bold>NCBI Taxon</bold></td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The development of the tool was carried out in collaboration with Scibite (<ext-link ext-link-type="uri" xlink:href="https://www.scibite.com/">https://www.scibite.com/</ext-link>), which also provided several of the taxonomies that formed the basis for the identification and assignment of metadata. In practice, however, it turned out that these external generic taxonomies, developed to represent a professional domain in general, were not sufficiently specific in relation to the company&#x2019;s use of and approach to categories. Therefore, internally developed taxonomies were primarily used, and even these had to be developed to achieve a sufficient quality in assignment of metadata.</p>
</sec>
<sec id="sec5">
<title>Research method</title>
<p>We used an exploratory sequential mixed-methods design (Clark et al., 2021) to study the use of and challenges related to the search tool. First, we reviewed the AI-based enterprise search tool with the purpose of gaining insight into the twelve types of AI metadata, with particular emphasis on the kinds of information they lead to. We also focused on interface design and functionality in interaction with the AI metadata, specifically investigating the visibility, accessibility, understanding, and usability of the metadata types and their associated information. The study was conducted between 15 January 2022 and 31 December 2022.</p>
<p>This review was followed by an interview with the information specialist responsible for the development of the AI metadata tool. The interview was semi-structured and aimed to illuminate the background and purpose of the AI metadata, the development process, and existing user experiences with the tool. In addition, during the development process, the development team held informal conversations with eight stakeholders, consisting of a mix of internal employees working with digitalization, enterprise systems, and R&#x0026;D tasks.</p>
<p>Next, we collected qualitative data on concrete end-user engagement and experiences with the AI interface, metadata, and associated information. Based on the findings from the qualitative interview study, we then designed a questionnaire study to assess the range and generalisability of the qualitative findings.</p>
<p>The end-user interviews were also semi-structured interviews. They opened with questions about participants&#x2019; jobs and organisational positions, their work tasks, and their use of the research archive in their work. Participants were then asked to carry out two recent searches, while explaining in detail their search moves and considerations. We were particularly interested in how they used and assessed the information provided by the AI metadata and the related information sources. Questions concerning the interviewees&#x2019; affiliations, work practices, and search tasks were designed to elucidate the context in which the AI search tool was employed. The subsequent structured questions were informed by established insights into challenges associated with enterprise search, as well as by the AI literacy literature concerning key competencies in the use of AI technologies. Open-ended questions emerged from observations of, and discussions about, the interactions that occurred during the searches undertaken by the interviewees as part of the interview. The interviews concluded with a general discussion of the role and usefulness of the semantic AI tool.</p>
<p>Interviews took place via MS Teams, with screen sharing enabled while participants carried out the two search tasks. Interviewees were located in their offices at the case company, while the three researchers were co-located in a conference room at the university. The interviews were audio-recorded and subsequently transcribed.</p>
<p>Nine people participated in the study (<xref ref-type="table" rid="T2">Table 2</xref>). The interviewees were sampled on the basis of two criteria. First, they were required to have used the newly developed AI search tool and the twelve AI metadata elements. Second, the sample was constructed to ensure collective representation of the organisational units and search tasks for which the tool was designed. Sampling and data collection were discontinued at the point at which additional interviews no longer yielded novel insights or emergent themes. Overall, participants worked with research and development of enzyme products (six participants), product safety (two participants), and product quality (one participant). It is important to note that the interviewees possessed limited experience with the newly introduced AI tool, since it had been released only one month prior to the commencement of the study.</p>
<table-wrap id="T2">
<label>Table 2.</label>
<caption><p>End-user interviewees.</p></caption>
<table>
<thead>
<tr>
<th align="center" valign="top">Number</th>
<th align="center" valign="top">Core area</th>
<th align="center" valign="top">Work area</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left" valign="top">1</td>
<td align="center" valign="top">Supply operations</td>
<td align="center" valign="top">Quality</td>
</tr>
<tr>
<td align="left" valign="top">2</td>
<td align="center" valign="top">R&#x0026;D</td>
<td align="center" valign="top">Formulation</td>
</tr>
<tr>
<td align="left" valign="top">3</td>
<td align="center" valign="top">Biosolutions</td>
<td align="center" valign="top">Liquid products</td>
</tr>
<tr>
<td align="left" valign="top">4</td>
<td align="center" valign="top">R&#x0026;D</td>
<td align="center" valign="top">Enzyme activity</td>
</tr>
<tr>
<td align="left" valign="top">5</td>
<td align="center" valign="top">Supply operations</td>
<td align="center" valign="top">Product safety</td>
</tr>
<tr>
<td align="left" valign="top">6</td>
<td align="center" valign="top">Biosolutions</td>
<td align="center" valign="top">Technical service</td>
</tr>
<tr>
<td align="left" valign="top">7</td>
<td align="center" valign="top">Supply operations</td>
<td align="center" valign="top">Product safety</td>
</tr>
<tr>
<td align="left" valign="top">8</td>
<td align="center" valign="top">Biosolutions</td>
<td align="center" valign="top">Liquid products</td>
</tr>
<tr>
<td align="left" valign="top">9</td>
<td align="center" valign="top">R&#x0026;D</td>
<td align="center" valign="top">Enzyme activity</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The transcriptions were read and coded inductively by the three researchers. Initial open coding was conducted individually, after which the researchers discussed and consolidated the identified themes. In addition to identifying themes, the discussion aimed to determine which themes should be investigated further through the questionnaire.</p>
<p>The questionnaire was distributed to 297 research archive users. Participants were selected based on search frequency, with employees who had conducted the highest number of searches during the previous three months invited to respond. The questionnaire consisted of thirty-eight questions, including opinion and assessment questions using ordinal scales, as well as background and factual questions concerning, for example, types of searches conducted in the archive, search frequency, years of employment, and organisational division and function.</p>
<p>Prior to answering the questionnaire, respondents were asked to view a one-minute video introducing the functionality of the AI metadata. This introduction was included, because the research archive search interface displayed two types of metadata. On the left side of the interface, metadata used to filter search results was displayed, while the machine-learning-based metadata was shown on the right side. During the interviews, it became clear that several participants did not distinguish between these two types of metadata. The introductory video was, therefore, included at the beginning of the questionnaire to ensure that respondents understood what was meant by AI metadata.</p>
<p>Seventy users completed the questionnaire in full, corresponding to a response rate of 24%. The questionnaire was prepared and the data collected using the online survey tool SurveyExact. Subsequently, the data were analysed using Excel. Uni- and bivariate statistical analyses were conducted to examine distributions and correlations.</p>
</sec>
<sec id="sec6">
<title>Findings</title>
<p>We start the presentation of findings by describing how the searchers assessed the usefulness of the AI metadata and the associated information in their search activities. Hereafter, we zoom in on user engagement and on what characterised the searchers&#x2019; interaction with the AI metadata and related information. We present their specific search activities and the challenges that characterised their use of the semantic tool. The study findings are presented in an integrated manner, combining results from the initial qualitative interview study involving nine users and the subsequent quantitative questionnaire study, completed by seventy respondents. Participants in both samples were selected to represent the groups of information searchers for whom the AI tool is intended to provide support in their search.</p>
<sec id="sec6_1">
<title>Usefulness of machine learning metadata and related information</title>
<p>All nine interviewees expressed that the twelve metadata types were relevant in relation to search and that the metadata referred to relevant domain-specific information that they could use for the context-oriented clarification and specification of their search.</p>
<disp-quote>
<p><italic>I think the metadata can be relevant in many contexts. Here is an example of a document from the research archive that refers to another document through the metadata. Looking at it, I can see that I get information about the relationship between two lab samples that I didn&#x2019;t know were related. So, this leads me to another place that I wouldn&#x2019;t be able to get to through the common metadata filtering.</italic> (4, R&#x0026;D, enzyme activity)</p>
</disp-quote>
<p>The search constitutes an instructive example of how AI-generated metadata linking data and information across the organisation&#x2019;s information sources over time, facilitated access to both recent and historical knowledge, thereby supporting the understanding and resolution of the specific search problem. The purpose of AI metadata was precisely to enable retrieval across temporal spans, linguistic evolution, and professional domains through the use of extended language models as explained by the interviewee. In the search situation mentioned above, the AI metadata led the searcher to relevant information that gave a deeper understanding of an enzyme from two laboratory experiments conducted at different points in time.</p>
<p>The perceived relevance of metadata was supported by the questionnaire findings, which showed that AI metadata was assessed as useful or very useful (<xref ref-type="fig" rid="F2">Figure 2</xref>). Specifically, metadata representing enzymes at different stages of the lifecycle in different sources were highlighted as valuable within the search process. For example, enzymes under development were represented through identification numbers and LUNA numbers in ELN and LUNA; finished products associated with various business areas were expressed through product and project names in the Product and Project sources; enzymes at a more general level were represented through generic nomenclature within the Enzyme and Organism sources; and information about enzyme quality were contained in the My MS source.</p>
<fig id="F2">
<label>Figure 2.</label>
<caption><p>Questionnaire results: Usefulness of AI metadata from the different information sources (n=70).</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="c1-fig2.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>Questionnaire respondents found AI metadata most relevant in relation to known-item search and specific search (<xref ref-type="fig" rid="F3">Figure 3</xref>). This is likewise reflected in the interviews, in which the interviewees explained that their task is to investigate how a specific enzyme may be applied in other business areas, or how a particular enzyme must be technically adapted and implemented in different contexts. Such search tasks are both highly specific and exhibit characteristics of known-item searching, insofar as the interviewees are aware that prior work concerning the extension of enzyme applications has been conducted and can be retrieved. At the same time, these search tasks are exploratory, since the information seekers do not know precisely which prior work has been undertaken, nor do they possess detailed knowledge of this work in order to retrieve it.</p>
<fig id="F3">
<label>Figure 3.</label>
<caption><p>Questionnaire results: Usefulness of AI metadata in relation to search types (N=70)</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="c1-fig3.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>The interviewees further explained that AI-generated metadata was primarily pertinent to research and development&#x2013;related tasks, where the objective is to explore novel possibilities for an enzyme, rather than, for example, activities within product safety, where the work centres on identifying established findings concerning safety issues associated with a specific product. Within safety-related work, the results were well established and closely tied to the specific enzymes or products under investigation; consequently, such information cannot readily be transferred to other contexts and is, therefore, not considered important to share across tasks in the same manner as in exploratory search activities.</p>
<p>The interviewees also expressed that the related information was in some cases incorrect in relation to the company&#x2019;s specific perspective and in particular naming of enzymes which, in several instances, diverged from, for example, the nomenclature employed in general taxonomies used by the AI algorithm:</p>
<disp-quote>
<p><italic>The only enzyme that shows up is an enzyme that is not used as part of the wanted measurement. It is not the enzyme we are interested in. The reason it shows up is because the name that I searched for is an accepted name inside the external enzyme database used for the AI classification, but in the taxonomy, it is accepted for a different enzyme than the one I&#x2019;m looking for. We use a different name internally.</italic> (1, R&#x0026;D, enzyme activity)</p>
</disp-quote>
<p>In other search situations, the information was perceived as superfluous and caused more disruption than benefit. In another search demonstration, as part of the interviews, the AI-driven metadata assignment had not accounted for the fact that an enzyme may serve both as the organism under investigation and as an ingredient within a methodological test system. This error recurred across several searches, giving rise to both frustration and diminished trust in the AI tool.</p>
<disp-quote>
<p><italic>This information is not important in this context because the reagents mentioned are used as part of the method. The reagent is not the substance that we are investigating in this study, just part of the method.</italic> (5, supply operations, product safety)</p>
</disp-quote>
<p>These examples of inappropriate metadata assignment illustrated the importance of ensuring that the taxonomies used for AI metadata reflect the perspective and way of working of the case company. In the first example, the external enzyme taxonomy underlying the AI algorithm classified enzymes based on principles that differed from those used within the company, which resulted in incorrect metadata assignment. In the second example, the taxonomy did not allow for description of the specific role of an enzyme in a study, for example, whether it was an auxiliary substance in the test method or the active substance under investigation. One of the interviewees highlighted that such contextual nuances make it very difficult to automate metadata assignment fully. These examples further demonstrated the importance of information searchers&#x2019; domain-specific knowledge. Such knowledge is necessary to assess and comprehend both the significance and the limitations of the retrieved metadata and the information to which they lead. This includes the ability to discern nuances, such as the fact that an enzyme may assume different roles, either as the principal product or as an ingredient within a product.</p>
<p>With regard to practical use and user&#x2013;system interaction, the questionnaire study showed that respondents agreed that it was clear or very clear how searchers gained access to AI metadata and associated information sources (<xref ref-type="fig" rid="F4">Figure 4</xref>). Respondents also indicated that it was easy to understand that AI metadata provided access to information in other information sources (<xref ref-type="fig" rid="F5">Figure 5</xref>). When comparing the questionnaire responses with the interview data, it becomes evident that the introductory video included in the questionnaire provided a good understanding of the interface functionality. The nine interviewees had not viewed the introductory video, and this lack of introduction was reflected in their assessment of user&#x2013;system interaction, where they emphasised that the interface was not intuitively understandable and required practice.</p>
<fig id="F4">
<label>Figure 4.</label>
<caption><p>Questionnaire results: Usefulness of access to AI metadata (n=70)</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="c1-fig4.jpg"><alt-text>none</alt-text></graphic>
</fig>
<fig id="F5">
<label>Figure 5.</label>
<caption><p>Questionnaire results: Usefulness of access to related information (n=70)</p></caption>
<graphic xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="c1-fig5.jpg"><alt-text>none</alt-text></graphic>
</fig>
<p>Once the interviewees had tested the new functionality across several searches during the interview, they highlighted direct access to data in other sources as a significant strength:</p>
<disp-quote>
<p><italic>It exposes me more to this external database, which makes it more likely that I will use it. It increases my awareness that there is this resource to draw on. I think that has a beneficial effect on the research organisation, that these links make it easy to navigate to both internal and external sources.</italic> (4, R&#x0026;D, enzyme activity)</p>
</disp-quote>
<p>They further emphasised increased visibility of data and efficient, effortless, and fast access:</p>
<disp-quote>
<p><italic>I think the one with ELN is helpful. In this way you can find your way into the ELN faster. You don&#x2019;t have to open a new browser and search for it yourself.</italic> (5, supply operations, product safety).</p>
</disp-quote>
</sec>
<sec id="sec6_2">
<title>Challenges in engagement with the AI metadata and related information</title>
<p>The interviews provided further insight into the use and usefulness of AI-generated metadata. The interview revealed and provided a more detailed account of two principal challenges that influenced how searchers engaged with and benefited from the AI-generated metadata, namely the significance of domain knowledge and the design of the interface. This section outlines these challenges and examines how the metadata contributed to the search process.</p>
<p>As mentioned above, a good search result required domain knowledge, such as knowing that an enzyme exists in several variations and has been studied across multiple studies over time, in order to take full advantage of the AI tool. Although the purpose of the tool was to provide contextual information to the searcher, understanding the AI metadata and related information still required domain knowledge, as well as knowledge of how to use metadata and information to improve a search. Effective use also required continuous interaction and ongoing critical assessment of search results. Several interviewees expressed that there may be a need to enrich the AI metadata display with explanations of how the metadata could support searching.</p>
<disp-quote>
<p><italic>Sometimes it seems that this metadata enrichment is pointless, because it requires you to have insight beforehand. I&#x2019;m just saying that you shouldn&#x2019;t think that you can ever create a system that means that anyone would come in from the street and just sit down and understand what we have been doing for the past many years. It requires some insight.</italic> (9, R&#x0026;D enzyme activity)</p>
</disp-quote>
<p>The interviewees emphasised that it may be necessary not only to provide explanations for AI metadata, but also to enrich the information presented in the information sources to which searchers are directed. For example, one interviewee explained how the laboratory system only provided a database-specific identification number as a header. This number needed to be supplemented with a title of the laboratory study, including the investigated enzyme, in order to be meaningful to the searcher:</p>
<disp-quote>
<p><italic>I would have liked a little more information than those rather spartan lists. When I go to the referred information in the lab database, I am not presented with the title. I&#x2019;m presented with a database-specific ID that makes no sense to me. We need to get a title, because it is the info that means something to me.</italic> (9, R&#x0026;D enzyme activity)</p>
</disp-quote>
<p>Another challenge was related to interface design, in which information searchers were presented with filtering via manually assigned metadata on the left side and AI metadata with related information from internal and external sources on the right side. This distinction was unclear to several interviewees. In particular, the difference between the two types of metadata and their respective functions in the search process was not immediately apparent.</p>
<disp-quote>
<p><italic>There is a difference in functionality where this one links out to an external database and this one does a new search. There is no separation of the different functionalities. They are kind of mixed into each other. The functionality can be helpful, but it is not intuitive until you have used it quite a few times. (6, biosolutions, technical service)</italic></p>
</disp-quote>
<p>Filtering via metadata was a well-known function, but it was not intuitively understandable that clicking on AI metadata initiated a new search in an internal or external database, thereby providing access to information about related aspects of the original search, such as companies, products, or laboratory results. The interviewees emphasised that this new functionality would require practice over time and the development of new search routines. It also emerged that such misunderstandings initially generated scepticism and reluctance toward the tool.</p>
<p>The AI metadata appeared most relevant for R&#x0026;D searches, while interviewees from product safety had more difficulty identifying how they could use the functionality. Safety-related searches were described as highly standardised, both because they constitute precise, known-item searches as described above and, from a technical search perspective, because the group of safety employees had developed and inherited practices of manually enriching important documents with contextual information in the title to ensure retrievability. This resulted in safety-related searching being conducted in a systematic and consistent manner. However, during the interview discussions with safety employees, it became apparent that this practice also imposed certain limitations, and that by utilising the new search functionalities and AI-generated metadata, they could extend their use of the enterprise search system. They concluded that the metadata might serve to refine and specify the standardised known-item searches, although this would necessitate the development of new routines. Furthermore, they emphasised that the new search capabilities enabled them to undertake novel types of searches; however, this too would require reconsideration and the establishment of new routines.</p>
<disp-quote>
<p><italic>There could well be examples where it could be interesting to go in and look at the information linked to AI metadata. For example, the link to these MyMS documents is interesting. A relevant service, but not something that I have missed as such, because in safety we do a recovery batch. We need to be able to document everything and everything needs to be able to be found, so part of the procedure is to add keywords. But I think that it might be a question of getting to know the function. (7, supply operations, product safety)</italic></p>
</disp-quote>
</sec>
</sec>
<sec id="sec7">
<title>Discussion</title>
<p>The aims of the study were to gain insight into how workplace searchers used AI-generated metadata and the information associated with it, and to identify literacy challenges in user&#x2013;system interaction to explore how searchers can be supported. <xref ref-type="bibr" rid="R4">Cetindamar et al. (2024)</xref> distinguishes between AI literacy at the individual and organisational level. However, the principal insight derived from the conceptual framework is that experience in the practical use of technology and knowledge is essential for the development of AI capabilities at both the individual and organisational levels. In the discussion, we focus on users&#x2019; experiences with AI-generated metadata, examining both how such metadata supports and enhances search processes, how it presents challenges for information searchers, and how they may best be equipped to utilise AI-generated metadata effectively.</p>
<sec id="sec7_1">
<title>Explorative and critical application</title>
<p>The study showed that searchers generally understood and were able to apply the new AI metadata in search. In relation to R&#x0026;D search tasks, searchers could immediately see how to use AI metadata, whereas searchers from product safety needed to interact with the metadata across different tasks before they could assess its potential.</p>
<p>Searchers working with R&#x0026;D and application of enzymes had search tasks in which they sought information about a specific enzyme; that is, the task was specific in nature, yet it also had an exploratory dimension, since they did not know precisely what research had been conducted on the enzyme or whether it would be applicable for their purposes. What was crucial for them was to ensure that they identified relevant prior R&#x0026;D work upon which they could build. They explained how the broad set of AI-generated metadata collectively provided insight into the research conducted over time on a given enzyme, guiding and reminding the information searcher of which sources to consult and which search terms were most worthwhile to pursue further. One interviewee emphasised that the AI-generated metadata functioned as an eyeopener and a shortcut to sources and information.</p>
<p>The searchers from product safety primarily conducted specific, known-item searches and described well-established practices of enriching key documents with tailored titles and metadata to ensure their retrieval. They did not immediately perceive that the new metadata held value in relation to their search tasks. However, upon exploring the AI-generated metadata, they recognised opportunities for broader application but emphasised that this would necessitate the adoption of new search routines.</p>
<p>In the searches, metadata emerged that was incorrect or irrelevant. These errors arose for various reasons. For example, the naming of enzymes varies across companies and between corporate and scientific vocabularies. Likewise, enzymes can assume different roles, such as a fundamental organism or an ingredient. Role distinctions also affected the assignment of company name, where a company might be a partner, supplier, or competitor. These errors primarily caused frustration for the searcher, but they also gave rise to scepticism and doubt regarding the accuracy and reliability of the information. This dissatisfaction and mistrust constitute a well-documented challenge in enterprise search and, regrettably, are not resolved through the application of the AI algorithm in question (<xref ref-type="bibr" rid="R8">Cleverley &#x0026; Burnett, 2019</xref>; <xref ref-type="bibr" rid="R9">Cleverley et al., 2017</xref>).</p>
<p>The information searchers emphasised that AI-generated metadata is not a plug-and-play solution. In several searches, they expressed a need for more guidance on how to concretely utilise the metadata and information in their search processes. Fully understanding the metadata and how it could be applied required both domain-specific knowledge and search experience. While AI-generated metadata provides valuable new insights, it does not replace the essential search expertise that an information searcher must possess in enterprise search. It offers a useful new framework for information retrieval, but it does not resolve classical search challenges, such as dealing with diverse and dynamic vocabularies, query formulation, or incorrect metadata assignment (<xref ref-type="bibr" rid="R15">Furnas et al., 1987</xref>; <xref ref-type="bibr" rid="R32">Nielsen, 2005</xref>; <xref ref-type="bibr" rid="R37">Schuff et al., 2016</xref>; <xref ref-type="bibr" rid="R39">Stocker et al., 2015</xref>).</p>
<p>The study demonstrated that the participants were experienced searchers with a solid understanding of search algorithms. They approached the AI metadata in an interactive, explorative and critical manner, relating it to search tasks and prior search experience. They consciously assessed whether the metadata provided new knowledge or support and pointed out relevant problems.</p>
<p>When comparing the interviewees&#x2019; behaviour with the four AI competencies proposed by <xref ref-type="bibr" rid="R30">Ng et al. (2021</xref>, <xref ref-type="bibr" rid="R31">2024</xref>), the participants demonstrated the ability to understand, apply, and evaluate AI metadata by drawing upon their existing search knowledge. In their assessment of AI-generated metadata, they relied on their general understanding of computer-based processes. This was reflected, for example, when they expressed understanding of the AI algorithm&#x2019;s difficulty in distinguishing, for instance, between roles and variations in names. While no interviewees explicitly addressed ethical issues, they implicitly touched on them, by emphasising the importance of domain knowledge and the limitations novices might face when using AI metadata without sufficient contextual understanding.</p>
<p>Similarly, Pinski and Benlian&#x2019;s (2023) distinction of AI actor knowledge, AI process knowledge, and AI experience is reflected in the findings. Although we did not directly assess participants&#x2019; AI knowledge, the study shows that searchers relied on practical experience to understand and apply AI metadata. They were aware of limitations related to domain-specific nuances that algorithms cannot fully capture. While incorrect metadata assignments were perceived as annoying and sometimes triggered mistrust, the participants&#x2019; search experience enabled them to manage such issues in practice. It may be argued that they transferred prior experience and existing knowledge of search algorithms to these new AI-based affordances, thereby using prior search experience to develop knowledge of and experience with AI. The fact that the information searchers possessed substantial prior search knowledge meant that they had the capacity to engage in the interaction with AI metadata and the associated information necessary to utilise the new AI-based knowledge to reformulate and improve their searches iteratively. This required the cognitive resources to recognise how different variations in names, as well as knowledge of roles, could be actively employed to identify relevant prior studies concerning a given enzyme.</p>
<p>Overall, the findings indicate that users with extensive search experience and deep domain knowledge were able to use AI-based search systems with the critical approach emphasised by Fountaine et al. (2019). Furthermore, this meant that, on the basis of their existing knowledge, they were able to develop experience with the new AI-based tool, which, in turn, enabled the development of AI literacy.</p>
</sec>
<sec id="sec7_2">
<title>Ensuring AI use and literacy</title>
<p>Interview participants emphasised the necessity of domain knowledge for their understanding and use of AI-generated metadata, noting that such engagement presupposes prior knowledge. Their reflections centre on the individual user, highlighting that metadata and its associated information may be utilised in markedly different ways, depending on users&#x2019; personal knowledge and experience.</p>
<p>Extending this line of argument, they further addressed the challenge at an organisational level by proposing functions or tools to support users with domain-specific knowledge. For example, they suggested that non-descriptive identification numbers should be enriched with the full titles and names of the enzymes to which such identifiers refer. In addition, they proposed that the interface should be augmented with explanations and guidance on how the data and information from a given source may be used in search processes. In this sense, the interface ought to be enriched both with contextual knowledge and with search knowledge, indicating how such contextual knowledge may be applied in practice.</p>
<p>Thus, at the organisational level, the study highlights the importance of introducing AI-based systems as tools that require critical use and contextual domain knowledge. Furthermore, the interview participants&#x2019; suggestions indicate that this knowledge and support should be communicated in multiple forms. Cultures and information-related work practices can be supported through intangible resources, such as inter-departmental coordination, organisational change capacity, and risk proclivity. These resources may enable critical sense-making, the emergence of new information routines, and adaptive practices within the organisation (Mikalef &#x0026; Gupta, 2021). Continuous and effective interaction with search tools can be further facilitated through human resource initiatives that emphasise the ongoing development of advanced search skills, as well as an increased awareness of the importance of domain knowledge in information searching processes. This may be achieved through introductions and training programmes. The questionnaire&#x2019;s introductory video illustrated how tangible organisational resources (specifically short and easily accessible instructional materials) can support the development of AI literacy and contribute to the adoption and routinization of AI-based systems.</p>
<p>In the interview with the information specialist, they emphasised that the selection of the twelve metadata types was based partly on user studies of search behaviour and on what the company&#x2019;s information specialists, on that basis, assessed to constitute important and relevant contextual knowledge, and partly on what was practically feasible to implement. This entailed, inter alia, that person-related metadata linking individuals to, for example, R&#x0026;D activities, laboratory tests, and projects were not included. None of the interview participants commented on the absence of particular metadata types, nor were any missing metadata types identified in the questionnaire. Since users have not been interactively involved in the development of the AI-based search tool, an important organisational initiative would be to involve users in a future design process, both with regard to the selection of metadata types and the determination of forms of domain and search knowledge to be communicated and incorporated into the interface design, as well as the manner of such communication. For instance, it may be considered whether video-based introductions with illustrative examples are useful, or whether communication should adopt a more dialogic form, for example, drawing on chat-based technologies.</p>
<p>Overall, the study has demonstrated that AI-generated metadata and access to domain-specific information from a broad range of sources are useful. The study further shows that such metadata and associated information transform and, in certain respects, improve the conditions for information retrieval, but that their effective utilisation nonetheless continues to require both domain knowledge and search expertise. There remains a need to develop a range of functionalities and tools that can support information searchers in transferring and developing their prior domain and search knowledge into AI literacy. This development should take place at both the individual and organisational levels.</p>
</sec>
</sec>
<sec id="sec8">
<title>Study limitations</title>
<p>The present study constitutes a case analysis of an international biotechnology company, drawing upon semi-structured interviews with the corporate information specialist responsible for the development of the AI tool under investigation, a questionnaire study with seventy searchers for whom the tool was developed, and nine semi-structured interviews, including demonstrations of two to three searches conducted using the AI tool by searchers with prior experience of it. The AI tool had only been implemented for one month; consequently, users&#x2019; experience with the tool was limited. The sampling of interview participants was discontinued at the point at which no further novel insights emerged.</p>
<p>Overall, the study has limited generalisability; however, it provides new and valuable insight into how a group of highly experienced information searchers, possessing substantial domain and search expertise, interpret and utilise highly specific, contextual metadata and information to expand and reformulate their queries in pursuit of information that is at once precise yet previously unknown. The findings may be considered in relation to similar contexts, in which experienced information searchers are introduced to and interact with new search technologies. Future research should, therefore, seek to examine this particular user group in greater depth and across comparable contexts.</p>
</sec>
<sec id="sec9">
<title>Conclusion</title>
<p>The aim of this study was to investigate how workplace searchers understood and used an AI-based search tool consisting of domain-specific metadata assigned to retrieved documents. Users&#x2019; assessments and interactions with the tool were examined through interviews with search demonstrations and a questionnaire survey conducted as part of a case study in an international biotechnology company.</p>
<p>The informants found the twelve AI metadata types useful for both exploratory search and specific searches for known information. In terms of user&#x2013;system interaction, the tool was generally perceived as easy-to-use. However, users also encountered irrelevant and incorrect information, which they found annoying but understandable given the complexity of domainspecific relationships. Several challenges were identified: domain and search knowledge were a prerequisite for effective use; the use of metadata in search was not always readily apparent; there was a need for improved communication of what metadata represent and how they are utilised in search; and new routines were required within established search practices.</p>
<p>During search activities, the interviewees demonstrated the four AI competencies identified by <xref ref-type="bibr" rid="R30">Ng et al. (2021)</xref>, drawing on existing search experience and understanding of search algorithms, including AI. They were able to understand, apply, and evaluate the AI metadata critically, identify problems, and suggest improvements. The study underscores that users with extensive search experience and deep domain knowledge can use AI-based search systems with the necessary critical approach. Moreover, effective use requires an open-minded, explorative attitude and a willingness to continuously interact with the system to achieve accurate and relevant search results.</p>
<p>The development of AI-related competences can be facilitated through the strategic alignment of tangible, intangible, and human resources, encompassing instructional materials, interdepartmental coordination and organisational change capacity, as well as the ongoing cultivation of advanced search skills and domain-specific knowledge in information-seeking practices.</p>
<p>The insight into how experienced corporate users adopt a novel AI-based search tool&#x2014;by drawing upon their existing search expertise and substantial domain knowledge, while concurrently extending their overall information-searching literacy to encompass AI-based search technologies&#x2014;constitutes the principal contribution of the study. The study further provides important insights and practical implications regarding how experienced searchers may be supported, for example, through video-based introductions, explanatory features, and potentially chat-based dialogue integrated within the search interface.</p>
</sec>
</body>
<back>
<ack>
<title>Acknowledgements</title>
<p>The authors would like to thank the company for the generous opportunity to conduct this research and the participants for their engagement and valuable insights on this topic. The authors would also like to thank the anonymous reviewers for their very helpful suggestions in developing the paper further.</p>
</ack>
<ref-list>
<title>References</title>
<ref id="R1"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Allard</surname><given-names>S.</given-names></name><name><surname>Levine</surname><given-names>K. J.</given-names></name><name><surname>Tenopir</surname><given-names>C.</given-names></name></person-group><year>2009</year><article-title>Design engineers and technical professionals at work: Observing information usage in the workplace</article-title><source>Journal of the American Society for Information Science and Technology</source><volume>60</volume><issue>3</issue><fpage>443</fpage><lpage>454</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1002/asi.21004">https://doi.org/10.1002/asi.21004</ext-link></comment></element-citation></ref>
<ref id="R2"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Asula</surname><given-names>M.</given-names></name><name><surname>Makke</surname><given-names>J.</given-names></name><name><surname>Freienthal</surname><given-names>L.</given-names></name><name><surname>Kuulmets</surname><given-names>H.-A.</given-names></name><name><surname>Sirel</surname><given-names>R.</given-names></name></person-group><year>2021</year><article-title>Kratt: Developing an automatic subject indexing tool for the National Library of Estonia</article-title><source>Cataloging &amp; Classification Quarterly</source><volume>59</volume><issue>8</issue><fpage>775</fpage><lpage>793</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/01639374.2021.1998283">https://doi.org/10.1080/01639374.2021.1998283</ext-link></comment></element-citation></ref>
<ref id="R3"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Bloom</surname><given-names>B. S.</given-names></name></person-group><year>1956</year><source>Taxonomy of educational objectives: The classification of educational goals</source><publisher-name>D. McKay</publisher-name></element-citation></ref>
<ref id="R4"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Cetindamar</surname><given-names>D.</given-names></name><name><surname>Kitto</surname><given-names>K.</given-names></name><name><surname>Wu</surname><given-names>M.</given-names></name><name><surname>Zhang</surname><given-names>Y.</given-names></name><name><surname>Abedin</surname><given-names>B.</given-names></name><name><surname>Knight</surname><given-names>S.</given-names></name></person-group><year>2024</year><article-title>Explicating AI literacy of employees at digital workplaces</article-title><source>IEEE Transactions on Engineering Management</source><volume>71</volume><fpage>810823</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/TEM.2021.3138503">https://doi.org/10.1109/TEM.2021.3138503</ext-link></comment></element-citation></ref>
<ref id="R5"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname><given-names>R.-C.</given-names></name><name><surname>Dewi</surname><given-names>C.</given-names></name><name><surname>Huang</surname><given-names>S.-W.</given-names></name><name><surname>Caraka</surname><given-names>R. E.</given-names></name></person-group><year>2020</year><article-title>Selecting critical features for data classification based on machine learning methods</article-title><source>Journal of Big Data</source><volume>7</volume><issue>1</issue><fpage>52</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1186/s40537-020-00327-4">https://doi.org/10.1186/s40537-020-00327-4</ext-link></comment></element-citation></ref>
<ref id="R6"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Chen</surname><given-names>S.</given-names></name><name><surname>Li</surname><given-names>M.</given-names></name></person-group><year>2024</year><article-title>AI for cataloging and metadata creation: Perspectives and future opportunities from cataloging and metadata professionals</article-title><source>Technical Services Quarterly</source><volume>41</volume><issue>4</issue><fpage>317</fpage><lpage>332</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/07317131.2024.2394919">https://doi.org/10.1080/07317131.2024.2394919</ext-link></comment></element-citation></ref>
<ref id="R7"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Cleverley</surname><given-names>P. H.</given-names></name><name><surname>Burnett</surname><given-names>S.</given-names></name></person-group><year>2015</year><article-title>Retrieving haystacks: A data driven information needs model for faceted search</article-title><source>Journal of Information Science</source><volume>41</volume><issue>1</issue><fpage>97</fpage><lpage>113</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1177/0165551514554522">https://doi.org/10.1177/0165551514554522</ext-link></comment></element-citation></ref>
<ref id="R8"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Cleverley</surname><given-names>P. H.</given-names></name><name><surname>Burnett</surname><given-names>S.</given-names></name></person-group><year>2019</year><article-title>Enterprise search and discovery capability: The factors and generative mechanisms for user satisfaction</article-title><source>Journal of Information Science</source><volume>45</volume><issue>1</issue><fpage>29</fpage><lpage>52</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1177/0165551518770969">https://doi.org/10.1177/0165551518770969</ext-link></comment></element-citation></ref>
<ref id="R9"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Cleverley</surname><given-names>P. H.</given-names></name><name><surname>Burnett</surname><given-names>S.</given-names></name><name><surname>Muir</surname><given-names>L.</given-names></name></person-group><year>2017</year><article-title>Exploratory information searching in the enterprise: A study of user satisfaction and task performance</article-title><source>Journal of the Association for Information Science and Technology</source><volume>68</volume><issue>1</issue><fpage>77</fpage><lpage>96</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1002/asi.23595">https://doi.org/10.1002/asi.23595</ext-link></comment></element-citation></ref>
<ref id="R10"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Corrado</surname><given-names>E. M.</given-names></name></person-group><year>2021</year><article-title>Artificial intelligence: The possibilities for metadata creation</article-title><source>Technical Services Quarterly</source><volume>38</volume><issue>4</issue><fpage>395</fpage><lpage>405</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/07317131.2021.1973797">https://doi.org/10.1080/07317131.2021.1973797</ext-link></comment></element-citation></ref>
<ref id="R11"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Domke</surname><given-names>E. M.</given-names></name><name><surname>Leidig</surname><given-names>J. P.</given-names></name><name><surname>Schymik</surname><given-names>G.</given-names></name><name><surname>Wolffe</surname><given-names>G.</given-names></name></person-group><year>2018</year><article-title>Query expansion in enterprise search</article-title><source>DocEng &#x2019;18: Proceedings of the ACM Symposium on Document Engineering 2018</source><comment>(article 33). <ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1145/3209280.3229111">https://doi.org/10.1145/3209280.3229111</ext-link></comment></element-citation></ref>
<ref id="R12"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Elliott</surname><given-names>A.</given-names></name></person-group><year>2019</year><source>The culture of AI: Everyday life and the digital revolution</source><publisher-name>Routledge</publisher-name><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.4324/9781315387185">https://doi.org/10.4324/9781315387185</ext-link></comment></element-citation></ref>
<ref id="R13"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Fagin</surname><given-names>R.</given-names></name><name><surname>Kumar</surname><given-names>R.</given-names></name><name><surname>McCurley</surname><given-names>K. S.</given-names></name><name><surname>Novak</surname><given-names>J.</given-names></name><name><surname>Sivakumar</surname><given-names>D.</given-names></name><name><surname>Tomlin</surname><given-names>J. A.</given-names></name><name><surname>Williamson</surname><given-names>D. P.</given-names></name></person-group><year>2003</year><article-title>Searching the workplace Web</article-title><source>WWW&#x2019;03: Proceedings of the 12th International Conference on World Wide Web</source><fpage>366</fpage><lpage>375</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1145/775152.775204">https://doi.org/10.1145/775152.775204</ext-link></comment></element-citation></ref>
<ref id="R14"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Freund</surname><given-names>L.</given-names></name></person-group><year>2015</year><article-title>Contextualizing the information-seeking behavior of software engineers</article-title><source>Journal of the Association for Information Science and Technology</source><volume>66</volume><issue>8</issue><fpage>1594</fpage><lpage>1605</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1002/asi.23278">https://doi.org/10.1002/asi.23278</ext-link></comment></element-citation></ref>
<ref id="R15"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Furnas</surname><given-names>G. W.</given-names></name><name><surname>Landauer</surname><given-names>T. K.</given-names></name><name><surname>Gomez</surname><given-names>L. M.</given-names></name><name><surname>Dumais</surname><given-names>S. T.</given-names></name></person-group><year>1987</year><article-title>The vocabulary problem in human-system communication</article-title><source>Communications of the ACM</source><volume>30</volume><issue>11</issue><fpage>964</fpage><lpage>971</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1145/32206.32212">https://doi.org/10.1145/32206.32212</ext-link></comment></element-citation></ref>
<ref id="R16"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Given</surname><given-names>L. M.</given-names></name><name><surname>Case</surname><given-names>D. O.</given-names></name><name><surname>Willson</surname><given-names>R.</given-names></name></person-group><year>2023</year><source>Looking for information: Examining research on how people engage with information</source><publisher-name>Emerald Group Publishing</publisher-name></element-citation></ref>
<ref id="R17"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Golub</surname><given-names>K.</given-names></name></person-group><year>2021</year><article-title>Automated subject indexing: An overview</article-title><source>Cataloging &amp; Classification Quarterly</source><volume>59</volume><issue>8</issue><fpage>702</fpage><lpage>719</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/01639374.2021.2012311">https://doi.org/10.1080/01639374.2021.2012311</ext-link></comment></element-citation></ref>
<ref id="R18"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Gunadi</surname><given-names>E.</given-names></name><name><surname>Albayrak</surname><given-names>S.</given-names></name></person-group><year>2015</year><article-title>Information aggregation in an enterprise</article-title><person-group person-group-type="editor"><name><surname>Hopfgartner</surname><given-names>F.</given-names></name></person-group><source>Smart information systems: Computational intelligence for real-life applications</source><fpage>99</fpage><lpage>122</lpage><publisher-name>Springer International Publishing</publisher-name><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1007/978-3-319-14178-7_4">https://doi.org/10.1007/978-3-319-14178-7_4</ext-link></comment></element-citation></ref>
<ref id="R19"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Jha</surname><given-names>S. K.</given-names></name></person-group><year>2023</year><article-title>Application of artificial intelligence in libraries and information centers services: Prospects and challenges</article-title><source>Library Hi Tech News</source><volume>40</volume><issue>7</issue><fpage>1</fpage><lpage>5</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1108/LHTN-06-2023-0102">https://doi.org/10.1108/LHTN-06-2023-0102</ext-link></comment></element-citation></ref>
<ref id="R20"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kadhim</surname><given-names>A. I.</given-names></name></person-group><year>2019</year><article-title>Survey on supervised machine learning techniques for automatic text classification</article-title><source>Artificial Intelligence Review</source><volume>52</volume><issue>1</issue><fpage>273</fpage><lpage>292</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1007/s10462-018-09677-1">https://doi.org/10.1007/s10462-018-09677-1</ext-link></comment></element-citation></ref>
<ref id="R21"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kandepu</surname><given-names>R. K.</given-names></name><name><surname>Harry</surname><given-names>A.</given-names></name></person-group><year>2023</year><article-title>The rise of AI in content management: Reimagining intelligent workflows</article-title><source>American Journal of Engineering, Mechanics and Architecture</source><volume>1</volume><issue>7</issue><fpage>78</fpage><lpage>85</lpage></element-citation></ref>
<ref id="R22"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Kruschwitz</surname><given-names>U.</given-names></name><name><surname>Hull</surname><given-names>C.</given-names></name></person-group><year>2017</year><article-title>Searching the enterprise</article-title><source>Foundations and Trends in Information Retrieval</source><volume>11</volume><issue>1</issue><fpage>1</fpage><lpage>142</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1561/1500000053">https://doi.org/10.1561/1500000053</ext-link></comment></element-citation></ref>
<ref id="R23"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Long</surname><given-names>D.</given-names></name><name><surname>Magerko</surname><given-names>B.</given-names></name></person-group><year>2020</year><article-title>What is AI literacy? Competencies and design considerations</article-title><source>CHI&#x2019;20: Proceedings of the 2020 CHI Conference on Human Factors in Computing Systems</source><fpage>1</fpage><lpage>16</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1145/3313831.3376727">https://doi.org/10.1145/3313831.3376727</ext-link></comment></element-citation></ref>
<ref id="R24"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Lowe</surname><given-names>D. B.</given-names></name><name><surname>Dollinger</surname><given-names>I.</given-names></name><name><surname>Koster</surname><given-names>T.</given-names></name><name><surname>Herbert</surname><given-names>B. E.</given-names></name></person-group><year>2021</year><article-title>Text mining for type of research classification</article-title><source>Cataloging &amp; Classification Quarterly</source><volume>59</volume><issue>8</issue><fpage>815</fpage><lpage>834</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/01639374.2021.1998281">https://doi.org/10.1080/01639374.2021.1998281</ext-link></comment></element-citation></ref>
<ref id="R25"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Lykke</surname><given-names>M.</given-names></name><name><surname>Bygholm</surname><given-names>A. K. M.</given-names></name><name><surname>S&#x00F8;ndergaard</surname><given-names>L. B.</given-names></name><name><surname>Bystr&#x00F6;m</surname><given-names>K.</given-names></name></person-group><year>2022</year><article-title>The role of historical and contextual knowledge in enterprise search</article-title><source>Journal of Documentation</source><volume>78</volume><issue>5</issue><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1108/JD-08-2021-0170">https://doi.org/10.1108/JD-08-2021-0170</ext-link></comment></element-citation></ref>
<ref id="R26"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Marques</surname><given-names>A.</given-names></name><name><surname>Murphy</surname><given-names>G. C.</given-names></name></person-group><year>2022</year><article-title>Evaluating the use of semantics for identifying task-relevant textual information</article-title><source>2022 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)</source><fpage>240</fpage><lpage>251</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1109/SANER53432.2022.00039">https://doi.org/10.1109/SANER53432.2022.00039</ext-link></comment></element-citation></ref>
<ref id="R27"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mathieu</surname><given-names>C.</given-names></name></person-group><year>2022</year><article-title>Defining knowledge workers&#x2019; creation, description, and storage practices as impact on enterprise content management strategy</article-title><source>Journal of the Association for Information Science and Technology</source><volume>73</volume><issue>3</issue><fpage>472</fpage><lpage>484</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1002/asi.24563">https://doi.org/10.1002/asi.24563</ext-link></comment></element-citation></ref>
<ref id="R28"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Moulaison-Sandy</surname><given-names>H.</given-names></name><name><surname>Adkins</surname><given-names>D.</given-names></name><name><surname>Bossaller</surname><given-names>J.</given-names></name><name><surname>Cho</surname><given-names>H.</given-names></name></person-group><year>2021</year><article-title>An automated approach to describing fiction: A methodology to use book reviews to identify affect</article-title><source>Cataloging &amp; Classification Quarterly</source><volume>59</volume><issue>8</issue><fpage>794</fpage><lpage>814</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/01639374.2021.1992694">https://doi.org/10.1080/01639374.2021.1992694</ext-link></comment></element-citation></ref>
<ref id="R29"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Mwantimwa</surname><given-names>K.</given-names></name><name><surname>Msoffe</surname><given-names>G.</given-names></name></person-group><year>2025</year><article-title>Application of generative artificial intelligence in library operations and service delivery: A scoping review</article-title><source>Technical Services Quarterly</source><volume>42</volume><issue>2</issue><fpage>139168</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/07317131.2025.2467574">https://doi.org/10.1080/07317131.2025.2467574</ext-link></comment></element-citation></ref>
<ref id="R30"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Ng</surname><given-names>D. T. K.</given-names></name><name><surname>Leung</surname><given-names>J. K. L.</given-names></name><name><surname>Chu</surname><given-names>S. K. W.</given-names></name><name><surname>Qiao</surname><given-names>M. S.</given-names></name></person-group><year>2021</year><article-title>Conceptualizing AI literacy: An exploratory review</article-title><source>Computers and Education: Artificial Intelligence</source><volume>2</volume><fpage>100041</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/j.caeai.2021.100041">https://doi.org/10.1016/j.caeai.2021.100041</ext-link></comment></element-citation></ref>
<ref id="R31"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Ng</surname><given-names>D. T. K.</given-names></name><name><surname>Wu</surname><given-names>W.</given-names></name><name><surname>Leung</surname><given-names>J. K. L.</given-names></name><name><surname>Chiu</surname><given-names>T. K. F.</given-names></name><name><surname>Chu</surname><given-names>S. K. W.</given-names></name></person-group><year>2024</year><article-title>Design and validation of the AI literacy questionnaire: The affective, behavioural, cognitive and ethical approach</article-title><source>British Journal of Educational Technology</source><volume>55</volume><issue>3</issue><fpage>1082</fpage><lpage>1104</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1111/bjet.13411">https://doi.org/10.1111/bjet.13411</ext-link></comment></element-citation></ref>
<ref id="R32"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Nielsen</surname><given-names>M. L.</given-names></name></person-group><year>2005</year><article-title>Special libraries and specialized vocabularies in the digital age. In:</article-title><source>Encyclopedia of library and information science</source><publisher-name>Dekker</publisher-name></element-citation></ref>
<ref id="R33"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Oyighan</surname><given-names>D.</given-names></name><name><surname>Ukubeyinje</surname><given-names>E. S.</given-names></name><name><surname>David -West</surname><given-names>B. T.</given-names></name><name><surname>Oladokun</surname><given-names>B. D.</given-names></name></person-group><year>2024</year><article-title>The role of AI in transforming metadata management: Insights on challenges, opportunities, and emerging trends</article-title><source>Asian Journal of Information Science and Technology</source><volume>14</volume><issue>2</issue><fpage>20</fpage><lpage>26</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.70112/ajist-2024.14.2.4277">https://doi.org/10.70112/ajist-2024.14.2.4277</ext-link></comment></element-citation></ref>
<ref id="R34"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Pinar</surname><given-names>A.</given-names></name><name><surname>Cox</surname><given-names>A.</given-names></name></person-group><year>2025</year><article-title>An analysis of artificial intelligence (AI) capability in libraries and archives</article-title><source>Cataloging &amp; Classification Quarterly</source><volume>63</volume><issue>6-7</issue><fpage>566</fpage><lpage>599</lpage><comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1080/01639374.2025.2539790">https://doi.org/10.1080/01639374.2025.2539790</ext-link></comment></element-citation></ref>
<ref id="R35"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Russell-Rose</surname><given-names>T.</given-names></name><name><surname>Chamberlain</surname><given-names>J.</given-names></name><name><surname>Azzopardi</surname><given-names>L.</given-names></name></person-group><year>2018</year><article-title>Information retrieval in the workplace: A comparison of professional search practices</article-title><source>Information Processing &amp; Management</source><volume>54</volume><issue>6</issue><fpage>1042</fpage><lpage>1057</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1016/j.ipm.2018.07.003">https://doi.org/10.1016/j.ipm.2018.07.003</ext-link></comment></element-citation></ref>
<ref id="R36"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Samuel</surname><given-names>J.</given-names></name><name><surname>Ali</surname><given-names>G. G. M. N.</given-names></name><name><surname>Rahman</surname><given-names>M. M.</given-names></name><name><surname>Esawi</surname><given-names>E.</given-names></name><name><surname>Samuel</surname><given-names>Y.</given-names></name></person-group><year>2020</year><article-title>COVID-19 public sentiment insights and machine learning for tweets classification</article-title><source>Information</source><volume>11</volume><issue>6</issue><fpage>paper314</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.3390/info11060314">https://doi.org/10.3390/info11060314</ext-link></comment></element-citation></ref>
<ref id="R37"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Schuff</surname><given-names>D.</given-names></name><name><surname>Louis</surname><given-names>R. S.</given-names></name><name><surname>Corral</surname><given-names>K.</given-names></name><name><surname>Schymik</surname><given-names>G.</given-names></name></person-group><year>2016</year><article-title>Word ambiguity and search: Implications for enterprise performance management</article-title><source>The Americas Conference on Information Systems (AMCIS) 2016 Proceedings</source><comment><ext-link ext-link-type="uri" xlink:href="https://web.archive.org/web/20200320101152id/https://aisel.aisnet.org/cgi/viewcontent.cgi?referer=&amp;httpsredir=1&amp;article=1075&amp;context=amcis2016">https://web.archive.org/web/20200320101152id/https://aisel.aisnet.org/cgi/viewcontent.cgi?referer=&amp;httpsredir=1&amp;article=1075&amp;context=amcis2016</ext-link></comment></element-citation></ref>
<ref id="R38"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Schymik</surname><given-names>G.</given-names></name><name><surname>Corral</surname><given-names>K.</given-names></name><name><surname>Schuff</surname><given-names>D.</given-names></name><name><surname>St. Louis</surname><given-names>R</given-names></name></person-group><year>2015</year><article-title>The benefits and costs of using metadata to improve enterprise document search</article-title><source>Decision Sciences</source><volume>46</volume><issue>6</issue><fpage>1049</fpage><lpage>1075</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1111/deci.12154">https://doi.org/10.1111/deci.12154</ext-link></comment></element-citation></ref>
<ref id="R39"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Stocker</surname><given-names>A.</given-names></name><name><surname>Richter</surname><given-names>A.</given-names></name><name><surname>Kaiser</surname><given-names>C.</given-names></name><name><surname>Softic</surname><given-names>S.</given-names></name></person-group><year>2015</year><article-title>Exploring barriers of enterprise search implementation: A qualitative user study</article-title><source>Aslib Journal of Information Management</source><volume>67</volume><issue>5</issue><fpage>470</fpage><lpage>491</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1108/AJIM-03-2015-0035">https://doi.org/10.1108/AJIM-03-2015-0035</ext-link></comment></element-citation></ref>
<ref id="R40"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Svarre</surname><given-names>T.</given-names></name><name><surname>Lykke</surname><given-names>M.</given-names></name><name><surname>Bygholm</surname><given-names>A. K. M.</given-names></name></person-group><year>2024</year><article-title>Searching for people in the workplace: Aims, behaviour, and challenges</article-title><source>Information Research: an International Electronic Journal</source><volume>29</volume><issue>2</issue><comment>Article 2</comment><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.47989/ir292848">https://doi.org/10.47989/ir292848</ext-link></comment></element-citation></ref>
<ref id="R41"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Thangaraj</surname><given-names>M.</given-names></name><name><surname>Sivakami</surname><given-names>M.</given-names></name></person-group><year>2018</year><article-title>Text classification techniques: A literature review</article-title><source>Interdisciplinary Journal of Information, Knowledge, and Management</source><volume>13</volume><fpage>117</fpage><lpage>135</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.28945/4066">https://doi.org/10.28945/4066</ext-link></comment></element-citation></ref>
<ref id="R42"><element-citation publication-type="book"><person-group person-group-type="author"><name><surname>Togia</surname><given-names>A.</given-names></name><name><surname>Tsigilis</surname><given-names>N.</given-names></name><name><surname>Koseoglou</surname><given-names>E.</given-names></name></person-group><year>2026</year><article-title>Artificial intelligence in Greek libraries: Perceptions, challenges, and readiness for adoption</article-title><source>Journal of Librarianship and Information Science</source><publisher-name>online first</publisher-name><comment><ext-link ext-link-type="uri" xlink:href="https://doi.org/10.1177/09610006251410240">https://doi.org/10.1177/09610006251410240</ext-link></comment></element-citation></ref>
<ref id="R43"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Townsend</surname><given-names>R.</given-names></name><name><surname>Mathieu</surname><given-names>C.</given-names></name></person-group><year>2018</year><article-title>Improving enterprise content findability through strategic intervention</article-title><source>The Code4Lib Journal</source><fpage>42</fpage></element-citation></ref>
<ref id="R44"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Vrindha</surname><given-names>K.</given-names></name><name><surname>Syamili</surname><given-names>C.</given-names></name></person-group><year>2025</year><article-title>Navigating the AI landscape in libraries: A PRISMA-based systematic analysis of AI applications in libraries</article-title><source>Journal of Web Librarianship</source><volume>19</volume><issue>1</issue><fpage>45</fpage><lpage>61</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1080/19322909.2025.2468697">https://doi.org/10.1080/19322909.2025.2468697</ext-link></comment></element-citation></ref>
<ref id="R45"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>White</surname><given-names>M. S.</given-names></name></person-group><year>2020</year><article-title>Information flows &#x2013; or does it? The complexity of enterprise information management</article-title><source>Business Information Review</source><volume>37</volume><issue>3</issue><fpage>103</fpage><lpage>110</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1177/0266382120950114">https://doi.org/10.1177/0266382120950114</ext-link></comment></element-citation></ref>
<ref id="R46"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Wu</surname><given-names>M.</given-names></name><name><surname>Brandhorst</surname><given-names>H.</given-names></name><name><surname>Marinescu</surname><given-names>M.-C.</given-names></name><name><surname>Lopez</surname><given-names>J.</given-names></name><name><surname>Hlava</surname><given-names>M.</given-names></name><name><surname>Busch</surname><given-names>J.</given-names></name></person-group><year>2025</year><article-title>Automated metadata annotation: What is and is not possible with machine learning</article-title><source>Data Intelligence</source><volume>5</volume><issue>1</issue><fpage>122</fpage><lpage>138</lpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1162/dint_a_00162">https://doi.org/10.1162/dint_a_00162</ext-link></comment></element-citation></ref>
<ref id="R47"><element-citation publication-type="journal"><person-group person-group-type="author"><name><surname>Yang</surname><given-names>H.</given-names></name><name><surname>Wang</surname><given-names>N.</given-names></name><name><surname>Yang</surname><given-names>L.</given-names></name><name><surname>Liu</surname><given-names>W.</given-names></name><name><surname>Wang</surname><given-names>S.</given-names></name></person-group><year>2023</year><article-title>Research on the automatic subject-Indexing method of academic papers based on climate change domain ontology</article-title><source>Sustainability</source><volume>15</volume><issue>5</issue><fpage>3919</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.3390/su15053919">https://doi.org/10.3390/su15053919</ext-link></comment></element-citation></ref>
<ref id="R48"><element-citation publication-type="web"><person-group person-group-type="author"><name><surname>Zhou</surname><given-names>D. X.</given-names></name><name><surname>Liu</surname><given-names>L.</given-names></name><name><surname>Anubhai</surname><given-names>A.</given-names></name><name><surname>Shandilya</surname><given-names>M.</given-names></name><name><surname>Sigalas</surname><given-names>S.</given-names></name><name><surname>Wang</surname><given-names>W. Y.</given-names></name><name><surname>Huang</surname><given-names>Z.</given-names></name></person-group><year>2023</year><article-title>Beyond accurate answers: Evaluating open-domain question answering in enterprise search</article-title><source>Proceedings of the 2023 Conference on Human Information Interaction and Retrieval</source><fpage>308312</fpage><comment><ext-link ext-link-type="doi" xlink:href="https://doi.org/10.1145/3576840.3578314">https://doi.org/10.1145/3576840.3578314</ext-link></comment></element-citation></ref>
</ref-list>
</back>
</article>