Changes

Code4Lib Journal Email Templates

9 bytes removed, 17:54, 2 April 2020
Call for proposals: Remove hard line returns inside paragraphs
Call for Papers (and apologies for cross-posting):
The Code4Lib Journal (C4LJ) exists to foster community and shareinformation among those interested in the intersection of libraries,technology, and the future.
We are now accepting proposals for publication in our <nth> issue.Don't miss out on this opportunity to share your ideas and experiences.To be included in the <nth> issue, which is scheduled for publicationin mid <Month YYYY>, please submit articles, abstracts, or proposals athttps://journal.code4lib.org/submit-proposal or to journal@code4lib.org by Friday, <Month DD, YYYY>. 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 welcomesubmissions across a broad variety of topics that support the missionof 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
* Assessment and user studies
C4LJ strives to promote professional communication by minimizing thebarriers to publication. While articles should be of a high quality,they need not follow any formal structure. Writers should aim for themiddle ground between blog posts and articles in traditional refereedjournals. Where appropriate, we encourage authors to submit codesamples, algorithms, and pseudo-code. For more information, visit C4LJ’s Article Guidelines or browse articles from the earlier issues published on our website: http ttp://journal.code4lib.org.
Remember, for consideration for the <nth> issue, please send proposals,abstracts, or draft articles to https://journal.code4lib.org/submit-proposalno later than Friday, <Month DD, YYYY>. (Use journal@code4lib.org ifsending attachments.)
Send in a submission. Your peers would like to hear what you are doing.
364
edits