Code4Lib Journal Email Templates - Revision history

DataGazetteer at 22:29, 8 February 2024

2024-02-08T22:29:13Z

Samato at 04:14, 15 April 2023

2023-04-15T04:14:16Z

Samato: clarifying article ready to review login steps

2023-04-15T04:13:32Z

clarifying article ready to review login steps

Samato: Added "article ready for review" template

2023-04-09T23:09:10Z

Added "article ready for review" template

Samato at 19:16, 5 February 2023

2023-02-05T19:16:24Z

Samato: new link to article submission form

2023-02-05T19:14:44Z

new link to article submission form

Samato: /* Submission Acknowledgement */ no longer using demographic form as use was uneven and no longer have access to results.

2022-11-11T02:59:10Z

‎Submission Acknowledgement: no longer using demographic form as use was uneven and no longer have access to results.

Samato: removed reference to journal@code4lb.org

2022-10-09T22:21:07Z

removed reference to journal@code4lb.org

Samato: removed reference to journal@code4lib.org

2022-10-09T22:18:33Z

removed reference to journal@code4lib.org

Samato: removed reference to journal@code4lib.org

2022-10-09T22:17:57Z

removed reference to journal@code4lib.org

← Older revision		Revision as of 22:29, 8 February 2024
Line 28:		Line 28:
	Remember, for consideration for the <nth> issue, please submit proposals, abstracts, or draft articles via the [https://forms.gle/2U8yV6TeG4ep8o6w5 Submission Form] no later than Friday, <Month DD, YYYY>.		Remember, for consideration for the <nth> issue, please submit proposals, abstracts, or draft articles via the [https://forms.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.		Send in a submission. Your peers would like to hear what you are doing.

@@ Line 125: / Line 125: @@
 NOTE: this login will take you to a generic profile page. Please do not change anything on this page.
-.  Once you have successfully logged in, visit the proof for your article: https://journal.code4lib.org/?p={put article number here}&preview=true
+.  Once you have successfully logged in, visit the proof for your article: https://journal.code4lib.org/?p={put_article_number_here}&preview=true
 .  PLEASE don't change the password or share beyond your co-authors.

@@ Line 123: / Line 123: @@
 username:  author
 pass:  {put current password here}
-.  visit the proof for your article: https://journal.code4lib.org/?p={put article number here}&preview=true
+.  Once you have successfully logged in, visit the proof for your article: https://journal.code4lib.org/?p={put article number here}&preview=true
 .  PLEASE don't change the password or share beyond your co-authors.
-−
-−
 == Call-for-Editors ==

@@ Line 107: / Line 107: @@
 Thanks for considering us, and please do not hesitate to submit a new or revised proposal in the future.
 </pre>
 == Call-for-Editors ==

@@ Line 10: / Line 10: @@
 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 via the [https://docs.google.com/forms/d/1wKMNdbQS2kbZIu_d0DzX9yucrhT-BfU4g-GIWx0o3z4/edit 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.
+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 via the [https://forms.gle/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:
@@ Line 26: / Line 26: @@
 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 submit proposals, abstracts, or draft articles via the [https://docs.google.com/forms/d/1wKMNdbQS2kbZIu_d0DzX9yucrhT-BfU4g-GIWx0o3z4/edit Submission Form] no later than Friday, <Month DD, YYYY>.
+Remember, for consideration for the <nth> issue, please submit proposals, abstracts, or draft articles via the [https://forms.gle/2U8yV6TeG4ep8o6w5 Submission Form] no later than Friday, <Month DD, YYYY>.
 Send in a submission.  Your peers would like to hear what you are doing.

@@ Line 5: / Line 5: @@
 Post to the [[Code4Lib Journal Publicity Venues]].
-<pre>
 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 by Friday, <Month DD, YYYY>.  When submitting, please include the title or subject of the proposal in the subject line of the email message.
+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 via the [https://docs.google.com/forms/d/1wKMNdbQS2kbZIu_d0DzX9yucrhT-BfU4g-GIWx0o3z4/edit 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:
@@ Line 26: / Line 26: @@
 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 proposals, abstracts, or draft articles to https://journal.code4lib.org/submit-proposal no later than Friday, <Month DD, YYYY>.
+Remember, for consideration for the <nth> issue, please submit proposals, abstracts, or draft articles via the [https://docs.google.com/forms/d/1wKMNdbQS2kbZIu_d0DzX9yucrhT-BfU4g-GIWx0o3z4/edit Submission Form] no later than Friday, <Month DD, YYYY>.
 Send in a submission.  Your peers would like to hear what you are doing.
@@ Line 32: / Line 32: @@
 Code4Lib Journal Editorial Committee
 == Submission Acknowledgement  ==

@@ Line 38: / Line 38: @@
 <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>
 == Submission Acknowledgement with Request for CC-BY Affirmation ==

@@ Line 60: / Line 60: @@
 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
+technology in libraries? Please respond to me with the additional
-the additional information requested.
+information requested or to ask any additional questions.
-You may also contact the editors at journal@code4lib.org if you have
+We look forward to hearing from you.
-any additional questions.  We look forward to hearing from you.
 </pre>

@@ Line 49: / Line 49: @@
 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.
+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>

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