Before I launch into a vast context-setting exercise, I can at least do a thumbnail sketch of the current state of the Scholar's Box:
-
It demonstrates technological possibilities that others hadn't but are beginning to do. (e.g., writing out OpenOfficeOrg documents de novo. When I mentioned that I was doing that to UcheOgbuji, he said that doing so was "hard core". Now, there's a Perl library to do some of that functionality.) Such demonstrations were very interesting in the early stages, but not so much so now. Partly because others are doing so but really, we have shown that it is possible.
-
Now, it might still be useful to show others that what we have demonstrated is indeed possible. Just because I know so and I find such demos a bit boring now doesn't mean that such demos would not be useful news to others.
-
The software is at the "edge of usability", meaning that the outlines of the required functionality is there, but not coherent and deep enough to support daily work with the software.
Another angle with which I have approached the Scholar's Box is through studying my own interactions and relationships with information. (See, for example, ScholarsBox/DesignedForRaymondYee.)
Finally, some clarity: I will put my focus on describing in detail what I want to create with the ScholarsBox or allied technologies, with a focus on bibliographic-related collections and image collections.
