For your needs, you might want to look at the MarkLogic extension to xmlsh. http://www.xmlsh.org/ModuleMarkLogic
One reason I developed this was the same as yours, to be able to explore MarkLogic while learning. The latest QueryConsole and explore are a great tool and I use them a lot, but some things are just easier as a command line. Including searching through directory listings. FYI the implementation of the "list" command makes use of the URI collection if available. its very nice to be able to pipe this through your favorite search program like grep. ml:list | grep -i myDoc Hard to do this with a GUI For fun you can see how the list command is implemented in xquery. http://xmlsh.svn.sourceforge.net/viewvc/xmlsh/extensions/marklogic/src/org/xmlsh/marklogic/list.xsh?revision=668&view=markup Prizes to the one who spots the bug I just spoted while reading this ! ----------------------------------------------------------------------------- David Lee Lead Engineer MarkLogic Corporation [email protected] Phone: +1 650-287-2531 Cell: +1 812-630-7622 www.marklogic.com<http://www.marklogic.com/> This e-mail and any accompanying attachments are confidential. The information is intended solely for the use of the individual to whom it is addressed. Any review, disclosure, copying, distribution, or use of this e-mail communication by others is strictly prohibited. If you are not the intended recipient, please notify us immediately by returning this message to the sender and delete all copies. Thank you for your cooperation. From: [email protected] [mailto:[email protected]] On Behalf Of Todd Gochenour Sent: Monday, February 27, 2012 3:08 PM To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] (1) Canceling XQuery requests, (2) Exploring Resource Hierarchy (2) cts:uri-match() doesn't make the utility of Query Console Explore any better. I haven't applied this collection strategy idea I just had to my data yet, but I hope that the collection links displayed in the Explore table will provide navigation to the filtered list of documents in that collection. Otherwise using collections won't work either. The biggest advantage I see to XQuery is that as a declarative language it just works. It reduces the problem to a simple declaration of what I want in a result. I don't need to think imperatively. The details of how to produce a result are left up to the platform. The complexity of the system is reduced significantly. The tools which surround the XQuery need to be just as simple. I haven't read all the FAQ's and tutorials that exist for MarkLogic so many of my questions will likely be RTFM. I jumped in with preconceived notions (learned from oXygen and eXistDB and xDB and XMLSpy and such) about what I need in a development environment to optimize my ability to experiment with XQuery analysis of large data sets. A would hope the Explore view would let me explore a three dimensional hierarchy, not just page through a two dimensional table of 3500 pages. That being said, eXistDB doesn't have a way to cancel a query in their explorer so I very much appreciate MarkLogic providing for that option.
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
