She Wants The World… And a Search Log Analyser!

Just kidding, but I got some details back from Lisa C, and she appears to have some very specialised requirements for her system. I have suggested that it might be better if we work together to develop a “base system” which would include the complete logging functionality, and then she can customise and/or extend the reporting/analysis interface as required.

I think this approach should work quite well, allowing me to collaborate on a logging module, and to refine the database schema, then develop a generic, “useful-across-the-board” analysis interface, which should be capable of being extended easily. Metabase, here I come.

Client Education Library for Information Architects (CELIA)

Aim:
Provide a collection of resources which will help Information Architects to educate potential and existing clients about the importance and relevance of Information Architecture and strategy.

Contents of Collection:

  • Diagrams
  • Quotes
  • Statistics
  • Case Studies/Examples
  • Online Resources

A search facility would be available, allowing you to hunt down certain things, as well as all widgets being categorised carefully and fully browsable. I’d like to be able to give everything a “permanent URL” within the collection as well, so that people can link back to it’s entry, and “reference” their resources properly, thus keeping authors happy(er) about the fact that their work is being used by other people in a relatively generic format.

We have response

Well, I thought they were silent, turns out I just needed to put the idea of CELIA to the whole AIfIA membership to get a response.

After being sparked on by a discussion on the [aifia-members] list, I posted about CELIA and had some reasonable responses. One of them was from James Robertson, of Step Two, an Australian Knowledge Management and CMS company based in Sydney – so he has offered to be a part of it, and this can be Australia’s biggest contribution to the community yet!

webpad Needs Some Love

webpad has been sorely neglected, and it is starting to show. I have a bad feeling that it won’t work on a default install of PHP anymore, and there are a number of reported bugs related to the install and configuration process which have done anything *but* go away with time. I think it is getting close to time that I need to re-write the core code for little-ole webpad, and try to bring things up to scratch.

There are also a number of improvements I would like to make to the system at the same time, but priority one will be to bring all of the existing code up to a certain level, then move forward to a new version.

And so… the requirements (as far as I am concerned) for version 2.1 public are;

  1. Re-write of backend code to standardize style/syntax etc.
  2. Ensure that all code is 100% compatible with a default installation (no register_globals being the big one here)
  3. Switch all of the Blogger.com operations over to using the new, inbuilt XML-RPC functions in PHP, rather than the external library it currently uses.
  4. Ensure that all Blogger.com operations still work (their API has been all over the place, so who knows??)
  5. Iron out any bugs in the install process to ensure that the app can be installed with a minimum of fuss.

With that out of the way, I will then look towards a 3.0 release, which should look something like this;

  1. Inclusion of ODBC, PostgreSQL and possibly Oracle plug-ins for authentication
  2. Streamlined setup/install and user management (*large* improvements planned)
  3. Improved support for authentication methods other than WIXAS
  4. Much better file management (directory creation, renaming, deleting etc)
  5. Integration with Blogger Pro, Radio and MovableType if possible (expanded to include template management and better post management)
  6. Ability to load a file from the filesystem via direct request (i.e. http://webpad/?file=/path/to/file.txt) assuming permissions allow it and it’s within the user’s home dir.
  7. Much better mult-user support
  8. Commercial licenses will attract a modest fee (in the vicinity of $USD15), while personal use will remain free

The Silence of the Asilomarians

After joining the AIfIA (and paying the membership fee), I have been somewhat disappointed with the response I received from the CELIA idea.

I signed up for the IA Library project with AIfIA, and have suggested that perhaps CELIA could be done as a part of that project, but have received no response. Zero. Nada. Zip.

I think Karl and I are going to start planning it out a little, hopefully I will be able to knock together a simple-ish system which can handle the stuff we would be working with, and that would allow us to get started. I think it’s a really valuable thing, and something that perhaps isn’t as important is the US, because IA is more established, but it sure is important here, where I have met all of about 3 people who even took a punt on what Information Architecture is!

Putting blosxom to REST

The plan with these helper scripts that I am writing is that blosxom will be able to operate in a “REST-like” environment. This means that directing a browser to a URL like /blogging/blogger.com/ should load the blog entries in that directory (if it is within a defined blog-tree).

It’s working so far, and I have added in the option of linking to ‘rss.xml’ within any directory in the blog-tree to get an RSS feed of that level/category/sub-blog. Sweeeet. Next up is to eliminate the permalinks needing to use the blosxom.pl script in the URL (i.e. so that archives don’t have to link to blosxom.pl at all).