[prev in list] [next in list] [prev in thread] [next in thread] 

List:       web4lib
Subject:    [WEB4LIB] Call for Submissions: Code4Lib Journal
From:       Brighid MG <brighidmg () GMAIL ! COM>
Date:       2020-01-27 15:10:49
Message-ID: CAOHy7D850T4+M3pe7o0jXgJS5nuKucnVBC051R3K222vmcmG4w () mail ! gmail ! com
[Download RAW message or body]

Call for Papers (and apologies for cross-posting):

The Code4Lib Journal (C4LJ) exists to foster community and share
information among those interested in the intersection of libraries,
technology, and the future.

We are now accepting proposals for publication in our 48th issue.
Don't miss out on this opportunity to share your ideas and experiences.
To be included in the 48th issue, which is scheduled for publication
in mid May 2020, please submit articles, abstracts, or proposals at
https://journal.code4lib.org/submit-proposal or to journal@code4lib.org
by Friday, February 7, 2020.  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
submissions across a broad variety of topics that support the mission
of the journal.  Possible topics include, but are not limited to:

* Practical applications of library technology (both actual and
  hypothetical)
* 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
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=E2=
=80=99s
Article Guidelines or browse articles from the earlier issues published on
our website: http://journal.code4lib.org.

Remember, for consideration for the 48th issue, please send proposals,
abstracts, or draft articles to https://journal.code4lib.org/submit-proposa=
l
no later than Friday, February 7, 2020.  (Use journal@code4lib.org if
sending attachments.)

Send in a submission.  Your peers would like to hear what you are doing.


Code4Lib Journal Editorial Committee

[Attachment #3 (text/html)]

<div dir="ltr">Call for Papers (and apologies for cross-posting):<br><br>The Code4Lib \
Journal (C4LJ) exists to foster community and share<br>information among those \
interested in the intersection of libraries,<br>technology, and the future.<br><br>We \
are now accepting proposals for publication in our 48th issue.<br>Don&#39;t miss out \
on this opportunity to share your ideas and experiences.<br>To be included in the \
48th issue, which is scheduled for publication<br>in mid May 2020, please submit \
articles, abstracts, or proposals at<br><a \
href="https://journal.code4lib.org/submit-proposal">https://journal.code4lib.org/submit-proposal</a> \
or to <a href="mailto:journal@code4lib.org">journal@code4lib.org</a> <br>by Friday, \
February 7, 2020.   When submitting, please include the title   <br>or subject of the \
proposal in the subject line of the email message.<br><br>C4LJ encourages creativity \
and flexibility, and the editors welcome<br>submissions across a broad variety of \
topics that support the mission<br>of the journal.   Possible topics include, but are \
not limited to:<br><br>* Practical applications of library technology (both actual \
and <br>   hypothetical)<br>* Technology projects (failed, successful, or proposed), \
including <br>   how they were done and the challenges faced<br>* Case studies<br>* \
Best practices<br>* Reviews<br>* Comparisons of third party software or \
libraries<br>* Analyses of library metadata for use with technology<br>* Project \
management and communication within the library environment<br>* Assessment and user \
studies<br><br>C4LJ strives to promote professional communication by minimizing \
the<br>barriers to publication.   While articles should be of a high quality,<br>they \
need not follow any formal structure.   Writers should aim for the<br>middle ground \
between blog posts and articles in traditional refereed<br>journals.   Where \
appropriate, we encourage authors to submit code<br>samples, algorithms, and \
pseudo-code. For more information, visit C4LJ's Article Guidelines or browse articles \
from the earlier issues published on our website: <a \
href="http://journal.code4lib.org">http://journal.code4lib.org</a>.<br><br>Remember, \
for consideration for the 48th issue, please send proposals,<br>abstracts, or draft \
articles to <a href="https://journal.code4lib.org/submit-proposal">https://journal.code4lib.org/submit-proposal</a><br>no \
later than Friday, February 7, 2020.   (Use <a \
href="mailto:journal@code4lib.org">journal@code4lib.org</a> if<br>sending \
attachments.)<br><br>Send in a submission.   Your peers would like to hear what you \
are doing.<br><br><br>Code4Lib Journal Editorial Committee</div>



[prev in list] [next in list] [prev in thread] [next in thread]