[Using Sakai] [Building Sakai] Citations Improvements - soliciting comments to SLIB-121

[Adam Marshall]

> -----Original Message-----
> From: James Eng [mailto:jimeng at umich.edu]
> Sent: 20 April 2012 14:31
> To: Adam Marshall
> Cc: John Leasia; sakai-dev; sakai-user
> Subject: Re: [Building Sakai] Citations Improvements - soliciting comments to
> SLIB-121
> 
> Hi Adam,
> 
> I can't address most of the specific issues at the moment, but it
> seems to me that many of the improvements mentioned on that page would
> be valuable to everyone. Even for things that are very specific to
> Oxford might best be handled by implementing optional hooks in trunk
> of ciations and then seperating the Oxford-specific bits into a local
> adapter. That way, you avoid having to do lots of patching on sakai
> code, and others get advantage of your improvements. I suggest you
> create Sakai JIRA tickets soon for as much of this as possible
> (without the Oxford-only parts).

Wilco! We're interviewing at the start of may and have a 8 week project, I'm not over-estimating how much will be achieved though as starting with Sakai involves a somewhat steep learning curve.

adam

> 
> Just my opinion.
> 
> Jim
> 
> 
> 
> On 4/20/12, Adam Marshall <adam.marshall at oucs.ox.ac.uk> wrote:
> > This all looks good to me.
> >
> > You know we added openURL support to CH? I take it you are building on
> that
> > work?
> >
> > Also have you considered allowing
> >
> > 1/ the lists to be reordered?
> >
> > 2/ the default limit of 10 citations per page to be increased?
> >
> > 3/ allowing HTML headings & paragraphs to be added cf evaluations tool?
> >
> > 4/ allow reading lists to be tracked by Site Stats
> >
> > We have a short project over the summer to make improvements to the
> tool.
> > Here's a list of items to tackle (you wont have access to our internal
> > Jira):
> >
> > http://wiki.oucs.ox.ac.uk/weblearn/ImprovedReadingLists
> >
> > adam
> >
> > From: sakai-dev-bounces at collab.sakaiproject.org
> > [mailto:sakai-dev-bounces at collab.sakaiproject.org] On Behalf Of John
> Leasia
> > Sent: 19 April 2012 17:44
> > To: sakai-dev; sakai-user
> > Subject: [Building Sakai] Citations Improvements - soliciting comments to
> > SLIB-121
> >
> > Hello -
> > IU and UMich have talked about making some changes to the UI for the
> > Citations tool/helper in Resources (an optional feature that helps create
> > lists of references pulled from outside repositories). A Jira -
> > https://jira.sakaiproject.org/browse/SLIB-121 - has been created to track
> > the work, and a draft of some of the UI changes are detailed there. We'd
> > appreciate any comments/suggestions to the Jira in the next couple weeks
> > from those using Citations as we'd like to get going on making the changes.
> > This is part of a re-look at citations in general, which includes some
> > back-end bug fix work and improvements to handle Open URL1.0 format
> and
> > multi-selection, and other things listed below.
> > 1. The Citations Helper module doesn't handle new lines, as listed in the
> > specification - http://www.refman.com/support/risformat_fields_02.asp
> >
> > This has been referenced in an existing JIRA issue, SAK-19154.
> >
> > How to handle long fields
> >
> > If the information following any one tag is more than 70 characters long, it
> > is allowable (though not necessary) to insert a carriage return/line feed at
> > the end of 70 characters, and continue on the next line.
> >
> >
> > Entries are handled currently on a line by line basis. It's possible the
> > code could be modified to allow for tag entries continuing onto the next
> > line, and this is something that would allow for better compatibility with
> > EndNote files. Of course this would require some testing to ensure that it
> > wouldn't break existing functionality.
> >
> > 2. SAK-20590 Import from RIS (EndNote): First citation from text file is
> > always missing
> >
> > This issue has been fixed and was related to a carriage return line feed
> > issue. Files saved on a Windows machine were putting empty characters
> into
> > the line, causing the string matching to fail. The data is now cleaned
> > before processing.
> >
> > 3. SAK-20589 SAK-18495 and SAK-20588 have been edited to reflect the fact
> > that they are duplications of an existing (and fixed) bug, SAK-16091.
> >
> > 4. SAK-16091 is fixed in version 2.7.2, however it still needs its patch
> > made into an upgrade script.
> >
> >