Difference between revisions of "Code4Lib Journal Email Templates"

From Code4Lib
Jump to: navigation, search
(Proposal Accepted)
(Proposal Accepted)
Line 22: Line 22:
 
As a member of the Code4Lib Journal editorial committee, I will be your contact for your proposed Code4Lib Journal article, and will work with you to get the article ready for publication.
 
As a member of the Code4Lib Journal editorial committee, I will be your contact for your proposed Code4Lib Journal article, and will work with you to get the article ready for publication.
  
We hope to publish your article in issue <#> of the Journal, which is scheduled to be published on <insert date here>. We need to see a complete draft of the article is <deadline for draft>, but the sooner you can get us a draft the better, the more likely we'll be able to get your article into that issue. Once we see a complete draft, we may work with you on additional requested edits before the Editorial Committee will consider it ready for publication.  Your proposal definitely looks like article we're interested in, but we can only make the final decision to publish when we see a complete draft.  
+
We hope to publish your article in issue <#> of the Journal, which is scheduled to be published on <insert date here>. We need to see a complete draft of the article by <deadline for draft>, but the sooner you can get us a draft the better, the more likely we'll be able to get your article into that issue. Once we see a complete draft, we may work with you on additional requested edits before the Editorial Committee will consider it ready for publication.  Your proposal definitely looks like article we're interested in, but we can only make the final decision to publish when we see a complete draft.  
  
 
To see what we're looking for, you should consult our author guidelines at: http://journal.code4lib.org/article-guidelines.  
 
To see what we're looking for, you should consult our author guidelines at: http://journal.code4lib.org/article-guidelines.  

Revision as of 21:21, 13 March 2009

See also Code4Lib_Journal_Deadlines

Submission Acknowledgement

Thanks 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 c4lj-articles@googlegroups.com 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 c4lj-articles@googlegroups.com with the additional information requested.

You may also contact the editors at c4lj-articles@googlegroups.com if you have any additional questions. We look forward to hearing from you.


Proposal Accepted

I'm pleased to tell you that the Code4Lib journal is interested in your recent article proposal about <insert topic/title>. Based on your proposal, we are interested in this topic, and would like to see a draft.

<insert any 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.". "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 your proposed Code4Lib Journal article, and will work with you to get the article ready for publication.

We hope to publish your article in issue <#> of the Journal, which is scheduled to be published on <insert date here>. We need to see a complete draft of the article by <deadline for draft>, but the sooner you can get us a draft the better, the more likely we'll be able to get your article into that issue. Once we see a complete draft, we may work with you on additional requested edits before the Editorial Committee will consider it ready for publication. Your proposal definitely looks like article we're interested in, but we can only make the final decision to publish when we see a complete draft.

To see what we're looking for, you should consult our author guidelines at: http://journal.code4lib.org/article-guidelines.

As a final note, we require all authors to agree to 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 are excited about your article, and look forward to seeing a complete draft and including it in the Journal. Thanks for submitting to us, and feel free to contact me directly with any questions.

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. This is likely because 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 c4lj-articles@googlegroups.com in the future with a new or revised proposal.