<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Training on the Job: Learning While Searching in an Engineering Workplace</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Dirk Ahlers</string-name>
          <email>dirk.ahlers@idi.ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Mahsa Mehrpoor</string-name>
          <email>mahsa.mehrpoor@ntnu.no</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>CCS Concepts</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>NTNU - Norwegian University of Science and Technology Trondheim</institution>
          ,
          <country country="NO">Norway</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>Professional search in an engineering context includes users on di erent stages from novice to expert. We discuss how searching as learning can help to understand searching in a larger information seeking, workspace, and learning environment, giving users the tools and understanding to become experts over time. We present some ndings of user interaction with engineering domain retrieval systems where the searching as learning perspective can improve our understanding of information seeking behaviour.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. INTRODUCTION</title>
      <p>In a number of professional search settings the goal is
not only to retrieve a particular isolated fact or document,
but also to satisfy more complex information needs as part
of a surrounding work task. In an inherently
knowledgedriven work environment, searching for and working with
documents is a common task that is considered especially
challenging for new personnel in a team or company due to
an often steep learning curve.</p>
      <p>
        In our ongoing work, we examine the use of search,
recommendation, and knowledge management tools to support
engineers [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ] in information seeking tasks in their daily work
[
        <xref ref-type="bibr" rid="ref2">2</xref>
        ]. Our users work in larger interdisciplinary teams,
designing and building complex products, with engineers from
many di erent disciplines as well as project managers and
nance, legal, or HR contributors. Due to the large
number of les generated and the preferred way of the teams to
Search as Learning (SAL), July 21, 2016, Pisa, Italy
The copyright for this paper remains with its authors. Copying permitted for private
and academic purposes.
handle les, we focus on an intranet or internal network le
system as a corpus [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ] on top of which we are developing an
expert search system [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ].
2.
      </p>
    </sec>
    <sec id="sec-2">
      <title>WORK, SEARCH, TRAINING</title>
      <p>
        In a specialised professional search system that is a large
part of daily information seeking activities and work tasks,
users gain increasing knowledge and expertise over time by
interacting with the search system. We argue in this
paper that the information seeking tasks of engineers working
on a complex project can be understood from a searching
as learning perspective. This perspective can help
understand the users as it better ts their progress from novice
to expert, both in the short and long term, it may explain
certain changes of information seeking behaviour over time,
and also inform the adaptability of the system. Previous
work has looked at conceptual types of learning as searching
in the workplace [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], here we examine a concrete example.
      </p>
      <p>Learning in this search scenario takes place at at least
two levels. The simpler and more general one is that users
learn how to use the system, especially learning how to
formulate queries to better retrieve relevant documents, how
to judge relevance of results, etc. This is basically
learning how to search and already a well-explored area. Still,
from a research perspective, we are also interested to see
how judgements are made in this context.</p>
      <p>
        On a more speci c case, users learn where to nd
documents, which type or source of document is more useful
for a certain task, and also learn the relevant documents
and processes in their work environment, the unwritten (and
written) rules of the company or the team. Undoubtedly, a
learning e ect occurs when retrieved documents are studied.
Users internalize gained information and knowledge,
changing the information needs they will have from the search
system in the future. This last part is the most interesting
from the searching as learning angle. If we take the de
nitions of learning as a change in the knowledge structures of
a user [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], learning should occur for the engineers on their
way to higher expertise in their job in general and also in
smaller units within a smaller project.
      </p>
      <p>
        The basis for the discussions in this paper are a number
of informal interviews and discussions with engineers from
a large engineering company that builds large-scale o shore
structures [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and others and more formal interviews with a
number of student groups at our university that take part in
a challenge to build an energy-e cient race car from scratch.
In the former case, team sizes range from around 5 to large
international teams of hundreds, in the latter case, there are
Information Needs
Search Process
around 10-15 students per group. We interviewed about 5
engineers and about 20 students. They all come from di
erent disciplines and have di erent backgrounds and di erent
roles in the project.
      </p>
      <p>
        Engineering large complex products or projects is
inherently a collaborative exercise. In the student example,
learning is of course the main desired outcome. Students share
knowledge directly, but also search and read documents from
their own and previous groups as well as general
documentation to advance their knowledge. In the company example
with a large workplace organization, the same happens, and
novices are also guided by expert engineers. However, an
additional task there is expert search, in which users search
for experts in the system to know whom to ask for particular
questions. Information needs also change depending on the
work and project context [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ].
      </p>
      <p>
        Figure 1 shows a simpli ed view of an engineer's work
situation, work tasks, resulting information needs, and possible
engagement with a retrieval system from the view of
information seeking [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Overlayed is the support by certain types
of engineering tools that may integrate some parts of these
layers. So-called Knowledge-based engineering (KBE)
systems allow construction of parameterised solutions to
standard engineering questions [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] and are very knowledge-intensive.
Not presented is the social environment consisting of team
members, hierarchical relations, or expert mentors. This
reects concepts of individual, social, and technical dimensions
of learning activities [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ].
      </p>
      <p>One important thing to note is that there is a lot of
interaction with documents, external Web sources, discussions
with colleagues or project veri cation and reviews that takes
place outside the context of the search system and may be
invisible from that system. From a learning perspective,
information needs even for the exactly same work task may
change over time. Novices need to nd their way around the
system, nd out where documents are stored and how they
are organised, and need to familiarise themselves with the
relevant standards and processes while experts have learned
a lot of these already. On the other hand, there are certain
standards and protocols that need always be followed in the
latest version for speci c parameters or processes. However,
this may still mean that users have bookmarked the latest
source and need not search for it or that they have a physical
printout in the o ce for reference.</p>
      <p>Understanding information seeking tasks with the
searching as learning view helps understand some of our initial
ndings in a new light. For example, an initial idea that
by observing the interaction of experts with a retrieval
system, certain document characteristics and relations as well
as interesting work ow aspects could be mined. This proved
extremely hard, as one of the ndings of our interviews was
that for many tasks, expert searchers use less searching
inside the system. In short, experts use retrieval systems a lot
less and with a di erent focus due to their experience and
expertise. This means that they may not need to use search
to nd the relevant information or that they do know much
more facts and processes and thus do not have any
information need at all. Thus simply observing an expert to train
or support novices turned out to be not feasible.</p>
      <p>
        However, another nding is that engineering experts search
for answers that support more complex or unfamiliar tasks.
Because search tasks often consist of multiple linked searches
for di erent snippets of information, this is inherently
difcult to model. These ndings are consistent with results
from a study of another aspect of engineering support [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
Saved time is not fully assigned to other tasks. Instead, it
is often used for increased breadth and depth of the search
for solutions to harder and more complex problems. This
basically frees up time and resources to rethink existing
solutions or tackle harder issues on higher complexity levels.
3.
      </p>
    </sec>
    <sec id="sec-3">
      <title>CONCLUSION</title>
      <p>
        We see some angles to explore in future work. It would
be interesting to more systematically map previous work [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]
more systematically to deeper explore this context. The
issue of 'good abandonment' where a result page already
covers the information need and no further interaction takes
place is stronger in this scenario as in many cases, we would
not even see the user in the system in the rst place. A
decreased use could also hint towards an advancement of
the user who is well on his learning path. Connected to this
would be a measure of the complexity of the search task
to better support users in their di erent stage of expertise.
This could inform understanding for future retrieval system
design in professional search.
      </p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Ahlers</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Mehrpoor</surname>
          </string-name>
          .
          <article-title>Everything is led under ` le' { conceptual challenges in applying semantic search to network shares for collaborative work</article-title>
          .
          <source>Hypertext '15. ACM</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>D.</given-names>
            <surname>Ahlers</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Mehrpoor</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kristensen</surname>
          </string-name>
          , and
          <string-name>
            <given-names>J.</given-names>
            <surname>Krogstie</surname>
          </string-name>
          .
          <article-title>Challenges for information access in multi-disciplinary product design and engineering settings</article-title>
          .
          <source>In ICDIM. IEEE</source>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>K.</given-names>
            <surname>Bystro</surname>
          </string-name>
          <article-title>m. Searching as a learning activity in real life workplaces</article-title>
          .
          <source>In Searching as Learning Workshop</source>
          ,
          <year>2014</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>L. S.</given-names>
            <surname>Freund</surname>
          </string-name>
          .
          <article-title>Exploiting task-document relations in support of information retrieval in the workplace</article-title>
          .
          <source>PhD thesis</source>
          , University of Toronto,
          <year>2008</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>M.</given-names>
            <surname>Hertzum</surname>
          </string-name>
          and
          <string-name>
            <given-names>A. M.</given-names>
            <surname>Pejtersen</surname>
          </string-name>
          .
          <article-title>The informationseeking practices of engineers: searching for documents as well as for people</article-title>
          .
          <source>Inf</source>
          . Process. Manage.,
          <volume>36</volume>
          (
          <issue>5</issue>
          ),
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>P.</given-names>
            <surname>Ingwersen</surname>
          </string-name>
          and
          <string-name>
            <given-names>K.</given-names>
            <surname>Ja</surname>
          </string-name>
          <article-title>rvelin. The Turn: Integration of Information Seeking and</article-title>
          Retrieval in Context.
          <year>2005</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>G. L.</given-names>
            <surname>Rocca</surname>
          </string-name>
          .
          <article-title>Knowledge based engineering: Between AI and CAD</article-title>
          . Adv. Eng. Inform.,
          <volume>26</volume>
          (
          <issue>2</issue>
          ):
          <volume>159</volume>
          {
          <fpage>179</fpage>
          ,
          <year>2012</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>P.</given-names>
            <surname>Vakkari</surname>
          </string-name>
          .
          <article-title>Searching as learning: A systematization based on literature</article-title>
          .
          <source>J. Inf. Sci.</source>
          ,
          <volume>42</volume>
          (
          <issue>1</issue>
          ):7{
          <fpage>18</fpage>
          ,
          <year>2016</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>