Do you mean what's the mime-type for RIS files? (RIS != "Refworks", I forget what RIS stands for, but it's used by many reference managers, and may have originally been invented by EndNote?)
There isn't a registered MIME type for RIS. Googling around, it looks like the preferred one is: application/x-Research-Info-Systems
(Guess that's what RIS stands for?)
Or wait, you mean the Refworks callback? You can actually give Refworks a variety of types of content in the callback. Are you giving it that weird marc-formatted-a-certain-way-in-a-textfile format? I doubt there's any mime type for that other than text/plain.
Jonathan
________________________________________
From: Code for Libraries [[log in to unmask]] On Behalf Of Bill Dueber [[log in to unmask]]
Sent: Wednesday, February 24, 2010 9:47 AM
To: [log in to unmask]
Subject: Re: [CODE4LIB] HathiTrust API
OK, I've added links for RIS and Endnote, but it turns out I *don't* know
what mime type to use for Refworks. When actually talking to refworks with
their callback system, I need to send it as text/plain, and I've been unable
to track down what the preferred type is.
Anyone know?
On Wed, Feb 24, 2010 at 3:45 AM, Ed Summers <[log in to unmask]> wrote:
> Nice work Bill! I particularly like your use of the <link> element to
> enable auto-discovery of these resources:
>
> <link rel="canonical" href="/Record/005550418">
> <link rel="alternate" type="application/marc" href="/Record/005550418.mrc"
> >
> <link rel="alternate" type="application/marc+xml"
> href="/Record/005550418.xml" >
> <link rel="alternate" href="/Record/005550418.rdf"
> type="application/rdf+xml" />
>
> Did you shy away from adding the RIS and Refworks formats as links
> because it wasn't clear what MIME type to use?
>
> I'd be interested in helping flesh out the RDF a bit if you are interested.
>
> //Ed
>
> On Tue, Feb 23, 2010 at 4:07 PM, Bill Dueber <[log in to unmask]> wrote:
> > Many of you just saw Albert Betram of the University of Michigan
> Libraries
> > talk at #c4l10 about HathiTrust APIs available to anyone interested. One
> of
> > these, the BibAPI, was formed mostly by me on the basis of "Imaginary
> User
> > Needs," not actual use cases. Anyone who has use cases that aren't
> > well-covered by the existing BibAPI should drop me a line and let me
> know.
> >
> > This is also a good time to mention that catalog.hathitrust.org (and
> > mirlyn.lib.umich.edu) support some limited export facilities by adding
> an
> > extension to a record URL. SO...
> >
> >
> > http://catalog.hathitrust.org/Record/005550418 Link to the
> Hathitrust
> > page
> > http://catalog.hathitrust.org/Record/005550418.marc MARC21 binary
> > http://catalog.hathitrust.org/Record/005550418.xml MARC-XML
> > http://catalog.hathitrust.org/Record/005550418.ris RIS tagged format
> > http://catalog.hathitrust.org/Record/005550418.refworks Refworks tagged
> > format
> > http://catalog.hathitrust.org/Record/005550418.rdf Perfunctory RDF
> > document
> >
> > I'd love help getting the RDF more fleshed out, btw.
> >
> > Again -- if you need anything else, or if you, say, wrap a nice jQuery
> > plugin around the BibAPI, please let me know!
> >
> > -Bill-
> >
> >
> >
> > Bill Dueber
> > Library Systems Programmer
> > University of Michigan Library
> >
>
--
Bill Dueber
Library Systems Programmer
University of Michigan Library
|