<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" version="2.0">
  <channel>
    <title>IdeaScale : The repository should provide authoring support</title>
    <description />
    <item>
      <title>The repository should provide authoring support</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>&lt;table width="100%"&gt;
&lt;tr&gt;&lt;td width="100" valign="top"&gt;
&lt;div id="IdeaScale_Vote" align="center"&gt;&lt;div style="padding:5px;font-size:2em"&gt;3&lt;/div&gt;&lt;div&gt;&lt;a href="http://jiscrepository.ideascale.com/akira/dtd/2274-784"&gt;Vote&amp;nbsp;On&amp;nbsp;Idea&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/td&gt;&lt;td valign="top"&gt;
&lt;div&gt;This is a refinement of the current top-rated idea, based on one of my blog posts on research repository systems.&lt;br/&gt;&lt;br/&gt;Authoring support should include version control, collaboration, possibly publisher liaison, and be integrated with the repository deposit process. It does need object disclosure control, see below. Version control would support ideas, working drafts, pre-prints, working papers, submitted drafts undergoing editorial changes, and refereed and published versions. Collaboration support would need to include support for multiple authors contributing document parts, and assembly of these into larger parts and eventually “complete” drafts. It should also include some kind of multiple author checkout system for updates, something like CVS or SVN, maybe a bit WIKI-like. It must support a wide choice of document editor, eg Word, OpenOffice.org, LaTeX etc (I don’t know how to combine this with the previous requirement!).&lt;br/&gt;
&lt;/div&gt;&lt;div id="IdeaScale_IdeaFooter"&gt;&lt;span style="border-right: 1px solid silver; margin:0 10px 0 0; padding: 0 5px 0 0; color: #666;"&gt;&lt;a id="DiscussionTopic_2274" href="http://jiscrepository.ideascale.com/akira/dtd/2274-784"&gt;Comments (4)&lt;/a&gt;&lt;/span&gt;&lt;span id="DiscussionTopicTag_2274"&gt;Category/Tags : &lt;a href="/akira/ideafactory.do?discussionID=3164"&gt;Repository functions (10)&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="border-left: 1px solid silver; margin:0 10px 0 0; padding: 0 5px 0 0; color: #666;" id="DiscussionTopicFlag_2274"&gt;&amp;nbsp;&amp;nbsp;  Mark as &lt;a href="javascript:ajaxLink('DiscussionTopicFlag_2274', '/akira/flagDiscussionTopic.do?mode=duplicate&amp;discussionID=3164&amp;ID=2274')"&gt;duplicate&lt;/a&gt;&lt;/span&gt;&lt;div style="margin-top:3px;" id="DiscussionTopicComment_2274"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</description>
      <pubDate>Mon, 14 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by o.stephens</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>I can't support stuff that says 'the repository should do x'. Can we start phrasing this type of thing like:&lt;br/&gt;&lt;br/&gt;The availability of research via Open Access would increase if the same systems that provide Open Access also provided, or were integrated with, tools which support the authoring process&lt;br/&gt;&lt;br/&gt;I'd vote yes to this!</description>
      <pubDate>Thu, 17 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by c.rusbridge</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>Something weird happened here; I was given an opportunity to vote on this (which I thought I already had... it was at 2 and I voted up and it dropped to 1!</description>
      <pubDate>Thu, 17 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by o.stephens</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>Also lost my comment/rant which was:&lt;br/&gt;&lt;br/&gt;I can't support stuff that says 'the repository should do x'. Can we start phrasing this type of thing like:&lt;br/&gt;&lt;br/&gt;The availability of research via Open Access would increase if the same systems that provide Open Access also provided, or were integrated with, tools which support the authoring process&lt;br/&gt;&lt;br/&gt;I'd vote yes to this wording!&lt;br/&gt;</description>
      <pubDate>Thu, 17 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by Andy McGregor</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>Sorry about this. I changed the categories of some posts and this meant that the comments got lost somehow. I have told the developers about this and they have identified the bug and a fix should be put into the production system tomorrow. Hopefully that should mean that comments will reappear.</description>
      <pubDate>Thu, 17 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by ian.stuart</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>This is a variation of what Peter Murry-Rust proposed back in '07: google-docs mixed with a CRIS.&lt;br/&gt;&lt;br/&gt;I've been promoting this idea for a while too :)</description>
      <pubDate>Fri, 18 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
    <item>
      <title>Comment by forkel</title>
      <link>http://jiscrepository.ideascale.com/akira/dtd/2274-784</link>
      <description>my experience is, that feature requests of this sort are exactly the ones which end up in the "users didn't know what they wanted bin" (i'm a developer). they basically mean, let us keep on working exactly the way we worked before and just have everything in the repository. while this may be the optimal solution, i don't think it will work. so if we have to make the users adapt their ways, why not point them to apps like google docs right away?</description>
      <pubDate>Fri, 18 Jul 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://jiscrepository.ideascale.com/akira/dtd/2274-784</guid>
    </item>
  </channel>
</rss>

