Title<\/strong>:\u00a0Code4Lib Journal\u00a0<\/em><\/p>\n ISSN<\/strong>: 1940-57581<\/sup><\/p>\n Purpose, objective, or mission<\/strong>: According to its mission website<\/a>, \u201cthe\u00a0Code4Lib Journal<\/em>\u00a0exists to foster community and share information among those interested in the intersection of libraries, technology, and the future.\u201d2<\/sup>\u00a0It \u201caims to help engender collective understanding and the necessary support for improving library technology and digital services.\u201d3<\/sup><\/p>\n Website<\/strong>:\u00a0Code4Lib<\/em> Homepage<\/a><\/p>\n Target audience<\/strong>: The target audience includes anyone who is involved in the \u201cwider library community\u201d who has an interest in libraries and technology.4<\/sup><\/p>\n Publisher<\/strong>:\u00a0Code4Lib<\/a>. Publication began in 2007.5<\/sup><\/p>\n Peer reviewed<\/strong>? Yes. Journal submissions are reviewed by an editorial committee6<\/sup>, and the committee views its process of selecting articles as an open peer review. According to a message from the 2020 coordinating editor, \u201cThe author and the designated editor work together to improve a paper before publication. The author knows the name of the editor and other readers on the editorial committee and\u00a0vice versa<\/em>. We\u2019ve found that this process works best for us and produces consistently high quality and relevant content for our audience.\u201d7<\/sup><\/p>\n Type<\/strong>: Open access with Creative Commons license. Although the editorial committee consists mainly of those involved in the academic library community, contents do not necessarily have the format of a traditional scholarly research article, and the journal does not use a traditional blind peer review. Articles can vary in formality and can include case studies and personal opinion pieces. Articles do not generally include extensive literature reviews. For these reasons, the journal is currently classed here as \u2018professional news\u2019. Articles tend to be focused on the practical application of the ideas presented.8<\/sup><\/p>\n Medium<\/strong>:\u00a0Code4Lib Journal<\/em>\u00a0is available online.9<\/sup><\/p>\n Content<\/strong>: From the\u00a0Call for Submissions<\/a>, \u201cthe editorial committee is looking for content that is practical, demonstrates how to exploit technology to create digital library collections and services, or offers insight and forethought regarding the use of computers in any type of library setting.\u201d10<\/sup><\/p>\n The journal publishes articles on a multitude of subjects, as long as they support the mission statement, and is flexible with length (1,500 to 5,000 words is an approximate word count). The types of articles published in the journal include:<\/p>\n Frequency of publication<\/strong>: It is published quarterly in March, June, September, and December.12<\/sup><\/p>\n Location of submission guidelines<\/strong>:\u00a0Call for Submissions<\/a><\/p>\n Types of contributions accepted<\/strong>: The types of articles the journal is looking for include:<\/p>\n Submission and review process<\/strong>: Submissions can be sent in the form of either an abstract or a complete draft. Submit articles using the\u00a0online form<\/a>, or via email to journal@code4lib.org. Once submitted the article goes through an editorial process, and not a peer review.14<\/sup><\/p>\n Editorial tone<\/strong>: \u201cWriters should aim for the middle ground between, on the one hand, blog or mailing-list posts, and, on the other hand, articles in traditional journals.\u201d15<\/sup><\/p>\n Style guide used<\/strong>: From the article guidelines: \u201cWhile articles in\u00a0C4LJ<\/em>\u00a0should be of high quality, they need not follow any formal structure or guidelines.\u201d16<\/sup>\u00a0However, endnotes and references should be cited using the\u00a0Council of Science Editors (CSE) Style Guide<\/em>.17<\/sup><\/p>\n This journal provides a semiformal setting in which to discuss issues of technology in the library and information science world. The information in the journal is concentrated around technology, and its place within the library setting, so it would be a good place for anyone with an interest in this subject to find a home for one of their articles.<\/p>\n <\/p>\n Publication circulation<\/strong>: Since the journal is 100% online, there was no information on the exact circulation available.18<\/sup><\/p>\n Audience location and language or cultural considerations<\/strong>: The editorial committee is based throughout the United States, but the writers come from both within and outside the United States.19<\/sup>\u00a0The journal is written in English, and although the editorial committee is American, not all of the contributors are. (Article guidelines note that articles should be written in English, and that \u201cAmerican or British usage is accepted, but not a mixture of these.\u201d)20<\/sup> Also, due to the online nature of the journal, people from anywhere in the world would have the ability to access the articles. Because of this, it would most likely be prudent to explain the use of any language or content that was too culturally specific.<\/p>\n Reader characteristics<\/strong>: Code4Lib is a \u201cvolunteer-driven collective of hackers, designers, architects, curators, catalogers, artists and instigators from around the world, who largely work for and with libraries, archives, and museums on technology \u2018stuff\u2019.\u201d From looking through the author\u2019s information supplies with the articles, it appears that almost all of the contributors work in academic libraries, although their actual job titles vary quite a bit. These job titles range from web designer to information technology coordinator to systems librarian. While this information is about the writers, it goes to show that the journal is of interest to all different types of professionals involved technologies in libraries. Of course, they also all have a professional interest in the intersection of libraries and technology.\u00a0Code4Lib<\/em>\u00a0is of interest to \u201ctechnology folks in libraries, archives, and museums to informally share approaches, techniques, and code across institutional and project divides.\u201d21<\/sup>\u00a0The readers of this journal are likely to have established opinions about the place of technology in libraries. A look at the\u00a0mission statement<\/a>\u00a0shows that the readers are likely to feel that technology holds a key position in the future of libraries.22<\/sup><\/p>\n Knowledge of LIS subject matter<\/strong>: The readers of\u00a0Code4Lib Journal<\/em>\u00a0would have a good knowledge and understanding of LIS topics and issues. They would also be familiar with library jargon. On top of that, due to the technical nature of the journal, they would also be familiar with most technical jargon.23<\/sup><\/p>\n The common thread running among these readers is an interest in, and a passion for, technology and its use within a library setting. Their level of technical knowledge would be rather high, and this would be an important thing for writers to keep in mind. In fact, it would also be a necessity for the writers of a proposed article for\u00a0Code4Lib Journal<\/em>\u00a0to have significant expertise in technology.<\/p>\n Publication analysis About the publication Title:\u00a0Code4Lib Journal\u00a0 ISSN: 1940-57581 Purpose, objective, or mission: According to its mission website, \u201cthe\u00a0Code4Lib Journal\u00a0exists to foster community and share information among those interested in the intersection of libraries, technology, and the future.\u201d2\u00a0It \u201caims to help engender collective understanding and the necessary support for improving library technology and digital services.\u201d3 […]<\/p>\n","protected":false},"author":772,"featured_media":0,"parent":2015,"menu_order":14,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2455","page","type-page","status-publish","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/pages\/2455","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/users\/772"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/comments?post=2455"}],"version-history":[{"count":5,"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/pages\/2455\/revisions"}],"predecessor-version":[{"id":3294,"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/pages\/2455\/revisions\/3294"}],"up":[{"embeddable":true,"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/pages\/2015"}],"wp:attachment":[{"href":"https:\/\/wordpress.library.illinois.edu\/infosci\/wp-json\/wp\/v2\/media?parent=2455"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
About the publication\u2019s submission guidelines<\/h3>\n
\n
Conclusion: Evaluation of publication\u2019s potential for LIS authors<\/h3>\n
Audience analysis<\/h2>\n
\nAbout the publication\u2019s readers<\/h3>\n
Conclusion: Analysis of reader characteristics and their potential impact on authors<\/h3>\n
\nReferences<\/h4>\n
\n