From rochkind at jhu.edu  Tue Apr 13 18:17:49 2010
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Tue, 13 Apr 2010 18:17:49 -0400
Subject: [Umlaut-general] new feature in SFX service adapter, trunk
Message-ID: <4BC4ED8D.8070604@jhu.edu>

I added a new feature to the Umlaut SFX service adapter, currently 
committed to svn.

It involves SFX "related objects".

If you have "related objects" display turned on in your SFX, then 
previously, when you looked up a citation, full text URLs for other 
"related objects" would also be included in the display.  This was quite 
similar to the way native SFX worked. Sometimes this is quite helpful to 
the user -- when the related object really the same journal after a name 
change, and maybe they had the wrong ISSN or Journal Title for their 
date, or didn't realize the name had changed or think of the name change 
as resulting in a "different" journal. That's all fine.

But in other cases, the "related objects" caused confusion for our users 
locally. Checking on the SFX listserv revealed that other institutions 
felt similarly.

The SFX kb actually records the _nature_ of the relationship for a 
related object, from a small controlled vocabulary.  While the native 
SFX interface does not give you any way to actually control your display 
based on this -- this nature of relationship IS revealed in the SFX API, 
which means the Umlaut interface could.

In the new feature, certain types of "related objects" do NOT have their 
targets shown in  the main Umlaut resolver menu.  These types are: 
"CONTINUES_IN_PART", "CONTINUED_IN_PART_BY", "ABSORBED_IN_PART", and 
"ABSORBED_BY"

Targets provided through that kind of relationship are NOT be in the 
main resolver menu, BUT INSTEAD a title-level link to the related title  
itself is provided in a sidebar "See Also" menu Umlaut provides.That is 
a link to viewing the related title in Umlaut.

Other types of related objects continue to be shown in the main 
listing.  You can customize this list of relationship types with the new 
SFX service adapter "really_distant_relationships" parameter.  It 
defaults to the above four at the moment -- if you want to disable this 
feature entirely, you could set it to the empty array ( that is, "[]") 
in your services.yml.

Here's an example of the new feature in action in our deployed Umlaut:

http://findit.library.jhu.edu/go/1528962


So that's that.  Putting the new feature into sfx.rb was a _bit_ hacky, 
I'm afraid. That sfx.rb code is some of the oldest code in Umlaut, and 
kind of messy, it could use a refactoring someday.

Jonathan

From rochkind at jhu.edu  Mon Apr 26 15:57:43 2010
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Mon, 26 Apr 2010 15:57:43 -0400
Subject: [Umlaut-general] replace prototype with jquery
In-Reply-To: <4BD5EC83.8030401@jhu.edu>
References: <4BD5EC83.8030401@jhu.edu>
Message-ID: <4BD5F037.3050000@jhu.edu>

Nevermind, I figured out my bug! Moving on.

Jonathan Rochkind wrote:
> Hey Scot, if you get this. I'm working experimentally in a branch trying 
> to replace all Prototype code with 'unobtrusive' (as feasible) JQuery 
> code, for a variety of reasons.
>
> So I've gotten to the point of the popup dialogs for the export stuff, 
> which I haven't been using my own install, but which I believe you are 
> using and it works fine?  Except now I can't get it to work even under 
> the old Prototype code (which I wanted to look at to make sure I 
> duplicated functionality appropriately).
>
> Any ideas, does the JS modal window stuff work 'out of the box' as far 
> as you know?
>
> Jonathan
>
>   

From rochkind at jhu.edu  Mon Apr 26 15:41:55 2010
From: rochkind at jhu.edu (Jonathan Rochkind)
Date: Mon, 26 Apr 2010 15:41:55 -0400
Subject: [Umlaut-general] replace prototype with jquery
Message-ID: <4BD5EC83.8030401@jhu.edu>

Hey Scot, if you get this. I'm working experimentally in a branch trying 
to replace all Prototype code with 'unobtrusive' (as feasible) JQuery 
code, for a variety of reasons.

So I've gotten to the point of the popup dialogs for the export stuff, 
which I haven't been using my own install, but which I believe you are 
using and it works fine?  Except now I can't get it to work even under 
the old Prototype code (which I wanted to look at to make sure I 
duplicated functionality appropriately).

Any ideas, does the JS modal window stuff work 'out of the box' as far 
as you know?

Jonathan