[CODE4LIB] Systems Librarian Position at The College of New Jersey

[Edward M. Corrado]

Hello all,

The College of New Jersey is currently seeking candidates to fill a
12-month, tenure-track Systems Librarian position at TCNJ Library (My
former position).  The URL for the job description/details can be found at:

http://delphi.tcnj.edu:8500/test/Employment/show_job.cfm?jobid=6303&category=Academic%2FFaculty%20Positions

For more information, please contact Mr. Marc Meola, Chair, Systems
Librarian Search Committee, by email only at [EMAIL PROTECTED]

Sincerely,

Edward M. Corrado

Re: [CODE4LIB] Open Library API

[Cloutman, David]

That may very well have been the problem. Whatever it was, after I had fixed 
some other bugs, the json_encode function produced strings for hashes that 
worked perfectly well with the API. As is often the case, the problem was user 
error.


-Original Message-
From: Code for Libraries on behalf of Posthumus, Etienne
Sent: Fri 6/6/2008 12:56 AM
To: CODE4LIB@LISTSERV.ND.EDU
Subject: Re: [CODE4LIB] Open Library API

David wrote:

>The problem is that for the two programming languages I use, Java and
> PHP the variable name key~ and $key~ is illegal, and I believe that is
> the case for most programming languages. Thus, in this PHP class (an its
> Java analog) would fail at compile / parse time:

> Note that
> $query = json_encode(array('key~'=>'\/about\/*'));

> will not be parsed through the API, and results in an error message.


Hi David

In the PHP example that you gave, try changing it to:

$query = json_encode(array('key~'=>'/about/*'));

The slashes in that string gets escaped by the JSON ecoder. If you already 
escape them before encoding, it gets double-escaped to look like this:
{"key~":"\\\/about\\\/*"}
That is probably why you  got an error message from the API.

I don't think that this is an issue in almost all programming languages.  The 
point is that you don't want to name any variables 'key~' but this is just a 
string key in an associative array (or HashMap or dict whatever your 
programming language calls it).

regards,

Etienne Posthumus
TU Delft Library


Email Disclaimer: http://www.co.marin.ca.us/nav/misc/EmailDisclaimer.cfm

Re: [CODE4LIB] refworks developer documentation?

[Jonathan Rochkind]

This is indeed the documentation I was looking for, thanks Ere!

I don't know if RefWorks offers any additional API; I doubt it, but I
don't really know (it certainly would be nice), but what I was looking
for was indeed this.

Jonathan

Eric Lease Morgan wrote:

On Jun 6, 2008, at 3:38 AM, Ere Maijala wrote:


Official documentation: 



This documentation seems to describe write operations. No? Does
RefWorks have an API for reading?

--
Eric Lease Morgan
University of Notre Dame

(574) 631-8604



--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu

Re: [CODE4LIB] refworks developer documentation?

[Eric Lease Morgan]

On Jun 6, 2008, at 3:38 AM, Ere Maijala wrote:


Official documentation: 



This documentation seems to describe write operations. No? Does
RefWorks have an API for reading?

--
Eric Lease Morgan
University of Notre Dame

(574) 631-8604

Re: [CODE4LIB] Open Library API

[Posthumus, Etienne]

David wrote:

>The problem is that for the two programming languages I use, Java and
> PHP the variable name key~ and $key~ is illegal, and I believe that is
> the case for most programming languages. Thus, in this PHP class (an its
> Java analog) would fail at compile / parse time:

> Note that
> $query = json_encode(array('key~'=>'\/about\/*'));

> will not be parsed through the API, and results in an error message.


Hi David

In the PHP example that you gave, try changing it to:

$query = json_encode(array('key~'=>'/about/*'));

The slashes in that string gets escaped by the JSON ecoder. If you already 
escape them before encoding, it gets double-escaped to look like this:
{"key~":"\\\/about\\\/*"}
That is probably why you  got an error message from the API.

I don't think that this is an issue in almost all programming languages.  The 
point is that you don't want to name any variables 'key~' but this is just a 
string key in an associative array (or HashMap or dict whatever your 
programming language calls it). 

regards,

Etienne Posthumus
TU Delft Library

Re: [CODE4LIB] refworks developer documentation?

[Ere Maijala]

Jonathan,

Official documentation: 

Sample code from our MetaLib implementation at

and Voyager at
.

--Ere

Jonathan Rochkind wrote:

Does anyone know where, if anywhere, I find documentation on the ways to
send references to RefWorks for importing?

Not having any luck on their website. I know I've seen it before
though.  I remember there were a variety of formats and methods you
could send things to RefWorks for an import. Must be documentation
somewhere?  I bet some code4libber has done this before.

Jonathan

--
Jonathan Rochkind
Digital Services Software Engineer
The Sheridan Libraries
Johns Hopkins University
410.516.8886
rochkind (at) jhu.edu




--
Ere Maijala (Mr.)
IT Research Specialist
The National Library of Finland
P.O.Box 26 (Teollisuuskatu 23)
FI-00014 University of Helsinki
FINLAND

ere.maijala(@)helsinki.fi
Tel. +358 9 191 44260