1 2<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 3<html lang="en-us" xmlns="http://www.w3.org/1/xhtml">
4<script type="text/javascript" src="/js/print_setup.js"></script>
vendor: 2 bytes, line 4
4
5<script src="/js/paged.polyfill.js"></script>
5 6 7<!-- HEAD --> 8 <head> 9 <!-- head :: head :: BEG --> 10 <title>Journal of Information Architecture</title> 11 <meta http-equiv="content-type" content="text/html; charset=ISO-885-15" /> 12 <meta name="keywords" content="Journal of Information Architecture, Journal of IA, JofIA, Information Architecture, IA, UX" /> 13 <meta name="description" content="The Journal of Information Architecture is a peer-reviewed scholarly journal. Its aim is to facilitate the systematic development of the scientific body of knowledge in the field of information architecture." /> 14 <meta name="revisit-after" content="7 days" /> 15 <link rel="icon" type="image/svg" href="/art/jofia-logo-IA.svg"/> 16 <link rel="preconnect" href="https://fonts.gstatic.com"> 17 <link href="https://fonts.googleapis.com/css2?family=Cardo:ital,wght@0,400;0,700;1,400&family=Oswald:wght@200;300;400;500&family=Sometype+Mono:ital,wght@0,400..700;1,400..700&display=swap" rel="stylesheet"> 18 <link type="text/css" rel="stylesheet" href="/css/normalize.css" /> 19 <link type="text/css" rel="stylesheet" href="/css/skeleton.css" /> 20 <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/css/font-awesome.min.css"> 21 <link type="text/css" rel="stylesheet" href="/css/journal.css" /> 22 <link type="text/css" rel="stylesheet" href="/css/article.css" /> 23 <link type="text/css" rel="stylesheet" href="/css/print.css" /> 24 25 <meta name="viewport" content="width=device-width, initial-scale=1.0"> 26 27 28
28<script> 29 function openDrawerMenu() 30 { 31 var x = document.getElementById("mainNavBar"); 32 if (x.className === "row") 33 { 34 x.className += " responsive"; 35 } else { 36 x.className = "row"; 37 } 38 } 39 40 document.addEventListener("DOMContentLoaded", function(event) { 41 document.querySelector('.toggle').addEventListener('click', function() { 42 nav = document.querySelector('.nav'); 43 nav.classList.toggle("active"); 44 }); 45 }); 46 </script>
46 47 48
48<script> 49 document.createElement( "picture" ); 50 </script>
50 51
51<script src="/js/picturefill.js" async></script>
51 52 <!-- head :: head :: END --> 53 </head> 54<!-- HEAD --> 55 56<!-- BODY --> 57 <body> 58 59 <div id="bar"> 60 <!-- content :: main menu :: BEG --> 61 <div id="barline"> 62 <div id="mtitle"> 63 <h1> 64 Journal of Information Architecture </h1> 65 </div> 66 </div> 67 <div id="menu"> 68 <nav class="nav"><ul class="menu"><li class="menu-item"><a href="/">home</a></li><li class="menu-item"><a class="current-issue" href="/issue/">SPRING 2026</a></li><li class="menu-item"><a href="/archives/">past issues</a></li><li class="menu-item"><a href="/about/">about jofia</a></li><li class="menu-item"><a class="selected" href="/submissions/">submissions</a></li></ul></nav><button class="toggle" aria-label="Menu"><i class="fa fa-bars" aria-hidden="true"></i></button> 69 </div> 70 <!-- content :: main menu :: END --> 71 </div> 72 <!-- HERO DIV --> 73 <div class="hero-img no-print" style="height: 100%;"> 74 <!-- header image :: BEG --> 75 <picture><!--[if IE 9]><video style="display: none;"><![endif]--><source srcset="/cvr/cover-submissions-2560.jpg 2400w" media="(min-width: 2400px)"><source srcset="/cvr/cover-submissions-1920.jpg 1800w" media="(min-width: 1600px)"><source srcset="/cvr/cover-submissions-1440.jpg 1200w" media="(min-width: 1200px)"><source srcset="/cvr/cover-submissions-1024.jpg 800w" media="(min-width: 800px)"><source srcset="/cvr/cover-submissions-800.jpg 320w" media="(min-width: 320px)"><!--[if IE 9]></video><![endif]--><img style="max-width: 100%; max-height: 100vh; margin: auto;" srcset="/cvr/cover-submissions.jpg" alt="" /></picture> <!-- header image :: END --> 76 <!-- breadcrumb :: BEG --> 77 <div id="breadcrumb" style="min-height: 6px;"> 78 </div> 79 <!-- issue no vol title :: BEG --> 80 <!-- issue no vol title :: END --> 81 <!-- breadcrumb :: END --> 82 </div> 83 <!-- HERO DIV --> 84 85 <!-- CONTAINER --> 86 <div class="container"> 87 <!-- CONTENT --> 88 <div id="content"> 89 90 91 <!-- content :: main :: BEG --> 92 <div id="main"> 93 94 <!-- content :: article :: BEG --> 95 96 <div class='twelve columns' id="article"> 97 98 <h2> 99 <a name="apc">Submitting a Draft Proposal or Manuscript</a> 100 </h2> 101 102 <p class="page"> 103 The Journal of Information Architecture is inviting contributions for upcoming issues. 104 Please submit drafts, abstracts, or complete articles to <strong>[email protected]</strong>. Remember that your paper will be reviewed in 105 accordance with our <a href="#open-peer-review">open peeer-review policy</a> unless you indicate you would rather undergo double blind peer-review. In this case, please explicitly 106 state your preference in your mail. 107 </p> 108 109 <p class="page"> 110 Read the Journal’s <a href="#guidelines">manuscript guidelines</a> for indications on how to submit a contribution and download either the 111 Word template (dotx) or the Open Document Template (ott). Complete instructions for styling a proposal are included in both documents. 112 </p> 113 114 <p class="page"> 115 There are no publication fees or article processing charges associated with publishing in the Journal. 116 </p> 117 118 <h3> 119 Rolling Waves Publishing Model 120 </h3> 121 122 <p class="page"> 123 The Journal of Information Architecture is published biannually in a Spring issue, usually beginning publication towards the end of February, and a 124 Fall issue, usually beginning publication at the end of August. 125 <br /> 126 Issues are published following a rolling waves model and feature a limited number of articles when they open: papers and contributions are added 127 regularly one at a time until the issue is closed. 128 </p> 129 130 <h3> 131 <a name="open-peer-review">Open Peer-review Process</a> 132 </h3> 133 134 <p class="page"> 135 All proposals accepted for review will undergo the Journal’s open peer-review process unless an agreement is in place between the author(s) 136 and the Editorial Board that a paper should be double–blind peer‐reviewed. 137 <br /> 138 The Journal’s open peer-review process follows the open identities model, where authors and reviewers are aware of each other’s identity 139 for the entire length of the peer-review process. Author’ and reviewers’ identities are never disclosed to the public, nor are the various 140 steps of the review process or its results, in any format. 141 The open peer-review process allows the Journal to facilitate a more informal and collaborative discussion aimed at improving the quality of the 142 proposal. 143 </p> 144 145 <p class="page"> 146 Prospective authors who want to submit a proposal but would prefer to be reviewed in accordance with a more traditional double blind peer-review can 147 indicate their preference in their mail at the moment of submission. While the Journal will honor the request, authors should be aware that choosing 148 an alternative review model might introduce delays or cause the lengthening of the review process. 149 </p> 150 151 <p class="page"> 152 Regardless of the modality of review, the Journal employs multiple reviewers for any paper it evaluates and strives to ensure that only sound scientific or 153 professional contributions are published, as well as to grant a fair procedure for all submissions. 154 </p> 155 156 <p class="page"> 157 For more about open peer-review, read for example <a href="https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5437951/">What is open peer review? A systematic review</a>. 158 </p> 159 160 <h3> 161 Review Stages 162 </h3> 163 164 <p class="page"> 165 All incoming draft proposals and manuscripts are first evaluated by the Editor–in–Chief. 166 Draft and manuscripts rejected at this stage either fall outside of the aims and scope of the Journal, have major structural or logical issues, or very poor form. 167 Authors of proposals or manuscripts rejected at this stage will be informed approximately within a month of receipt. 168 Draft proposals and manuscripts that are provisionally approved for review are passed on to a minimum of two expert referees for the actual review. 169 </p> 170 171 <h3> 172 Selection of Referees 173 </h2> 174 175 <p class="page"> 176 Referees are matched to a manuscript according to their expertise. To ensure a fair review, besides adopting the open peer-review approach, the Journal 177 verifies that referees and authors do not share affiliation that may introduce bias. We encourage suggestions of possible referees from authors, though these 178 recommendations will not be necessarily used. The sole person responsible for the selection of referees is the Editor–in–Chief or an associate 179 editor appointed by the EiC for the task. 180 181 <h3> 182 Reports by Referees 183 </h3> 184 185 <p class="page"> 186 Reports by referees include both qualitative and quantitative assessments according to a standardized form and are shared with the authors who so desire at the end of 187 the review process. 188 Referees are asked to evaluate whether the proposed contribution: 189 </p> 190 191 <ul> 192 <li>Is original;</li> 193 <li>Is relevant for the scientific or professional community;</li> 194 <li>Is methodologically sound;</li> 195 <li>Includes accurately supported conclusions;</li> 196 <li>Correctly cites earlier relevant work;</li> 197 <li>Follows appropriate ethical guidelines;</li> 198 <li>Is clear and thorough in presentation;</li> 199 </ul> 200 201 <p class="page"> 202 Language correction is not part of the peer review process but referees may, if they so wish, suggest corrections to the text. 203 </p> 204 205 <h3> 206 Duration of the Review Process 207 </h3> 208 209 <p class="page"> 210 The review process of the Journal of Information Architecture ought not to exceed 12 weeks. 211 However, the process may take longer in some special cases. The Editor-in-Chief makes sure to keep the authors abreast of the process in such cases. 212 Should the referees’ reports contradict one another or a report delayed, further expert opinion will be sought. 213 In exceptional cases for which it is particularly difficult to find an additional referee to review the manuscript, or when at least one referee’s 214 report has thoroughly convinced the EiC, decisions at this stage to accept, reject or ask the authors for a revision are made on the basis 215 of only one referee’s report. 216 </p> 217 218 <h3> 219 Final Decision, Acceptance, and Publication Date 220 </h3> 221 222 <p class="page"> 223 The EiC’s final decision to publish (as is, or with minor revisions) or reject the manuscript will be sent to the authors together with 224 any final recommendations made by the referees, which might include a request for another revision of the manuscript before publication. 225 The complete original forms will be sent only upon the authors’ request. 226 <br /> 227 Referees, occasionally along with other editors or members of the Advisory Board, only advise the EiC, who is the sole person responsible for the final decision. 228 </p> 229 230 <p class="page"> 231 Indicatively, manuscript finalized between October 1st and Feb 28th will be published in the Spring Issue, which will generally open at the end 232 of February and close at the end of June. Proposals finalized between March 1st and September 30th will be published in the Fall Issue, which 233 will generally open at the end of August and close at the end of December. 234 Different agreements might nonetheless be put in place between the authors and the EiC, for example when the manuscript is being considered for publication 235 as part of an upcoming special issue. 236 </p> 237 238 <h3>
239 <a name="copyright">Copyright</a> 240 </h3> 241 242 <p class="page"> 243 All articles and contributions published by the Journal are licensed under the <a href="https://creativecommons.org/licenses/by-nc-nd/4.0/">Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License</a>. 244 </br> 245 Articles are freely available at no charge and visitors are allowed to read, download, print, distribute, link, or use the articles published for any other lawful purpose without prior permission, within the limit of the CC-BY-NC-ND license. 246 <br /> 247 Individual authors retain copyright of their work. You can read more about licenses and copyright on the <a href="https://creativecommons.org/licenses/">Creative Commons website</a>. 248 <br /> 249 As of September 2022, the Journal has applied to obtain formal Open Access status. 250 </p> 251 252 <h2> 253 Topics, Subject Areas, and Loci of Interest 254 </h2> 255 256 <p class="page"> 257 The Journal focuses on information architecture research and development in all types of shared information environments and favors a systemic approach 258 from different perspectives, such as for example technical, cultural, social, and communicational. 259 </p> 260 <p class="page"> 261 The Journal publishes original papers; original research already published by other journals, but rewritten with a clearer focus on information architecture or for the purpose of demonstrating its relevance to information architecture; systematic bibliographies and recognition works in the field of information architecture; useful case studies; students’ papers on information architecture-related projects. 262 </p> 263 264 <p class="page"> 265 The Journal if broadly interested in theoretical and practical contributions to the field of information architecture and its role in the conceptualization, 266 formalization, design, and implementation of digital / physical and blended information spaces and the critical reflection thereof. 267 Suggested topics of inquiry include but are not limited to: 268 </p> 269 270 <ul> 271 <li> 272 Information architecture as a design practice; 273 </li> 274 <li> 275 Theoretical foundations of information architecture; 276 </li> 277 <li> 278 Pervasive information architecture; 279 </li> 280 <li> 281 History of information architecture; 282 </li> 283 <li> 284 Information architecture techniques and best practices; 285 </li> 286 <li> 287 Placemaking in digital and blended spaces 288 </li> 289 <li> 290 Wayfinding, navigation, and navigation behaviors; 291 </li> 292 <li> 293 Categorization, labeling and representation in digital, physical, and blended spaces; 294 </li> 295 <li> 296 Organization of information, taxonomies and folksonomies; 297 </li> 298 <li> 299 Pace layering; 300 </li> 301 <li> 302 Social media, social networks, and social computing; 303 </li> 304 <li> 305 Postdigital culture; 306 </li> 307 <li> 308 Information architecture in organizations, in communities, and in society; 309 </li> 310 <li> 311 The role of information architecture in information systems; 312 </li> 313 <li> 314 The value of information architecture for organizations; 315 </li> 316 <li> 317 The impact of information architecture on information policies and information strategy; 318 </li> 319 <li> 320 Multilingual, multicultural information architecture; global information architecture; 321 </li> 322 <li> 323 Information architecture metrics and evaluation; 324 </li> 325 <li> 326 The impact of information architecture on people’s attitude, behavior, performance, perception, and productivity; 327 </li> 328 <li> 329 Information architecture education and training 330 </li> 331 <li> 332 Information architecture research 333 </li> 334 </ul> 335 336 <h2> 337 Becoming a Referee for the Journal 338 </h2> 339 340 <p class="page"> 341 The person in charge of the journal’s peer review procedures is Editor–in–Chief Andrea Resmini (ar at journalofia dot org). 342 If you would like to be considered as a referee for future issues, e-mail Andrea Resmini directly via email, specifying you are considering applying for 343 a referee role in the subject, and providing a brief description of your interests and expertise in information architecture or related fields. 344 </p> 345 346 <h2> 347 <a name="guidelines">Manuscript Guidelines</a> 348 </h2> 349 350 <h3> 351 Format of the Submission 352 </h3> 353 354 <p class="page"> 355 Draft proposals and manuscripts should be submitted in either Open Document Format (odt) or Microsoft Word format (docx) and styled using the templates 356 provided below. Proposal submitted in other formats, including PDF, will not be considered. The documents should be sent to <strong>[email protected]</strong> 357 as attachment and should include the full name, affiliation, and email address of the author or authors. 358 </p> 359 360 <h3> 361 Templates 362 </h3> 363 364 <p class="page"> 365 You can download the Journal’s draft proposal or manuscript template in either <a href="/files/journalofia-template.ott">Open Document Format</a> (ott) or 366 <a href="/files/journalofia-template.dotx">Microsoft Word format</a> (dotx). A <a href="/files/journalofia-template.pdf">PDF version</a> is also available primarily to 367 provide a visual rendition of the different styles used in the template. 368 </p> 369 370 <p class="page" style="margin-bottom: 3rem;"> 371 We look forward to receiving your proposals. 372 </p> 373 </div> 374 <!-- content :: article :: END --> 375 376 <!-- content :: blocks :: BEG --> 377 <!-- content :: blocks :: END --> 378 379 380 </div> 381 <!-- content :: main :: END --> 382 383 </div> 384 <!-- CONTENT --> 385 386 </div> 387 <!-- CONTAINER --> 388 389 <!-- FOOTER --> 390 <!-- content :: footer :: BEG --> 391 <div class="footback"> 392 <div class="container"> 393 <div id="footer"> 394 <div class="row"> 395 <!-- content :: image credits and jofia boilerplate :: BEG --> 396 <p class="tsans tsmall tlight"> 397 The Journal of Information Architecture is an independent peer-reviewed scie
397ntific journal bridging practice and academia. It is an initiative of REG-iA, the Research & Education Group in Information Architecture in collaboration with the School of Information Technology at Halmstad University and Architecta, the Italian Society for Information Architecture <br /><br /> 398 <a rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/"><img alt="Creative Commons License" style="border-width:0" src="https://i.creativecommons.org/l/by-nc-nd/4.0/88x31.png" /></a><br />The Journal of Information Architecture is an open access journal and all content is licensed under a <a class="meta" rel="license" href="http://creativecommons.org/licenses/by-nc-nd/4.0/">Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License</a> . Articles are freely available at no charge and visitors are allowed to read, download, print, distribute, link, or use the articles published for any other lawful purpose without prior permission, within the limit of the CC-BY-NC-ND license. This is in accordance with the BOAI definition of open access</p> 399 400 401 402<p class="tsans tsmall tlight"> 403 Image: Roots and branches – Journal of Information Architecture</p> 404 405 406 <!-- content :: image credits and jofia boilerplate :: END --> 407 </div> 408 409 <div class='row' id="footer-container"> 410 411 <!-- content :: meta :: BEG --> 412 <div class='eight columns' id="meta"> 413 <p class="meta"> 414 <strong>REG-iA</strong> 415 <br /> 416 The Research and Education Group in Information Architecture 417 <br /> 418 <br /> 419 <strong>Halmstad University</strong> 420 <br /> 421 <a class="meta" href="https://www.hh.se/english/about-the-university/schools/school-of-information-technology.htm">School of Information Technology</a> 422 <br /> 423 <br /> 424 <strong>Architecta</strong> 425 <br /> 426 <a class="meta" href="http://architecta.it">Italian Society for Information Architecture</a> 427 <br /> 428 <br /> 429 <strong>Design Culture Collective</strong> 430 <br /> 431 <a class="meta" href="http://english.designculturecollective.org">Promoting the culture and value of the design practice</a> 432 <br /> 433 <br /> 434 <strong>Copenhagen Business School</strong> 435 <br /> 436 <a class="meta" href="http://uk.cbs.dk/">Founding partner</a> 437 </p> 438 439 <!--PRIVACY --> 440 <p class="meta"> 441 <strong>Privacy</strong> 442 <br /> 443 The Journal of Information Architecture adopts a no-data-saved policy 444 </p> 445 <!--PRIVACY --> 446 447 <p class="meta"> 448 All content © 2009–2026 — Journal of Information Architecture and individual authors 449 <!-- Individual authors retain copyright of their works if not expressedly indicated otherwise --> 450 </p> 451 </div> 452 <!-- content :: meta :: END --> 453 <!-- content :: colophon :: BEG --> 454 <div class='four columns' id="colophon"> 455 <p class="colophon"> 456 <strong>Journal of Information Architecture</strong> 457 <br /> 458 http://journalofia.org/ 459 <br /> 460 ISSN 1903-7260 461 </p> 462 <p class="colophon"> 463 <strong>General inquiries</strong> 464 <br /> 465 [email protected] 466 </p> 467 <p class="colophon"> 468 <strong>Manuscripts and submissions</strong> 469 <br /> 470 [email protected] 471 </p> 472 <p class="colophon"> 473 <strong>Editors</strong> 474 <br /> 475 [email protected] 476 </p> 477 478 </div> 479 <!-- content :: colophon :: END --> 480 </div> 481 </div> 482 <!-- content :: footer :: BEG --> 483 </div> 484 </div> 485 <!-- content :: footer :: END --> 486 487 <!-- FOOTER --> 488 489 </body> 490<!-- BODY --> 491<!-- PRINT FOOTER START --> 492 <div id="footer-print"> 493 <p></p> 494 </div> 495<!-- PRINT FOOTER END --> 496 497</html>
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.