Changes

Change <angle brackets> and post Post to the [[Code4Lib Journal Publicity Venues]].

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 athttpvia the [https://journalforms.code4lib.orggle/submit-proposal or to journal@code4lib.org 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 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

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, visitC4LJ's C4LJ’s Article Guidelines or browse articles from the first <n> earlier issuespublished on our website: http https://journal.code4lib.org.

Remember, for consideration for the <nth> issue, please send submit proposals,abstracts, or draft articles to journal@code4libvia the [https://forms.org gle/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.

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 should will be in touch with you in { within 2-4 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 us at 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 == <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 regarding its appropriateness for publication in C4LJ.  Articles in the Code4Lib Journal are published with a Creative Commons 'By' license, and we require that all authors acknowledge that licensing (see http://journal@.code4lib.org /article-guidelines#Copyright - "Copyright/Licensing" section). Please send a reply and let us know if that is acceptable. We will notify you if we need additional information to make this decision. Please feel free to contact me if you have additional questions.

audience for the 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.

You may also contact the editors at journal@code4lib.org if you have any additional questions. We look forward to hearing from you.

<pre>I'm pleased to tell you that your recent proposal for an article about<topicTOPIC/titleTITLE> has been provisionally accepted to the Code4Lib Journal.The editorial committee is interested in your proposal, and would liketo see a draft.

<Additional comments ADDITIONAL COMMENTS about focus we'd like to see in the article or

As a member of the Code4Lib Journal editorial committee, I will beyour contact for this article, and will work with you to get it readyfor publication.  Working with me is second reader <SECOND READER>.  

We hope to publish your article in issue <nPICK_ONE> of the Journal, which isscheduled to appear mid <Month YYYY>. The deadline for submissionof a complete draft is <Friday, Month DD, YYYY>, but the sooner youcan get us a draft the better, and the more likely we'll be able toget your article into issue <n>. Upon receipt of the draft, I willwork with you to address any changes recommended by the EditorialCommittee. More information about our author guidelines may be foundat http://journal.code4lib.org/article-guidelines.

Please note that final drafts must be approved by Publishing an article in the Code4Lib Journal is a vote of collaborative effort between theEditorial Committee before being publishedauthors and editors.  The journal's editors work with authors throughout the draft-writing process to create a clear and useful article for the Code4Lib Journal audience.  That works best when a collaborative editing environment is used; we typically use Google Docs, but other tools such as Office 365 and even Etherpad can work as well.  When you have a draft ready for us to look at, please send me a link.

We look forward to seeing a complete draft and hope to include it Publishing an article inthe Code4Lib Journalis a collaborative effort between the authors and editors. Thank When you have a draft ready for submitting to usto look at, and feel free please send it to contactme directly in a common word processor format (for instance, DOCX for Microsoft Word or ODT for LibreOffice/OpenOffice). I will return it to you with any questionsmy comments and the comments from other journal editors.

</PICK_ONE> We hope to publish your article in issue <ISSUE> of the Journal, which is scheduled to appear <APPROXIMATE PUBLICATION DATE>.  To keep us on that publishing schedule, we have a series of deadlines—the first is the submission of a draft is <FIRST DRAFT DUE DATE>, but the sooner you can get us a draft the better—and the more likely we'll be able to get your article into the issue. Upon receipt of the draft, I will work with you to address any changes recommended by the Editorial Committee.  More information about our author guidelines may be found at http://journal.code4lib.org/article-guidelines. Please note that final drafts must be approved by a vote of the Editorial Committee before being published. We also require all authors to agree to US CC-BY licensing for the articles we publish in the journal. We recommend that any included code also have some type of code-specific open source license (such as the GPL). If the work described in the article makes use of personally identifiable information (PII), please confirm that proper approval was received from the relevant institutional review boards or equivalent bodies. Also please consider whether any of your images or screenshots require attributions. We look forward to seeing a complete draft and hope to include it in the Journal. Thank you for submitting to us, and feel free to contact me directly with any questions. If you could drop me a line acknowledging receipt of this email, thatwould be great.</pre>

We regret to inform you that your recent proposal to the Code4LibJournal for an article about <topic/title> has not been accepted forpublication. The Editorial Committee determined that it was not anappropriate match for the audience, mission, or scope of the Code4LibJournal. [optional - comment about why it's not appropriate]

For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.

Thanks for considering us, and please do not hesitate to contact theeditors at journal@code4lib.org in the future with submit a new or revisedproposalin the future.