JAMS Quick Look

[justinsalamon]

From #2:

JAMS Quick Look: "Text editors" versus "specialized tools"

There are loads of json editors out there, and some even accept schema! Check out http://jeremydorn.com/json-editor/ (https://github.com/jdorn/json-editor) I bet it wouldn't be hard to fork that one to do dynamic namespace validation as well.

So the main question here is how/should we provide convenience tools for (batch)editing jams files (outside the python API)

[bmcfee]

Pondering this a bit more:

I like the idea of building this out as a flask-based web service, for a couple of reasons:

• being web-based will make it easy to deploy and extend to a general-purpose music annotation tool. we can still run it locally, of course.
• we already have stable python code for dynamic namespace validation, which could be accessed through a rest api. I don't see any sense in trying to rebuild that client-side in javascript and maintaining separate codebases.
• The schema files can still be used to populate a form editor automatically.

This maybe ought to get farmed out as a separate project though. It seems complex enough that it shouldn't impact the release cycle of the core jams library.

[bmcfee]

This might be nice to have up in time for ismir2015, if we want to show it off at the LBD. Anyone feel up to it?

I'm thinking something pretty simple that renders annotations on top of a peaks.js display.

[justinsalamon]

I probably don't have cycles for this right now, but just wanted to note that I agree this should probably be farmed out as a separate project.

[urinieto]

I will be able to help, but after I write my msaf LBD paper :/

On Mon, Sep 21, 2015 at 11:56 AM, Justin Salamon notifications@github.com
wrote:

I probably don't have cycles for this right now, but just wanted to note
that I agree this should probably be farmed out as a separate project.

—
Reply to this email directly or view it on GitHub
#19 (comment).

[bmcfee]

Hah. I'd suggest making it a hamr project, but i just realized that i'm skipping hamr due to flights.

[ejhumphrey]

Actually, at the risk of biting off more than I can chew, I'm in need of
(a) contributing something meaningful to this project again and (b) a MMH
project this Saturday, soooo ... I'm in!
On Sep 21, 2015 9:40 PM, "Brian McFee" notifications@github.com wrote:

Hah. I'd suggest making it a hamr project, but i just realized that i'm
skipping hamr due to flights.

—
Reply to this email directly or view it on GitHub
#19 (comment).

[bmcfee]

👍

[bmcfee]

dash might be a quick way to get something running for this.

[bmcfee]

I think #93 basically implements this in the form of notebook rendering.

We could maybe roll up a little flask app that loads a jam and prints out its repr_html, but that seems overkill / unlikely to be used.

OTOH, once jupyterlab launches, I'm all in favor of making an extension so that jams files can be smartly rendered in the file browser. This might have to be written in javascript though, see the dev guides.

Otherwise, can we close this one out?

[bmcfee]

Note: if we do want to go the direction of jupyterlab extensions (written in javascript), it might be best to postpone until after #178 / #92 , so that the schema is directly accessible from js land.