Difference between revisions of "Code4Lib Journal Email Templates"

From Code4Lib
Jump to: navigation, search
(Call for proposals: spaces)
m (Call for proposals)
 
(24 intermediate revisions by 6 users not shown)
Line 3: Line 3:
 
== Call for proposals ==
 
== Call for proposals ==
  
Change <angle brackets> and post to the [[Code4Lib Journal Publicity Venues]].
+
Post to the [[Code4Lib Journal Publicity Venues]].
  
 
<pre>
 
<pre>
Line 16: Line 16:
 
To be included in the <nth> issue, which is scheduled for publication
 
To be included in the <nth> issue, which is scheduled for publication
 
in mid <Month YYYY>, please submit articles, abstracts, or proposals at
 
in mid <Month YYYY>, please submit articles, abstracts, or proposals at
http://journal.code4lib.org/submit-proposal or to journal@code4lib.org  
+
https://journal.code4lib.org/submit-proposal or to journal@code4lib.org  
by <Friday, Month DD, YYYY>.  When submitting, please include the title   
+
by Friday, <Month DD, YYYY>.  When submitting, please include the title   
 
or subject of the proposal in the subject line of the email message.
 
or subject of the proposal in the subject line of the email message.
  
Line 27: Line 27:
 
   hypothetical)
 
   hypothetical)
 
* Technology projects (failed, successful, or proposed), including  
 
* Technology projects (failed, successful, or proposed), including  
   how they were done and challenges faced
+
   how they were done and the challenges faced
 
* Case studies
 
* Case studies
 
* Best practices
 
* Best practices
Line 41: Line 41:
 
middle ground between blog posts and articles in traditional refereed
 
middle ground between blog posts and articles in traditional refereed
 
journals.  Where appropriate, we encourage authors to submit code
 
journals.  Where appropriate, we encourage authors to submit code
samples, algorithms, and pseudo-code. For more information, visit
+
samples, algorithms, and pseudo-code. For more information, visit C4LJ’s Article Guidelines or browse articles from the earlier issues published on our website: http://journal.code4lib.org.
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,
 
Remember, for consideration for the <nth> issue, please send proposals,
abstracts, or draft articles to journal@code4lib.org no later than  
+
abstracts, or draft articles to https://journal.code4lib.org/submit-proposal
<Friday, Month DD, YYYY>.
+
no later than Friday, <Month DD, YYYY>. (Use journal@code4lib.org if
 +
sending attachments.)
  
 
Send in a submission.  Your peers would like to hear what you are doing.
 
Send in a submission.  Your peers would like to hear what you are doing.
Line 58: Line 57:
  
 
<pre>
 
<pre>
Thank you for submitting a proposal to the Code4Lib Journal. We  
+
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 us at journal@code4lib.org if you have additional questions.
appreciate your participation in the Code4Lib community. The editors  
+
 
have received your proposal and should be in touch with you in 2-4
+
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
weeks regarding its appropriateness for publication in C4LJ. We will  
+
</pre>
notify you if we need additional information to make this decision.  
+
 
Please feel free to contact us at journal@code4lib.org if you have  
+
== Submission Acknowledgement with Request for CC-BY Affirmation ==
additional questions.
+
 
 +
<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 us at journal@code4lib.org if you have additional questions.
 
</pre>
 
</pre>
  
Line 74: Line 79:
 
In order to help the editors determine if your proposal is appropriate  
 
In order to help the editors determine if your proposal is appropriate  
 
for this publication, could you share more details about the intended  
 
for this publication, could you share more details about the intended  
audience for the the article and how it will address issues surrounding  
+
audience for the article and how it will address issues surrounding  
technology in libraries? Please respond to journal@code4lib.org with  
+
technology in libraries? Please respond to journal@code4lib.org with  
 
the additional information requested.
 
the additional information requested.
  
 
You may also contact the editors at journal@code4lib.org if you have  
 
You may also contact the editors at journal@code4lib.org if you have  
any additional questions. We look forward to hearing from you.
+
any additional questions. We look forward to hearing from you.
 
</pre>
 
</pre>
  
Line 104: Line 109:
 
We hope to publish your article in issue <n> of the Journal, which is
 
We hope to publish your article in issue <n> of the Journal, which is
 
scheduled to appear mid <Month YYYY>.  The deadline for submission
 
scheduled to appear mid <Month YYYY>.  The deadline for submission
of a complete draft is <Friday, Month DD, YYYY>, but the sooner you
+
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
 
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
 
get your article into issue <n>.  Upon receipt of the draft, I will
Line 117: Line 122:
 
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). 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
 
We look forward to seeing a complete draft and hope to include it in
Line 130: Line 136:
  
 
<pre>
 
<pre>
We regret to inform you that your recent proposal to the Code4Lib
+
We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <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 - comment about why it's not appropriate]
Journal for an article about <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 - comment about why it's not appropriate]
+
  
For more information about the mission of the Code4Lib Journal,  
+
For more information about the mission of the Code4Lib Journal, please see http://journal.code4lib.org/mission/.
please see http://journal.code4lib.org/mission/.
+
  
Thanks for considering us, and please do not hesitate to contact the
+
Thanks for considering us, and please do not hesitate to submit a new or revised proposal in the future.
editors at journal@code4lib.org in the future with a new or revised
+
proposal.
+
 
</pre>
 
</pre>
 +
 +
== Call-for-Editors ==
 +
 +
The Code4Lib Journal (http://journal.code4lib.org/) is looking for volunteers to join its editorial committee.  Editorial committee members work collaboratively to produce the quarterly Code4Lib Journal.  Editors are expected to:
 +
 +
* Read, discuss, and vote on incoming proposals.
 +
* Volunteer to be the assigned editor or second reader for specific proposals.
 +
    ** Assigned editors work with the author(s) to make sure the article is as strong as possible, that the copy is clean, and deadlines are met.  They also enter the article into WordPress, making sure the formatting is okay, all images and tables look good, etc.
 +
    ** Second readers act as a second set of eyes for the assigned editor.
 +
* Read and comment on any other article that interests you.
 +
* Volunteer for administrative tasks and projects as they crop up.
 +
* Take a turn as Coordinating Editor for an Issue.  The Coordinating Editor shepherds the issue through its life cycle.
 +
 +
We seek an individual who is self-motivated, organized and able to meet deadlines; is familiar with ideas and trends in the field; and has an interest in the mechanics of writing.  There is a sometimes significant time commitment involved; expect to set aside ten or more hours a month.
 +
 +
It sounds like a lot of work, but it's also a lot of fun (if editing is your idea of fun).
 +
 +
Intrigued?  Please send a letter of interest by xxxxxxxxxxxxx to journal_at_code4lib.org. Your letter should address these questions:
 +
 +
1) What is your vision for the Code4Lib Journal? Why are you interested in it?
 +
 +
2) What types of libraries have you worked with?
 +
 +
3) What are your areas of expertise and/or research?
 +
 +
4) How can you contribute to the Code4Lib Journal, i.e. what do you have to offer?
 +
 +
We encourage people who have previously applied and who are still interested to re-apply. We have had to turn down a lot of highly-qualified people in the past due to the large number of applications.
 +
 +
If you have any questions, contact us by email at journal_at_code4lib.org or ask any member of the editorial committee (listed at http://journal.code4lib.org/editorial-committee). We plan to make decisions about additional editors by XXXXXXXX.
  
 
[[Category: Code4Lib Journal]]
 
[[Category: Code4Lib Journal]]

Latest revision as of 23:08, 1 July 2019

See also Code4Lib_Journal_Deadlines

Call for proposals

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
https://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 the 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 earlier issues published on our website: http://journal.code4lib.org.

Remember, for consideration for the <nth> issue, please send proposals,
abstracts, or draft articles to https://journal.code4lib.org/submit-proposal
no later than Friday, <Month DD, YYYY>.  (Use journal@code4lib.org if
sending attachments.)

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 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 us at journal@code4lib.org if you have additional questions.

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 

Submission Acknowledgement with Request for CC-BY Affirmation

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 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 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). 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, that
would be great.

Proposal Rejected

We regret to inform you that your recent proposal to the Code4Lib Journal for an article about <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 - 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 submit a new or revised proposal in the future.

Call-for-Editors

The Code4Lib Journal (http://journal.code4lib.org/) is looking for volunteers to join its editorial committee. Editorial committee members work collaboratively to produce the quarterly Code4Lib Journal. Editors are expected to:

  • Read, discuss, and vote on incoming proposals.
  • Volunteer to be the assigned editor or second reader for specific proposals.
   ** Assigned editors work with the author(s) to make sure the article is as strong as possible, that the copy is clean, and deadlines are met.  They also enter the article into WordPress, making sure the formatting is okay, all images and tables look good, etc.
   ** Second readers act as a second set of eyes for the assigned editor.
  • Read and comment on any other article that interests you.
  • Volunteer for administrative tasks and projects as they crop up.
  • Take a turn as Coordinating Editor for an Issue. The Coordinating Editor shepherds the issue through its life cycle.

We seek an individual who is self-motivated, organized and able to meet deadlines; is familiar with ideas and trends in the field; and has an interest in the mechanics of writing. There is a sometimes significant time commitment involved; expect to set aside ten or more hours a month.

It sounds like a lot of work, but it's also a lot of fun (if editing is your idea of fun).

Intrigued? Please send a letter of interest by xxxxxxxxxxxxx to journal_at_code4lib.org. Your letter should address these questions:

1) What is your vision for the Code4Lib Journal? Why are you interested in it?

2) What types of libraries have you worked with?

3) What are your areas of expertise and/or research?

4) How can you contribute to the Code4Lib Journal, i.e. what do you have to offer?

We encourage people who have previously applied and who are still interested to re-apply. We have had to turn down a lot of highly-qualified people in the past due to the large number of applications.

If you have any questions, contact us by email at journal_at_code4lib.org or ask any member of the editorial committee (listed at http://journal.code4lib.org/editorial-committee). We plan to make decisions about additional editors by XXXXXXXX.