{"id":1105,"date":"2010-03-23T01:05:43","date_gmt":"2010-03-23T01:05:43","guid":{"rendered":"http:\/\/jodischneider.com\/blog\/?p=1105"},"modified":"2010-03-23T01:05:43","modified_gmt":"2010-03-23T01:05:43","slug":"code4lib-journal-a-reminisce","status":"publish","type":"post","link":"https:\/\/jodischneider.com\/blog\/2010\/03\/23\/code4lib-journal-a-reminisce\/","title":{"rendered":"Code4Lib Journal: A Reminisce"},"content":{"rendered":"

The Code4Lib Journal<\/a> published issue 9 today. It’s a bittersweet day for me, because today also marks the end of my editorship on the Journal. I helped found the Journal, thinking when I signed on that I could just do a little copyediting. Along the way, I’ve taken a turn at many tasks (regrettably, I postponed taking a turn at Coordinating Editor too long).<\/p>\n

The Journal published issue 1 in December 2007, but work started in April that year. From the beginning, Jonathan Rochkind<\/a> served as a moving force. His post “Code4Lib journal idea revival?<\/a>” ((April 11, 2007 to Code4Lib listserv)) generated a number of responses, in part because he made it sound so easy:<\/p>\n

So pretty much all we would need is:<\/p>\n

1) An editorial committee or whatever. [Maybe some people imagined some
\nmore ‘revolutionary’ egalitarian type of community process, but I figure
\nkeep it simple, and an editorial committee seems simple, and also
\nprovides some people who have explicitly taken responsibility for
\ngetting things done.]
\n2) A place to host it. [maybe some kind of “institutional repository”
\nsoftware would be cool, but in a pinch seems to me a WordPress
\ninstallation would do. Keep things simple and do-able and good enough is
\nmy motto. I’m sure one of our institutions would donate server
\nspace\/cycles for a WordPress installation for such a journal. ]
\n3) Maybe a wiki would be nice for editorial commitee discussions.
\n4) Maybe a simple one page description of the mission of the journal and
\nwhat the journal is looking for in articles. The editorial committee can
\nwork on that on the hypothetical wiki.
\n5) Some articles. The editorial committee can solicit some for the first
\n‘issue’.<\/p>\n

Step 6: Profit! I mean, some e-published articles. No profit, sorry.\n<\/p><\/blockquote>\n

After that post, 10 of us<\/a> stepped forward to decide how to get the Journal off the ground<\/a>. It surprised me how easy some things were: hosting (thanks ibiblio<\/a>!), getting an ISSN, finding a sysadmin (the incomparable Jonathan Brinley<\/a>)…<\/p>\n

I spoke at Code4Lib2008, my first Code4Lib conference, due to Jonathan Brinley’s interest in sharing our publishing methods and Jonathan Rochkind’s encouragement. While we looked at other systems, we chose WordPress as a platform, for its simplicity and its customizability. Jonathan Brinley had put in a proposal to Code4Lib2008 to talk about the Journal’s customizations ((The customizations are documented<\/a> on the Code4Lib wiki, part of a category about the Code4Lib Journal<\/a>.)) He graciously shared the podium with me and Ed Corrado to co-present “The Making of the Code4Lib Journal<\/a>”<\/p>\n

<\/embed><\/p>\n

Since then, the Journal has gone CC-BY (thanks to DOAJ’s<\/a> prodding and to qualify for the SPARC Europe Seal for Open Access Journals<\/a>) and agreed to indexing in EBSCO. We’ve published numerous articles (73 + 9 editorials, if I’ve got the count right), from authors on at least 3 continents. All in all, a great first couple years!<\/p>\n

While I’m sad to be leaving the Journal, I’m delighted to have been a part of it. A strong Editorial Committee, with new blood in the form of 5 new editors, makes it easier to pull back from this project. As Tom Keays said when introducing issue 7<\/a>: Code4Lib Journal, Long May You Run!<\/p>\n","protected":false},"excerpt":{"rendered":"

The Code4Lib Journal published issue 9 today. It’s a bittersweet day for me, because today also marks the end of my editorship on the Journal. I helped found the Journal, thinking when I signed on that I could just do a little copyediting. Along the way, I’ve taken a turn at many tasks (regrettably, I […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[58,182],"tags":[177,242],"class_list":["post-1105","post","type-post","status-publish","format-standard","hentry","category-future-of-publishing","category-scholarly-communication","tag-code4lib","tag-code4lib-journal"],"_links":{"self":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/1105","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/comments?post=1105"}],"version-history":[{"count":14,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/1105\/revisions"}],"predecessor-version":[{"id":1119,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/posts\/1105\/revisions\/1119"}],"wp:attachment":[{"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/media?parent=1105"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/categories?post=1105"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jodischneider.com\/blog\/wp-json\/wp\/v2\/tags?post=1105"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}