<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Open Access Publishing with Drupal</title>
	<atom:link href="http://journal.code4lib.org/articles/5913/feed" rel="self" type="application/rss+xml" />
	<link>http://journal.code4lib.org/articles/5913</link>
	<description></description>
	<lastBuildDate>Tue, 21 May 2013 06:29:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: iLibrarian &#187; 16 New Library Tech Stories You May Have Missed</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4693</link>
		<dc:creator>iLibrarian &#187; 16 New Library Tech Stories You May Have Missed</dc:creator>
		<pubDate>Tue, 22 Nov 2011 18:09:45 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4693</guid>
		<description><![CDATA[[...] Open Access Publishing with Drupal &#8211; Code4Lib [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Open Access Publishing with Drupal &#8211; Code4Lib [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thomas Dodson</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4319</link>
		<dc:creator>Thomas Dodson</dc:creator>
		<pubDate>Mon, 07 Nov 2011 16:30:00 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4319</guid>
		<description><![CDATA[Great article.  I&#039;ve found drupal to be a great platform for literary journals as well.  I started my journal, Printer&#039;s Devil Review (http://pdrjournal.org) using OJS but found it&#039;s workflow and submission process much too cumbersome for a non-peer-reviewed publication. Building a submission form with drupal using the webform module, however, was a snap. I also have a lot more control over the look and feel of the journal through customizing the &quot;journalcrunch&quot; theme.

Readers also may be interested in Yana, an open source project we&#039;re working on at Harvard designed to provide OA journals with a template for mobile apps using existing content: http://osc.hul.harvard.edu/yana.

We&#039;ve tested it with OJS and drupal and it&#039;s very easy on both platforms to simply give Yana the URL of the RSS feed for your current issue, for example, and instantly have it work as a web app.]]></description>
		<content:encoded><![CDATA[<p>Great article.  I&#8217;ve found drupal to be a great platform for literary journals as well.  I started my journal, Printer&#8217;s Devil Review (<a href="http://pdrjournal.org" rel="nofollow">http://pdrjournal.org</a>) using OJS but found it&#8217;s workflow and submission process much too cumbersome for a non-peer-reviewed publication. Building a submission form with drupal using the webform module, however, was a snap. I also have a lot more control over the look and feel of the journal through customizing the &#8220;journalcrunch&#8221; theme.</p>
<p>Readers also may be interested in Yana, an open source project we&#8217;re working on at Harvard designed to provide OA journals with a template for mobile apps using existing content: <a href="http://osc.hul.harvard.edu/yana" rel="nofollow">http://osc.hul.harvard.edu/yana</a>.</p>
<p>We&#8217;ve tested it with OJS and drupal and it&#8217;s very easy on both platforms to simply give Yana the URL of the RSS feed for your current issue, for example, and instantly have it work as a web app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iLibrarian &#187; Open Access Publishing with Drupal</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4306</link>
		<dc:creator>iLibrarian &#187; Open Access Publishing with Drupal</dc:creator>
		<pubDate>Sun, 06 Nov 2011 23:37:41 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4306</guid>
		<description><![CDATA[[...] by Nina McHale, Assistant Systems Administrator at the Arapahoe Library District, on the topic of Open Access Publishing with Drupal. If you&#8217;re considering moving to an open access model for your journal, you&#8217;ll want to [...]]]></description>
		<content:encoded><![CDATA[<p>[...] by Nina McHale, Assistant Systems Administrator at the Arapahoe Library District, on the topic of Open Access Publishing with Drupal. If you&#8217;re considering moving to an open access model for your journal, you&#8217;ll want to [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nina</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4245</link>
		<dc:creator>Nina</dc:creator>
		<pubDate>Tue, 01 Nov 2011 21:35:53 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4245</guid>
		<description><![CDATA[Hey, Cary! Thanks for your comments. My co-editor Tabby Farney and I just discovered OpenPublish-we worked it into our LITA Forum presentation about this project :)-and it&#039;s something that we will seriously consider. Roman Chyla was very kind when I emailed him out of the blue about the future of the E-Journal module, and it was my hope that through writing this, we could either convince him to go to 7 or that we might possibly find a group of interested folks who might be willing to help maintain it, with his help and/or blessing.]]></description>
		<content:encoded><![CDATA[<p>Hey, Cary! Thanks for your comments. My co-editor Tabby Farney and I just discovered OpenPublish-we worked it into our LITA Forum presentation about this project :)-and it&#8217;s something that we will seriously consider. Roman Chyla was very kind when I emailed him out of the blue about the future of the E-Journal module, and it was my hope that through writing this, we could either convince him to go to 7 or that we might possibly find a group of interested folks who might be willing to help maintain it, with his help and/or blessing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: &#8230;welcome to Elias&#8217; blog! &#187; Blog Archive &#187; Open Access Week 2011</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4244</link>
		<dc:creator>&#8230;welcome to Elias&#8217; blog! &#187; Blog Archive &#187; Open Access Week 2011</dc:creator>
		<pubDate>Tue, 01 Nov 2011 21:05:49 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4244</guid>
		<description><![CDATA[[...] But just as I finish with this post, a new alternative has been published in the Code4Lib Journal Open Access Publishing with Drupal … anyway, I guess different choices for different [...]]]></description>
		<content:encoded><![CDATA[<p>[...] But just as I finish with this post, a new alternative has been published in the Code4Lib Journal Open Access Publishing with Drupal … anyway, I guess different choices for different [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cary Gordon</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4239</link>
		<dc:creator>Cary Gordon</dc:creator>
		<pubDate>Tue, 01 Nov 2011 15:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4239</guid>
		<description><![CDATA[You have pointed out a key issue in the adoption of a complex, modular free content management system. Drupal 7, at its release, had 469 core contributors, a bit less than one tenth of one percent of its user base. Obviously, that percentage of users for the E-Jounal module -- used on about 40 sites -- would be more or less nobody.

The E-Jounal module was created and is occasionally maintained by a CERN fellow who is also teaching and pursuing his PhD. I would venture to say that this represented a huge effort on his part. He has no obligation to maintain it forever. As it has had no updates in almost a year, it is, for practical purposes, abandoned.

This means that users of the module have three choices:
* They can use the module in its current release as long as they like.
* They can find a way of assembling the modules functionality using other modules -- presumably more generic modules.
* They can provide resources to keep the module up-to-date and to port it to Drupal 7.

If they chose the latter, and I hope that at least one of them does, it could be done several ways:
- Provide a coder to contribute and possibly take over the module.
- Offer resources to the original contributors to resume work on the module.
- Hire a Drupal shop to update and/or maintain the module.

It might be advantageous to start a Drupal group (on http://groups.drupal.org/) so that you can collaborate with other module users. You can also get an idea of who might be using the module by noting who has posted issues in the issue queue. Once you have a group, you can see if any of them are willing to commit resources, as well.

One alternative might be to investigate the OpenPublish profile, which I believe contains most of the features of Ejournal, with the possible exception of peer review. OpenPublish is a collection of core, contrib and custom modules that is sponsored by and supported (commercially) by a major Drupal shop. OpenPublish is supported for Drupal 7.]]></description>
		<content:encoded><![CDATA[<p>You have pointed out a key issue in the adoption of a complex, modular free content management system. Drupal 7, at its release, had 469 core contributors, a bit less than one tenth of one percent of its user base. Obviously, that percentage of users for the E-Jounal module &#8212; used on about 40 sites &#8212; would be more or less nobody.</p>
<p>The E-Jounal module was created and is occasionally maintained by a CERN fellow who is also teaching and pursuing his PhD. I would venture to say that this represented a huge effort on his part. He has no obligation to maintain it forever. As it has had no updates in almost a year, it is, for practical purposes, abandoned.</p>
<p>This means that users of the module have three choices:<br />
* They can use the module in its current release as long as they like.<br />
* They can find a way of assembling the modules functionality using other modules &#8212; presumably more generic modules.<br />
* They can provide resources to keep the module up-to-date and to port it to Drupal 7.</p>
<p>If they chose the latter, and I hope that at least one of them does, it could be done several ways:<br />
- Provide a coder to contribute and possibly take over the module.<br />
- Offer resources to the original contributors to resume work on the module.<br />
- Hire a Drupal shop to update and/or maintain the module.</p>
<p>It might be advantageous to start a Drupal group (on <a href="http://groups.drupal.org/" rel="nofollow">http://groups.drupal.org/</a>) so that you can collaborate with other module users. You can also get an idea of who might be using the module by noting who has posted issues in the issue queue. Once you have a group, you can see if any of them are willing to commit resources, as well.</p>
<p>One alternative might be to investigate the OpenPublish profile, which I believe contains most of the features of Ejournal, with the possible exception of peer review. OpenPublish is a collection of core, contrib and custom modules that is sponsored by and supported (commercially) by a major Drupal shop. OpenPublish is supported for Drupal 7.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Open Access Publishing with Drupal In January&#8230; &#171; InfoDoc MicroVeille</title>
		<link>http://journal.code4lib.org/articles/5913/comment-page-1#comment-4213</link>
		<dc:creator>Open Access Publishing with Drupal In January&#8230; &#171; InfoDoc MicroVeille</dc:creator>
		<pubDate>Mon, 31 Oct 2011 15:56:43 +0000</pubDate>
		<guid isPermaLink="false">http://journal.code4lib.org/?p=5913#comment-4213</guid>
		<description><![CDATA[[...] : http://journal.code4lib.org/articles/5913      [...]]]></description>
		<content:encoded><![CDATA[<p>[...] : <a href="http://journal.code4lib.org/articles/5913" rel="nofollow">http://journal.code4lib.org/articles/5913</a>      [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
