[prev in list] [next in list] [prev in thread] [next in thread]
List: web4lib
Subject: [WEB4LIB] Code4Lib Journal Call for Papers (52nd Issue)
From: Mark Swenson <mark () WINNETKALIBRARY ! ORG>
Date: 2021-05-11 2:06:28
Message-ID: CH2PR06MB670962A5FDB1C8BD97515E91C1539 () CH2PR06MB6709 ! namprd06 ! prod ! outlook ! com
[Download RAW message or body]
Call for Papers (and apologies for cross-posting):
The Code4Lib Journal (C4LJ) exists to foster community and share informatio=
n among those interested in the intersection of libraries, technology, and =
the future.
We are now accepting proposals for publication in our 52nd issue. Don't mis=
s out on this opportunity to share your ideas and experiences. To be includ=
ed in the 52nd issue, which is scheduled for publication in mid-September 2=
021, please submit articles, abstracts, or proposals at https://journal.cod=
e4lib.org/submit-proposal or to journal@code4lib.org<mailto:journal@code4li=
b.org> by Friday, June 11, 2021. When submitting, please include the title=
or subject of the proposal in the subject line of the email message.
C4LJ encourages creativity and flexibility, and the editors welcome submiss=
ions across a broad variety of topics that support the mission of the journ=
al. Possible topics include, but are not limited to:
* Practical applications of library technology (both actual and hypothetica=
l)
* Technology projects (failed, successful, or proposed), including how they=
were done and the challenges faced
* Case studies
* Best practices
* Reviews
* Comparisons of third party software or libraries
* Analyses of library metadata for use with technology
* Project management and communication within the library environment
* Assessment and user studies
C4LJ strives to promote professional communication by minimizing the barrie=
rs to publication. While articles should be of a high quality, they need n=
ot follow any formal structure. Writers should aim for the middle ground b=
etween blog posts and articles in traditional refereed journals. Where app=
ropriate, we encourage authors to submit code samples, algorithms, and pseu=
do-code. For more information, visit C4LJ=92s Article Guidelines or browse =
articles from the earlier issues published on our website: https://journal=
.code4lib.org.
Remember, for consideration for the 52nd issue, please send proposals, abst=
racts, or draft articles to https://journal.code4lib.org/submit-proposal no=
later than Friday, June 11, 2021. (Use journal@code4lib.org<mailto:journa=
l@code4lib.org> if sending attachments.)
Send in a submission. Your peers would like to hear what you are doing.
Mark Swenson, Coordinating Editor for Issue 52
Code4Lib Journal Editorial Committee
[Attachment #3 (text/html)]
<html xmlns:o="urn:schemas-microsoft-com:office:office" \
xmlns:w="urn:schemas-microsoft-com:office:word" \
xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" \
xmlns="http://www.w3.org/TR/REC-html40"> <head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:0 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
p.p1, li.p1, div.p1
{mso-style-name:p1;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.s1
{mso-style-name:s1;}
span.apple-converted-space
{mso-style-name:apple-converted-space;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:12.0pt;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="#0563C1" vlink="#954F72" style="word-wrap:break-word">
<div class="WordSection1">
<p class="p1" style="margin:0in"><span class="s1"><span \
style="font-family:Helvetica;color:black">Call for Papers (and apologies for \
cross-posting):</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">The Code4Lib Journal \
(C4LJ) exists to foster community and share information among those interested in the \
intersection of libraries, technology, and the future.</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">We are now accepting \
proposals for publication in our 52nd issue. Don't miss out on this opportunity to \
share your ideas and experiences. To be included in the 52nd issue, which is \
scheduled for publication in mid-September 2021, please submit articles, abstracts, \
or proposals at</span></span><span class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black"><a \
href="https://journal.code4lib.org/submit-proposal">https://journal.code4lib.org/submit-proposal</a>
or to</span></span><span class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black"><a \
href="mailto:journal@code4lib.org">journal@code4lib.org</a></span></span><span \
class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black">by Friday, June 11, 2021. When \
submitting, please include the title or subject of the proposal in the subject line \
of the email message.</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">C4LJ encourages \
creativity and flexibility, and the editors welcome submissions across a broad \
variety of topics that support the mission of the journal. Possible topics \
include, but are not limited to:</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Practical \
applications of library technology (both actual and hypothetical)</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Technology \
projects (failed, successful, or proposed), including how they were done and the \
challenges faced</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Case \
studies</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Best \
practices</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* \
Reviews</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Comparisons of \
third party software or libraries</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Analyses of \
library metadata for use with technology</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Project management \
and communication within the library environment</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">* Assessment and \
user studies</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">C4LJ strives to \
promote professional communication by minimizing the barriers to publication. \
While articles should be of a high quality, they need not follow any formal \
structure. Writers should aim for the middle ground between blog posts and \
articles in traditional refereed journals. Where appropriate, we encourage \
authors to submit code samples, algorithms, and pseudo-code. For more information, \
visit C4LJ’s Article Guidelines or browse articles from the earlier issues published \
on our website: </span></span><span class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black"><a \
href="https://journal.code4lib.org">https://journal.code4lib.org</a>.</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">Remember, for \
consideration for the 52nd issue, please send proposals, abstracts, or draft articles \
to</span></span><span class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black"><a \
href="https://journal.code4lib.org/submit-proposal">https://journal.code4lib.org/submit-proposal</a></span></span><span \
class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black">no later than Friday, June 11, 2021. \
(Use</span></span><span class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black"><a \
href="mailto:journal@code4lib.org">journal@code4lib.org</a></span></span><span \
class="apple-converted-space"><span \
style="font-family:Helvetica;color:black"> </span></span><span class="s1"><span \
style="font-family:Helvetica;color:black">if sending \
attachments.)</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">Send in a \
submission. Your peers would like to hear what you are \
doing.</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span \
style="font-family:Helvetica;color:black"> </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">Mark Swenson, \
Coordinating Editor for Issue 52 </span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="p1" \
style="margin:0in;font-variant-caps: normal;orphans: auto;text-align:start;widows: \
auto;-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> \
<span class="s1"><span style="font-family:Helvetica;color:black">Code4Lib Journal \
Editorial Committee</span></span><span \
style="font-family:Helvetica;color:black"><o:p></o:p></span></p> <p class="MsoNormal" \
style="caret-color: rgb(0, 0, 0);font-variant-caps: normal;orphans: \
auto;text-align:start;widows: auto;-webkit-text-size-adjust: \
auto;-webkit-text-stroke-width: 0px;word-spacing:0px"> <span \
style="color:black"> </span><span style="color:black"><o:p></o:p></span></p> <p \
class="MsoNormal"><span style="font-size:11.0pt"><o:p> </o:p></span></p> </div>
</body>
</html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic