Computer Weekly has a snippet describing a watch developed at Bristol University that uses GPS to provide the wearer with a description of, and directions to, the nearest pub.
MARC (MAchine Readable Cataloguing?) is old, comprehensive, and there are CPAN modules for it - including conversion to and from XML. It seems to record everything that a library could need for all types of holding. However it is way too complicated for what I need and not very easy to understand (at least for me) as the codes describing the types of records are numeric, e.g. 100 indicates the author and 245 indicates the title.
Back to googling then....
Oh well, as everybody seems to be making resolutions to use the journal system more so I think I'll join in. One objective this year is to finish off something that I've been playing with for years now. What I want to do is create something that will let me catalogue all my books/CDs/etc. I first started trying to do this in the dim and distant MS days with Access but I never got it to the point where it either worked o.k. or I was happy with what it did. So this year I'm going to do it using Perl/XML/PostgreSQL or similar.
Add new books as I acquire them
Search by title, author
Print pretty catalogues
Produce simple lists that can be downloaded to the Palm
Have fun doing it.
Learn more about XML.
Learn more about DBI.
Make it extensible.
Make it future proof.
I've been putting some thoughts together at work about how we apply operating system patches - for the HP-UX systems for example you can do some clever things:
1. Get the current patch state and ftp it to HP
2. Go onto their site and analyse what patches you are missing (and any dependencies etc)
3. Collect all these patches together and download them to your server
4. Apply them all in one go
Of course you can specify what sort of patches you are interested in. For example 'CRITICAL' patches are those that can cause data loss or system failures - and these are the ones we are most interested in.
Of course in the perl world CPAN does something similar - you can get a report showing, for all the packages you have installed, if there is a newer version available. But if you want to go further you have to start looking at the README/CHANGES for each individual package (and hope that what the author wrote makes some sense to enable you to decide whether to upgrade or not). And this can be a lot of work if you haven't upgraded for a long time. (And we try to minimise change frequency for our production systems.)
I started wondering if something could be done for CPAN to enable new version to be classified so that you can see if you need to install them - everything from releases that fix serious bugs through minor bugs to added functionality releases.