Code4Lib Journal WordPress Input Guidelines - Revision history

EricHanson at 19:04, 10 February 2021

2021-02-10T19:04:11Z

2021-02-10T19:03:16Z

2019-04-23T17:12:02Z

‎Bibliographies/Endnotes

2019-04-23T17:11:08Z

2019-04-10T20:17:16Z

2019-04-10T20:15:29Z

2018-04-26T17:12:00Z

Typo

2018-01-23T17:29:46Z

minor edit to fix the url to be used in WP posts for images

2017-07-19T16:08:06Z

2017-07-19T16:05:38Z

@@ Line 206: / Line 206: @@
 # Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
 # Submit URLS to Internet Archives for harvest ([https://gist.github.com/ruthtillman/fa7562989f299e4904c7fb0448d1fc83#file-waybacksubmit-py Wayback Submission Script] )
-# In the article tracking spreadsheet, cut the article rows from the current issue sheet and paste them at the bottom of the "Published" sheet. Delete the empty sheet for the current issue.
+# In the article tracking spreadsheet, cut the article rows from the current issue sheet and paste them at the bottom of the "Published" sheet. Delete current issue sheet now that it is empty.
 # Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
 # Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

@@ Line 206: / Line 206: @@
 # Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
 # Submit URLS to Internet Archives for harvest ([https://gist.github.com/ruthtillman/fa7562989f299e4904c7fb0448d1fc83#file-waybacksubmit-py Wayback Submission Script] )
 # Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
 # Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

@@ Line 136: / Line 136: @@
 ==Bibliographies/Endnotes==
 <!--
 We would like to provide COinS information with every appropriate citation that does not have a publicly accessible url.

@@ Line 136: / Line 136: @@
 ==Bibliographies/Endnotes==
-We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
+<!--
 It appears the COinS generator at  http://generator.ocoins.info/ is no longer in service.  An alternative is [https://www.zotero.org/download/ Zotero's stand alone citation software].
@@ Line 147: / Line 148: @@
 This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.  For an example see the [http://journal.code4lib.org/articles/7922 References section of a published article including coins].
+-->
 ===Endnotes style and HTML coding===
 * Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

@@ Line 92: / Line 92: @@
 If code is attached as a file, follow the directions above for attached images, except:
-* If there is not a folder for the author, create it, according to the guidelines above for images)
+* If there is not a folder for the author, create it, according to the guidelines above for images
 * Create a subfolder under the author's folder for "code".  Insert code files here
 * In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)
 Put all inline code in <code>&lt;pre&gt;</code> tags.
@@ Line 114: / Line 117: @@
 For more  subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f
 ====Ampersand Issues====

@@ Line 99: / Line 99: @@
 ====Code Highlighting====
 If the code is in a supported language, we can do syntax highlighting.
 Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:
@@ Line 118: / Line 114: @@
 For more  subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f
 ====Ampersand Issues====

@@ Line 163: / Line 163: @@
 ==Categories/Tags==
-Posts will have "Uncagetorized" checked by default.  Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues."  Do not check the "Issues" category. We generally do not add tags, except for Conference reviews
+Posts will have "Uncategorized" checked by default.  Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues."  Do not check the "Issues" category. We generally do not add tags, except for Conference reviews
 ==WordPress Buttons==

@@ Line 60: / Line 60: @@
 /public/vhost/c/c4lj/html/media
-in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
+in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. This sort of url will be used in the "<img src>" tag:
-http://journal.code4lib.org/media/issue1/smith/imagename.png
+/media/issue1/smith/imagename.png
 Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)