.@mls Watching #MTLvPHL on #MLSSeasonPass I have a simple request -- if the ball is in play, give us the wide view. Save the close-ups for dead balls and replays -- and get back to the action on time!
When you use @MarkLogic's Hub Central to build entities, it automatically creates a TDE template with a view for you. If you see "SQL-TABLENOTFOUND -- Unknown table", here's what's happening. https://t.co/BRwZYC8V4o
Looking for a @MarkLogic developer with strong #semantics skills to work with one of my clients 15-20 hours per week. If that's you, please get in touch!
I'm looking to hire a @marklogic developer -- if you'd like to work with a small but supportive team doing interesting work, let me know! https://t.co/V8k4nfccmc
I learned a little wrinkle today about how @MarkLogic's sem.sparqlUpdate function handles write locks. Thought it might be helpful to others, so I wrote it up: https://t.co/s1aifKE2vJ
In @apachenifi, EvaluateJsonPath is great but requires a static path. A client need to pull a value from JSON where the name of the property is in an attribute, so I wrote up how to do it. https://t.co/gM09tBlRl2
Version 1.9.1.6 of @MarkLogic's NiFi Connector has been released with some good bug fixes. Looking forward to getting this version into use at my clients!
You have big plans for what you can do with @MarkLogic. You've already got a great team of developers. So why do you need 4V Services? https://t.co/pXCjdNVzlY
Great news! @usairforce awards @MarkLogic prime contractor position to support the Advanced Battle Management Systems.
Read the press release now to learn more:
https://t.co/E9oDuXWqlz
#ABMS#AirForce#PublicSector
I just taught my auto-mechanic-in-training daughter to convert between decimal and binary.
And then how to do it on a calculator, because who does that on paper? :)
Proud to announce that the U.S. Air Force has awarded @MarkLogic Prime Contractor Position on the Advanced Battle Management Systems (ABMS). Data integration is critical in the $950m effort towards a unified force. https://t.co/nfCWMLe8NN
@mazihe @MarkLogic My preference is that if the data will end up in JSON, it might as well start there. And using JS makes it easier to bring my clients up to speed on how to work with what my team builds.
Working with @MarkLogic, it's natural to use XQuery for XML and JavaScript for JSON, but sometimes it's useful to cross the boundaries. I wrote up some notes on using XQuery to work with JSON: https://t.co/DwbMiQaUUs
@mazihe @MarkLogic I've done more with JSON using XQuery than I have XML using JS, but I think you're probably right. The JS NodeBuilder is less intuitive (to me) than json:object() => map:with(...)
@mazihe @MarkLogic All else being equal, I'd say to use JS for JSON and XQuery for XML, but the fact is all else is not equal. JS is a much more widely known language. For most clients, using JavaScript makes staffing easier.