This should be called `nbopenrefine`!

[choldgraf]

Just a thought - there's nothing binder-specific about this proxy except for the postBuild scripts etc, right? It's just a server extension that somebody could install on their jupyter server locally to? IMO that could be separated from the idea of "openrefine" on binder. Then it would be "just another jupyter extension that also works on Binder" and we could put an example in binder-examples. just a thought :-)

[betatim]

But I worked so hard to come up with the funny name :-/

It is correct though that this is yet another notebook extension - yane :)

[choldgraf]

Haha I actually love the name - but what if that's what the binder-examples repo was called?!?!

[choldgraf]

or you could create another openrefineder repo and I can just fork it for binder-examples and give you a shout-out :-)

[betatim]

I think the way to go is to create a nbopenrefineproxy repo, that contains the server extension (no binder) and then have openrefineder that uses it. That setup would mimic more closely how others would use this in their repositories.

[choldgraf]

Yep, that's exactly what I was imagining