Today I was privileged to present to the 6th International Congress of Technological Innovation, Innovatics 2016, organized by Duoc UC Libraries, Library of Santiago, and University of Chile Libraries. The conference was simultaneously translated in English and Spanish. To aid the translators, I wrote out the text of my presentation for them to review. Below is the text as it was intended to be presented; I did diverge in a few places mostly based on what others said earlier in the conference.
Welcome to the Disruptive Library Technology Jester. From here you can browse the musings and visions of a library technologist as he walks the fine line between the best of the library profession on one side and the best of technology on the other.
Index Data posted an announcement on their blog about how I will be joining them next month. Confirmed! I'll be working on the open source library service platform that was announced by EBSCO last month, and more specifically in a role as an organizer and advocate for people participating in the project. It feels like my career has been building to this role. And it also means getting re-engaged in the OLE project; I was part of the design effort in 2008-2009 and then drifted away as professional responsibilities took me in other directions. In the executive overview of the OLE design report, we said:
Alan Stanley taught me this trick at an Islandora Camp a few years ago, and when trying to remember it this morning I messed up one critical piece. So I’ll post it here so I have something to refer back to when I need to do this again.
The Drupal Devel module includes a menu item for executing arbitrary PHP code on the server. (This is, of course, something you want to set permissions on very tightly because it can seriously wreck havoc on your day if someone uses it to do bad things.) Navigate to
/devel/php on your Islandora website (with the Devel module enabled), and you’ll get a nice, big
≶textarea> and an “Execute” button:
Nuts. I added and committed a directory to my Git repository when the directory itself was another separate Git repository. Now Git thinks it’s some sort of submodule, but it doesn’t know how to deal with it:
$ git submodule update No submodule mapping found in .gitmodules for path 'blah'
And worse, Git won’t let me remove it:
$ git rm blah error: the following submodule (or one of its nested submodules) uses a .git directory: blah (use 'rm -rf' if you really want to remove it including all of its history)
So what to do? This:
$ git rm --cached blah $ git add blah
In my case I had a situation where there were several Git repositories-inside-a-repository, so I wanted a way to deal with them all:
$ for i in `find . -type d -name .git -print | sed 's#/.git##'`; do > echo $i > rm -rf $i/.git > git rm --cached $i > git add $i > done
(Be careful not to run this
find command at the root of your Git repository, of course, or else you will effectively destroy its usefulness as a git repo. )