If you’re interested in zettelkastens, this might be the meetup for you.
On the agenda:
Using Tinderbox to surface bottom-up emergent data.
How big can our data file (zettelkasten) get? From The Tinderbox Way: Think hundreds and thousands, not tens and hundreds of thousands.
How can we plan ahead, use and curate our Tinderbox files—possibly connect multiple files?—so we don’t outgrow the power and benefits Tinderbox brings to data?
NOTE: We plan on recording this meeting.
Join Zoom Meeting
Meeting ID: 885 065 9900
One tap mobile
+13126266799,8850659900# US (Chicago)
+16465588656,8850659900# US (New York)
Dial by your location
+1 312 626 6799 US (Chicago)
+1 646 558 8656 US (New York)
+1 301 715 8592 US (Germantown)
+1 346 248 7799 US (Houston)
+1 669 900 9128 US (San Jose)
+1 253 215 8782 US (Tacoma)
Meeting ID: 885 065 9900
Find your local number: Zoom International Dial-in Numbers - Zoom
One suggestion in the last meeting (I’m not sure if it came from Steve), was about Tinderbox using some database server.
I’ve superficially read about eXist DB, which is the database engine behind the TEI publisher. It’s a document database based on XML.
Is it a possibility for Tinderbox to have something like a connector to a database of this kind? Would it be advantageous in terms of performance and scalability?
Otherwise, and although TBX is already XML, which permits read access to the data anyways, the capability for simultaneously writing to a document, for example, could potentially open a new world of interoperability.
(Omnioutliner, by the way, already has XSL transformation methods built into its scripting idiom, but I don’t know what is it meant for exactly).