Hey David, In MarkLogic, you'll hear folks say "Documents are Like Rows". There's some detail in http://developer.marklogic.com/inside-marklogic that discusses this:
Here's a quote: When modeling data for MarkLogic, think of documents more like rows than tables. In other words, if you have a thousand items, model them as a thousand separate documents not as a single document holding a thousand child elements. This is for two reasons: First, locks are managed at the document level. A separate document for each item avoids lock contention. Second, all index, retrieval, and update actions happen at the fragment level. When finding an item, retrieving an item, or updating an item, that means it's best to have each item in its own fragment. The easiest way to accomplish that is to put them in separate documents. Of course MarkLogic documents can be more complex than simple relational rows, because XML is a more expressive data format. One document can often describe an entity (a manifest, a legal contract, an email) completely. I'd recommend you look at building an Information Studio collector that takes your single large XML file and breaks it into appropriate individual XML document during ingestion. Justin Makeig's Tunage<http://developer.marklogic.com/code/tunage> application does something similar with the iTunes XML file. And... the Tunage app itself is actually an built with Application Builder and as such, seems like a good example for you to base your work on. Best, Eric Eric Bloch [email protected]<mailto:[email protected]> On Jan 20, 2011, at 4:18 PM, David Epstein wrote: Hello, I have a single large XML file produced by a desktop application and am considering using Marklogic Application Builder to create a better search interface than the desktop application provides. This project is primarily for personal use. The examples in the Application Builder Developer guide, I believe, concern multiple documents each with the same metadata. Instead, I have a single file composed of sections of different kinds of "nodes" and then sections of different kinds of "edges". In standard relational database terms, I have several tables of items and several tables of association lists all strung together in a single file. Are there examples of using Application Builder to panel data in such a format? Essentially, I would like to start with a node, and then search through all the association lists to find connecting nodes and arrange them according to type. -david _______________________________________________ General mailing list [email protected]<mailto:[email protected]> http://developer.marklogic.com/mailman/listinfo/general
_______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
