[prev in list] [next in list] [prev in thread] [next in thread]
List: web4lib
Subject: [WEB4LIB] Code4Lib Journal - 2nd Call for Papers (and apologies for cross-posting)
From: Meghan Finch <mmfinch () OAKLAND ! EDU>
Date: 2016-01-11 16:26:51
Message-ID: CA+BYxggFT+gDgXZ4yuU730oDqKbKq68t-FYETHV7WLCyDuuYtw () mail ! gmail ! com
[Download RAW message or body]
I apologize for the additional posting. I just wanted to remind everyone
that submissions are due to Code4Lib for Issue 32 this Friday, January 15.
Thank you!
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 32nd issue.
Don't miss out on this opportunity to share your ideas and experiences.
To be included in the 32nd issue, which is scheduled for publication
in mid April 2016, please submit articles, abstracts, or proposals at
http://journal.code4lib.org/submit-proposal or to journal@code4lib.org
by Friday, January 15, 2016. 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 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's Article Guidelines or browse articles from the first 31 issues
published on our website: http://journal.code4lib.org.
Remember, for consideration for the 32nd issue, please send proposals,
abstracts, or draft articles to journal@code4lib.org no later than
Friday, January 15, 2016.
Send in a submission. Your peers would like to hear what you are doing.
Code4Lib Journal Editorial Committee
--
Meghan Finch
Assistant Professor
Digital Assets Librarian
Oakland University
Rochester, MI
mmfinch@oakland.edu
============================
To unsubscribe: http://bit.ly/web4lib
Web4Lib Web Site: http://web4lib.org/
2016-01-11
[Attachment #3 (text/html)]
<div dir="ltr">I apologize for the additional posting. I just wanted to remind \
everyone that submissions are due to Code4Lib for Issue 32 this Friday, January 15. \
Thank you!<br><br>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 32nd \
issue.<br>Don't miss out on this opportunity to share your ideas and \
experiences.<br>To be included in the 32nd issue, which is scheduled for \
publication<br>in mid April 2016, please submit articles, abstracts, or proposals \
at<br><a href="http://journal.code4lib.org/submit-proposal">http://journal.code4lib.org/submit-proposal</a> \
or to <a href="mailto:journal@code4lib.org">journal@code4lib.org</a><br>by Friday, \
January 15, 2016. 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 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<br>C4LJ's Article Guidelines or browse \
articles from the first 31 issues<br>published on our website: <a \
href="http://journal.code4lib.org">http://journal.code4lib.org</a>.<br><br>Remember, \
for consideration for the 32nd issue, please send proposals,<br>abstracts, or draft \
articles to <a href="mailto:journal@code4lib.org">journal@code4lib.org</a> no later \
than<br>Friday, January 15, 2016.<br><br>Send in a submission. Your peers would \
like to hear what you are doing.<br><br><br>Code4Lib Journal Editorial Committee<br \
clear="all"><br>-- <br><div class="gmail_signature">Meghan Finch<br> Assistant \
Professor<br> Digital Assets Librarian<br>
Oakland University<br>
Rochester, MI<br>
<a href="mailto:mmfinch@oakland.edu" target="_blank">mmfinch@oakland.edu</a></div>
</div>
============================
<p>
To unsubscribe: http://bit.ly/web4lib
</p><p>
Web4Lib Web Site: http://web4lib.org/
</p><p>
2016-01-11
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic