[OPEN-ILS-DEV] Export to RefWorks in Evergreen

[David Fiander]

You definitely need to be able to turn it off and on. The default
should probably be "off".

You also need to be able to set the refworks server name, since most
Canadian universities don't go to the refworks.com server, but use the
Canadian server, refworks.scholarsportal.info.

In the perfect world, individual users would have a personal
configuration option, but that's easily handled by some of the other
ways of integrating refworks.

- David

On Fri, Jun 19, 2009 at 5:28 PM, Mike Rylander<mrylander at gmail.com> wrote:
> On Fri, Jun 19, 2009 at 5:14 PM, Mike Rylander<mrylander at gmail.com> wrote:
>> On Fri, Jun 19, 2009 at 5:11 PM, Bill Erickson<erickson at esilibrary.com> wrote:
>>>
>>>
>>> On Thu, Jun 18, 2009 at 7:39 AM, Warren Layton <warren.layton at gmail.com>
>>> wrote:
>>>>
>>>> On Wed, Jun 17, 2009 at 11:50 PM, Mike Rylander <mrylander at gmail.com>
>>>> wrote:
>>>>>
>>>>> Hrm ... is the purpose of <VENDOR> to tell RefWorks what sort of
>>>>> system the data is coming from, or to tell them which of their clients
>>>>> is using the service?
>>>>
>>>> I believe it's the latter (for instance, see the link to RefWorks at
>>>> http://mirlyn2-beta.lib.umich.edu/Record/001376273 ).
>>>>
>>>> I've attached a slightly modified patch that doesn't append "+Evergreen"
>>>> to <VENDOR> and just uses the org's fullname (with spaces replaced with '+'
>>>> chars). That is likely more appropriate, at least from RefWorks' point of
>>>> view.
>>>
>>> Couple comments... We need to turn "Export to RefWorks" into a DTD entity
>>> for i18n purposes (says the lazy i18n-er).
>>
>> Done while integrating the patch.
>>
>>>  We also need to consider
>>> displaying (or suppressing display) of the link by org unit setting or some
>>> other easily toggled switch in the javascript.
>>>
>>
>> Not done ... but I'm inclined to leave it in, rather than out, by
>> default for now.  Thoughts, anyone?
>>
>>> Other than that, the patch looks great to me.
>>>
>>
>> I also wrapped the code that does the actual attribute setting in a
>> test to make sure the element's there, which it won't be in craftsman,
>> for now.
>>
>>> wlayton++
>>
>> Indeed.
>>
>> Not committed yet.  Waiting on an updated xslt.
>>
>
> Now ... it's committed.  Thanks a ton, Warren.  Very nice work.
>
> I'm not going to backport this from trunk to 1.6 just yet so we can
> have some discussion on the ability to turn it on or off, and what the
> default should be.
>
> --
> Mike Rylander
>  | VP, Research and Design
>  | Equinox Software, Inc. / The Evergreen Experts
>  | phone:  1-877-OPEN-ILS (673-6457)
>  | email:  miker at esilibrary.com
>  | web:  http://www.esilibrary.com
>