Ingest XQuery workspaces to MarkLogic

[sastafford]

As a user
I want to TITLE
So that I can share Query Console workspaces with other developers

Routinely, I want to share a bunch of xquery snippets with customers and have that show up automatically in a qc workspace. This would be a really neat feature for starters.

/project
/src
/test
/xqy
/qconsole
/
query1.xqy
query2.js
:

[rjrudin]

Scott - where do those get ingested into? The app-services database? I agree, this sounds like a nice feature, I just don't know where they should go yet.

[rjrudin]

Also, I think "/data" is a good standard top-level directory in a project structure for holding version-controlled data files that aren't part of the runtime for an application. How about "/data/qc-workspaces" as a directory?

[TammyHale]

Do you see this as being different from the import/export workspace functionality in qconsole? If not, we could re-use MarkLogic server code in Modules/MarkLogic/appservices/qconsole/qconsole-mode.xqy. Applicable functions might be: export-workspace, import-workspace, clone-workspace, etc.

[rjrudin]

I hadn't thought about how best to export the workspace documents - or when a user would do it.

At least for importing them, the main requirement is that we don't impose any new requirements - e.g. an XDBC server - on the developer's application. Ideally it can be done via an XCC call to port 8000 server, which now exposes an XDBC interface.

[rjrudin]

This is now in ml-javaclient-util