I’ve spent the morning building a prototype WebObjects app to act as an xml metadata server. I’ve embedded eXistDB into the application, and it created the necessary database files and indices for me.
Then, I wrote a short method to import xml documents from a path (and added the added bonus of importing a whole directory if that was given). 3600+ records in the embedded database.
And boy, is it fast. Queries are almost instantaneous (~100ms typical), but document retrievals are a wee bit slower, increasing linearly with the number of hits. I haven’t added any limits, so you can do a query for something lame like “a” and get the whole database back in one page.
One of the really cool things about eXist is the XPath extensions for fulltext searching. They mimic (using XPath) the stuff that is done in XStreamDB via XQuery.
I can do stuff like:
document(*)//text() &= "*image*"
and eXist will return me any xml document (from it’s entire set of collections) that contains the string “image” somewhere in it (could be in /lom/general/title/langstring/Images Of Bangalore, or /lom/technical/format/image/jpeg, or whatever. It doesn’t care. And, it’s very fast.
I initially sent this as an email to the group, but thought it might serve better on the weblog…
I’ve been playing around with eXist today. Holy crap.
I used Rob’s JUD export script to suck all 3600+ records out of the CAREO JUD (took almost 2 hours to process that), then ran the import function on eXist (took maybe 5 minutes to import them all).
It looks like it’s going to be able to do some pretty freaky stuff, search-wise. I’ve been playing around with some pretty loose XPath queries, and it returns excellent hits, pretty darned fast. It can be slow if I request, say, all documents with the letter “a” in them somewhere, but for normal queries, it’s stinky fast.
With the help of a whole cast of characters, we’ve got our “reference implementation” Pachyderm project server up and running. It’s just a clone of SFMOMA’s Making Sense of Modern Art production server, so we may need to clean out some data and media, but it’s working (apparently) well.
I’ve tried creating a new presentation (a Zoom Screen of an Ansel Adams photo), and the creation process went quite smoothly. I’m having some trouble actually viewing the result, but that’s probably a minor thing.
Thanks to Al Delgado for the tip on this. There’s a big education bloggers shindig in San Francisco November 22-23. Sounds like it will be quite a gathering.
I hadn’t heard of (or if I’ve heard of it, I promptly forgot about it) the EdBloggers Network. K-12 focussed, with colleges of education participating.
I’ll be keeping an eye on this group… (no, not in a scary restraining-order kind of way…)
I participated in the last CanCore conference call (and promptly forgot to post about it. doh.). One of the items that made its way onto the agenda was to discuss my proposal of adding multiple elements in a lom to support thumbnail images and various formats of a single learning object.
Anyway, I’ve captured the conclusion of the group, and appended them to my proposal document.
Long story short: survey says “use the relation element, since it’s part of the LOM already. it ain’t as elegant or as useful as multiple technical elements, but at least it doesn’t break anything.”
MT-Blacklist RULES! I installed version 1.5, and it’s been saving this weblog from hundreds of unsolicited, unwelcome, and unwanted comment spams!
If you run a MT weblog, you REALLY have to install this bad boy. Right now.
Here’s a screenshot of a small, small part of my MT log. This weasel tried several times over the course of a few hours, hammering repeatedly in bursts within seconds of each other (I can only assume it was some kind of software following Google links…)
Back when I was building the “theme engine” for CAREO, everything began to look like themable stuff. I kept saying “Hey, that’s not hard - we can just implement that as a theme in CAREO!”
Everything from a version of the Learning Commons website, to SciQ, to a bunch of other projects, were mocked up (and some even implemented) as themed components in CAREO.
Worked pretty well, and was an awesome test of the flexibility of the theme engine.
I’ve been working on the app that manages workshop registrations here in the Learning Commons, and have been tackling one of the major problems in the current version - people can enter invalid email addresses, and may never even know they did it. They won’t receive confirmation, and can’t receive updates/modifications.
Often, these addresses are trivially incorrect (an errant space, a missing . or whatever).
Anyway, here is the code I whipped up for the app to attempt to verify the email address. It relies on the Java InetAddress class, and does a lookup of the hostname. If there’s a machine at the hostname, I’ll assume it’s correct. (could get fancy and look up only MX records etc… but it’s a start.)
The big Pachyderm 2.0 Kickoff Meeting in San Francisco is just about wrapping up now. It’s been amazing the last couple of days. This group is simply incredible, with representatives from museums, universities, colleges, and the corporate world.
And they all Get it. The energy and excitement in the group is tangible. They are here for the collaboration and the process, not for fame or fortune. It’s awesome.
We’ve broken off into working groups. I’ve been placed into the Software group and the Metadata/Interoperability group.
