Re: [Simile-Widgets] "consider running Babel yourself" - how??

[David Karger]

Hi Mark. Babel is running at http://service.simile-widgets.org/babel .
On what page are you finding the text you quote?
On 4/11/2013 8:42 AM, Mark Wilkinson wrote:
> "Note about Babel: The Babel service is not guaranteed to run as a
> public service indefinitely. If you rely on Babel translation services
> (RDF/XML, N3, Excel, an Exhibit page, KML, JPEG, TSV importers),
> consider running Babel yourself, downloading the transformed data if
> you don't need to actively transform the original, or maintaining the
> original data in a format that does not depend on Babel."
>
> There's definitely a missing hyperlink over the "consider running
> babel yourself". I've searched for days, and there is no
> documentation anywhere on how to do this. Downloading and compiling
> the code, sure, I can do that. But there is no user-instructions for
> what to do with it. The readme in the source code says "for more
> information go to..." and provides to a hyperlink that doesn't work.
> No user-documentation beyond the bare-bones readme in the source tree
> either. The /babel/ page can be reverse-engineered to figure out what
> all of the form-fields are, and to discover the /translate/
> endpoint... and that's fine too, but that isn't exactly "running it
> yourself".
>
> I'm trying to not overload your public resource, but you're making it
> very difficult for me to be kind ;-) ;-)
>
> Cheers all!
>
> M
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "SIMILE Widgets" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to simile-widget...@googlegroups.com.
> To post to this group, send email to simile-...@googlegroups.com.
> Visit this group at http://groups.google.com/group/simile-widgets?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

[Mark Wilkinson]

On Sun, 21 Apr 2013 17:25:31 +0200, David Karger <kar...@mit.edu> wrote:

> Hi Mark. Babel is running at http://service.simile-widgets.org/babel .
> On what page are you finding the text you quote?

I know where it's running, that wasn't my question (though the API is not
described anywhere, I figured it out by tracing the messages in my browser
so that I could access the public service from code)

The problem is that on this page:
http://www.simile-widgets.org/wiki/Data you say that I should "consider
running it [myself]" (quoted below). Unfortunately, there are no
instructions on how to do so. No installation instructions, and no API
description.

...makes it pretty difficult to follow your advice! ;-)

M

[Leopold]

Since several days the service

http://service.simile-widgets.org/babel/

is down. Any idea if and when it would come up again. Did any of those posting here already succeed in running it on your own server? any return on experience to share here?

thanks

On Thursday, 16 May 2013 16:03:51 UTC+2, Ben Ransford wrote:

On Monday, April 22, 2013 2:01:11 AM UTC-4, Mark Wilkinson wrote:

The problem is that on this page:  
http://www.simile-widgets.org/wiki/Data  you say that I should "consider  
running it [myself]" (quoted below).  Unfortunately, there are no  
instructions on how to do so.  No installation instructions, and no API  
description.  

 

+1 for making it easy to run babel locally.  Speaking for myself, I have a script that runs my group's BibTeX file through the babel web service [1] to generate a JSON file for Exhibit to display -- but at the moment my script fails for reasons that may be outside my control.

I checked out https://github.com/zepheira/babel just now, but am not enough of a Maven maven to grok the build system (reactors?  lifecycle phases?).  Is there an easy way to convert a BibTeX file to an Exhibit JSON file from the command line?

Current issue aside, thanks for making Exhibit!

-ben

[1] FTR, the meat of my script is:

$ curl --insecure --show-error --fail -F raw-text=@mybibfile.bib -o mybibfile.js 'https://service.simile-widgets.org/babel/translator?reader=bibtex&writer=bibtex-exhibit-json&mimetype=default'

which worked when I last checked a few weeks ago but now returns HTTP 400.