Difference between revisions of "Code4Lib Journal Email Templates"
From Code4Lib
(→Need More Information) |
(→Proposal Accepted: <pre>) |
||
| Line 84: | Line 84: | ||
== Proposal Accepted == | == Proposal Accepted == | ||
| − | + | See also [[Code4Lib Journal Deadlines]]. | |
| + | <pre> | ||
I'm pleased to tell you that your recent proposal for an article about | I'm pleased to tell you that your recent proposal for an article about | ||
| − | < | + | <topic/title> has been provisionally accepted to the Code4Lib Journal. |
| − | Journal. | + | The editorial committee is interested in your proposal, and would like |
| − | would like to see a draft. | + | to see a draft. |
| − | < | + | <Additional comments about focus we'd like to see in the article or |
| − | article or editorial committee concerns. Sample language "We're | + | editorial committee concerns. Sample language: "We're especially |
| − | especially interested in X, and we'd like you to make sure to flesh | + | interested in X, and we'd like you to make sure to flesh this out when |
| − | this out when you write the article." | + | you write the article." or "We're interested in this proposal if you |
| − | proposal if you can do X, Y, or Z."> | + | can do X, Y, or Z."> |
As a member of the Code4Lib Journal editorial committee, I will be | As a member of the Code4Lib Journal editorial committee, I will be | ||
| Line 101: | Line 102: | ||
for publication. | for publication. | ||
| − | We hope to publish your article in issue < | + | We hope to publish your article in issue <n> of the Journal, which is |
| − | scheduled to appear | + | scheduled to appear mid <Month YYYY>. The deadline for submission |
| − | of a complete draft is < | + | of a complete draft is <Friday, Month DD, YYYY>, but the sooner you |
| − | get us a draft the better, and the more likely we'll be able to | + | can get us a draft the better, and the more likely we'll be able to |
| − | your article into issue < | + | get your article into issue <n>. Upon receipt of the draft, I will |
| − | with you to address any changes recommended by the Editorial | + | work with you to address any changes recommended by the Editorial |
| − | Committee. More information about our author guidelines may be found | + | Committee. More information about our author guidelines may be found |
| − | at http://journal.code4lib.org/article-guidelines. | + | at http://journal.code4lib.org/article-guidelines. |
Please note that final drafts must be approved by a vote of the | Please note that final drafts must be approved by a vote of the | ||
| Line 114: | Line 115: | ||
We also require all authors to agree to US CC-BY licensing for the | 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 | + | articles we publish in the journal. We recommend that any included |
code also have some type of code-specific open source license (such as | code also have some type of code-specific open source license (such as | ||
the GPL). | the GPL). | ||
We look forward to seeing a complete draft and hope to include it in | 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 | + | the Journal. Thank you for submitting to us, and feel free to contact |
me directly with any questions. | me directly with any questions. | ||
| − | If you could drop me a line acknowledging receipt of this email, that would be great. | + | If you could drop me a line acknowledging receipt of this email, that |
| + | would be great. | ||
| + | </pre> | ||
== Proposal Rejected == | == Proposal Rejected == | ||
Revision as of 15:42, 7 December 2010
See also Code4Lib_Journal_Deadlines
Contents
Call for proposals
Change <angle brackets> and 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 http://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 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 <n> issues published on our website: http://journal.code4lib.org. Remember, for consideration for the <nth> issue, please send proposals, abstracts, or draft articles to journal@code4lib.org no later than <Friday, Month DD, YYYY>. Send in a submission. Your peers would like to hear what you are doing. Code4Lib Journal Editorial Committee
Submission Acknowledgement
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 be in touch with you in 2-4 weeks 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 journal@code4lib.org if you have additional questions.
Need More Information
Thank you for your interest in publishing in the Code4Lib Journal. The Journal is primarily focused on technological issues in libraries. In order to help the editors determine if your proposal is appropriate for this publication, could you share more details about the intended audience for the the article and how it will address issues surrounding technology in libraries? Please respond to journal@code4lib.org with the additional information requested. You may also contact the editors at journal@code4lib.org if you have any additional questions. We look forward to hearing from you.
Proposal Accepted
See also Code4Lib Journal Deadlines.
I'm pleased to tell you that your recent proposal for an article about <topic/title> has been provisionally accepted to the Code4Lib Journal. The editorial committee is interested in your proposal, and would like to see a draft. <Additional comments about focus we'd like to see in the article or editorial committee concerns. Sample language: "We're especially interested in X, and we'd like you to make sure to flesh this out when you write the article." or "We're interested in this proposal if you can do X, Y, or Z."> As a member of the Code4Lib Journal editorial committee, I will be your contact for this article, and will work with you to get it ready for publication. We hope to publish your article in issue <n> of the Journal, which is scheduled to appear mid <Month YYYY>. The deadline for submission of a complete draft is <Friday, Month DD, YYYY>, but the sooner you can get us a draft the better, and the more likely we'll be able to get your article into issue <n>. 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). 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, that would be great.
Proposal Rejected
We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <insert topic/title> has not been accepted for publication. The Editorial Committee determined that it was not an appropriate match for the audience, mission, or scope of the Code4Lib Journal. [optional - insert comment here 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 the editors at journal@code4lib.org in the future with a new or revised proposal.
