364
edits
Changes
no edit summary
Post to the [[Code4Lib Journal Publicity Venues]].
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 <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 publication in mid <Month YYYY>, please submit articles, abstracts, or proposals at via the [https://journalforms.code4lib.orggle/submit-proposal 2U8yV6TeG4ep8o6w5 Submission Form] 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 welcome submissions across a broad variety of topics that support the mission of the journal. Possible topics include, but are not limited to:
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: https://journal.code4lib.org.
Remember, for consideration for the <nth> issue, please send submit proposals, abstracts, or draft articles to via the [https://journalforms.code4lib.orggle/submit-proposal 2U8yV6TeG4ep8o6w5 Submission Form] no later than Friday, <Month DD, YYYY>.
When a proposal has been accepted, authors will submit drafts to the assigned editor in a format likely to be widely readable (with a strong preference for Google Docs). The article should be accompanied by brief "about the author(s)" metadata. We may request the submission in a different format if we have trouble with yours.
Please note that articles published in <em>C4LJ</em> must be licensed by their authors under a <a href="http://creativecommons.org/licenses/by/3.0/us/">US CC-BY license</a>. We recommend but do not require that any included code also be given an <a href="http://www.opensource.org/licenses/category">open source license</a> suitable for code. Authors are free to publish articles anywhere else in addition to <em>C4LJ</em>.
By submitting the proposal you accept that the email and full name of authors will appear with your submission, and that all named authors are consenting to this. If your article involves the utilization of individuals’ personal data (such as but not limited to email addresses, unique identifiers, borrowing history - a <a href="https://www.dol.gov/general/ppii">potentially useful definition is available from the US Department of Labor</a>) it is not currently eligible for inclusion in Code4Lib. The editorial committee is undertaking an audit of internal editorial practices in order to prevent accidental exposure of personally identifiable information.
Note: We cannot accept files with the anticipation we host them as attachments to the article, and encourage use of open formats in linked files.
For more information, see our <a href="https://journal.code4lib.org/article-guidelines/">Article Guidelines</a> and the Journal's <a href="https://journal.code4lib.org/process-and-structure/">Process and Structure</a>.
Send in a submission. Your peers would like to hear what you are doing.
Code4Lib Journal Editorial Committee
== Submission Acknowledgement ==
<pre>
Thank you for submitting a proposal to the Code4Lib Journal. We appreciate your participation in the Code4Lib community. The editors have received your proposal and will be in touch with you { within 2 weeks or put date if reviewing all together} regarding its appropriateness for publication in C4LJ. We will notify you if we need additional information to make this decision. Please feel free to contact me if you have additional questions.
</pre>
<s>The C4LJ editorial team has begun collecting demographic data about abstracts submitted in an effort to understand the diversity (or lack thereof) of proposals submitted. This data will not be connected to your submission or viewed by the editorial team during the process of voting on submissions. The aggregate data will be curated and made publicly available annually. If you would be willing to participate and have not already done so, please use the following link. We would appreciate your distributing the link to co-authors: https://forms.gle/4zHtARWPP7bNdniw6</s>
== Submission Acknowledgement with Request for CC-BY Affirmation ==
for this publication, could you share more details about the intended
audience for the article and how it will address issues surrounding
technology in libraries? Please respond to journal@code4lib.org me with the additional information requestedor to ask any additional questions.
</pre>
Thanks for considering us, and please do not hesitate to submit a new or revised proposal in the future.
</pre>
== Article Ready for Review ==
Hello Author Name -
Your article is now in WordPress and ready for final review - preview instructions are given below. Please review the article and let me know if you see anything amiss. We expect the journal to publish {put approximate date here}. As a reminder, publication is contingent on final review by the editorial board.
Thank you for your contribution to the C4LJ community.
/// Article Viewing Instructions ///
Note: You cannot edit the article directly; please pass any changes along to me in the body of an email.
1. Log in to WordPress (https://journal.code4lib.org/wp-login.php )
username: author
pass: {put current password here}
NOTE: this login will take you to a generic profile page. Please do not change anything on this page.
2. Once you have successfully logged in, visit the proof for your article: https://journal.code4lib.org/?p={put_article_number_here}&preview=true
3. PLEASE don't change the password or share beyond your co-authors.
== Call-for-Editors ==