Aha, thanks, I understand now. Aside from the mime type (aka 'internet content
type') issue, I'm curious, if you're already generating RIS anyway... and
RefWorks can take RIS.... what reasons do you have for sending RefWorks the
Refworks Tagged Format, instead of just sending it the RIS you already have?
I'm curious becuase I've been kind of turning around a game plan for this in
the back of my head too.
Now as far as a content type for the weird Refworks Tagged Format... I doubt
there is one. If there isn't one, you could just make one up yourself with x-?
application/x-refworks-tagged-format ? That's what I'd do. Use the most
'official'/standard name for the format you can find ("Refworks Tagged
Format"), to make it more likely someone else will come up with the same thing,
and you won't collide with something someone else comes up with that is
something different, and just slap an x- in front.
________________________________________
From: Code for Libraries [[email protected]] On Behalf Of Bill Dueber
[[email protected]]
Sent: Wednesday, February 24, 2010 10:38 AM
To: [email protected]
Subject: Re: [CODE4LIB] HathiTrust API
OK, slow it down J-Rock. :-)
I'm looking for a MIME type for Refworks Tagged Format, which is NOT RIS.
It's a different tagged format. The three most common tagged formats are
RIS, Refworks, and Endnote-style-Refer. It's the Refworks one I need help
with.
And I gave up on the marc-lines-pretend-format stuff; I just send Refworks
their preferred tagged format now, I just don't know what MIME type to use.
On Wed, Feb 24, 2010 at 9:57 AM, Jonathan Rochkind <[email protected]> wrote:
> 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 [[email protected]] On Behalf Of Bill
> Dueber [[email protected]]
> Sent: Wednesday, February 24, 2010 9:47 AM
> To: [email protected]
> 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 <[email protected]> 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 <[email protected]> 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
>
--
Bill Dueber
Library Systems Programmer
University of Michigan Library
