Idly, besides MARC features, do we want to do a feature-request list, while you all are in the process of polishing and intergrating the MARC and other items? I see the traffic on the various DB reorg/changes and am curious to know what else is on various wish lists. Since the faq is basically done, I can handle tracking that... Nick
On Sun, 2002-03-03 at 11:43, Nicholas Rosasco wrote:
Idly, besides MARC features, do we want to do a feature-request list, while you all are in the process of polishing and intergrating the MARC and other items? I see the traffic on the various DB reorg/changes and am curious to know what else is on various wish lists.
Since the faq is basically done, I can handle tracking that...
Excellent I think a big one, is a templating system. Im leaning towards using axkit (axkit.org) at the moment. If we get the templating set up right, it should make localisation and customisation of koha a ton easier. What other things do we want to put on the wishlist? Steve .. perhaps something to do with the eduml idea? Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
What other things do we want to put on the wishlist?
One of the most useful features I've ever seen is a function to 'print to email' -- ie to send a search, or selected results from a search, to email. A line-printer (ie text only) display feature for records is also something I see getting a lot of use -- printing an entire webpage gets costly after awhile. Does anyone know, also, if there is a standardized format for the various citation manager applications (EndNote, etc)? Applications like these are major favorites of academics, in my experience. Also, I've never played with the patron info section -- is there a block for email address? The ability to automagically request a recall of a book when checked out is pretty handy. Nick
On Sat, 2 Mar 2002, Nicholas Rosasco wrote:
Idly, besides MARC features, do we want to do a feature-request list, while you all are in the process of polishing and intergrating the MARC and other items? I see the traffic on the various DB reorg/changes and am curious to know what else is on various wish lists.
Since the faq is basically done, I can handle tracking that...
More abstraction of user interface from data processing code. Since I know this will mean nothing to the non-programmers amongst us, it basically means that things like search routines return a fixed set of data every time, and _never_ concern themselves with how the data is going to be presented to the user. This should probably be taken into consideration while axkit development is taking place... 1. Search interface needs to be cleaned up. The @stuff arrays confuse me. :) 2. Cataloguing API - This is what I started on, but have gotten badly bogged down with. Syncing the MARC and KohaDB backends got ugly in a hurry. I need to rethink how I approached it, I think. If there are programmers on the list now who are interested in helping with this, drop me a line. 3. Soundex searches (ie searching for elefant will turn up elephant results) Steve.
I've fed, more out of habit, what I've seen so far in terms of feature requests/etc to the sourceforge tracker. I'll be keeping tabs on the list for more. Is there a way to configure which information is displayed for classtype, etc? on record display for an item? Not everyone uses Dewey classification, for example, and if/when we have full marc capability it might be useful to be able to trim how much record is displayed (elementary school libraries, for example, have little need for the lengthy version). Also, on a possible usage-increase note... if anyone thinks it'd be nifty :) I'll see if the k12linux (Linux for schools) project would be interested in adding Koha to their install package? Nick
On Tue, 2002-03-05 at 07:37, Nicholas Rosasco wrote:
I've fed, more out of habit, what I've seen so far in terms of feature requests/etc to the sourceforge tracker. I'll be keeping tabs on the list for more.
Is there a way to configure which information is displayed for classtype, etc? on record display for an item? Not everyone uses Dewey classification, for example, and if/when we have full marc capability it might be useful to be able to trim how much record is displayed (elementary school libraries, for example, have little need for the lengthy version).
Actually this feeds in nicely into what I was saying about the searches in the earlier email. Id like to be able to customise the searches and search results.
Also, on a possible usage-increase note... if anyone thinks it'd be nifty :) I'll see if the k12linux (Linux for schools) project would be interested in adding Koha to their install package?
Sounds good, perhaps 1.2.0 ... we really need to get our more easier install up and going i think. Its a snap to install Koha as a debian package. Its still a mission from the tarball. Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
More abstraction of user interface from data processing code. Since I know this will mean nothing to the non-programmers amongst us, it basically means that things like search routines return a fixed set of data every time, and _never_ concern themselves with how the data is going to be presented to the user. This should probably be taken into consideration while axkit development is taking place...
Yep, good call
1. Search interface needs to be cleaned up. The @stuff arrays confuse me. :)
Yeah I have a grand scheme for the search stuff, in terms of setting up some way so that ppl can customise the search. IE when u install koha, you can say I want to be able to search author, title, keyword in the opac. Or I want the search off the front screen of the opac to search only author's and titles. I was thinking that as mysql is heading towards stored procedures, and most other rdbms support them already it would be the way to do it. So we have some kind of customisation/admin program that can generate the stored procedures for doing the searches. Thoughts/Comments/Youve got to be joking remarks?
2. Cataloguing API - This is what I started on, but have gotten badly bogged down with. Syncing the MARC and KohaDB backends got ugly in a hurry. I need to rethink how I approached it, I think. If there are programmers on the list now who are interested in helping with this, drop me a line.
I could probably spend a little time on this, if you have some tasks, you want to throw my way.
3. Soundex searches (ie searching for elefant will turn up elephant results)
Ohh yeah, I know the librarians at HLT would love that Chris -- Chris Cormack Programmer 025 500 789 Katipo Communications Ltd chris@katipo.co.nz www.katipo.co.nz
3. Soundex searches (ie searching for elefant will turn up elephant results)
Ohh yeah, I know the librarians at HLT would love that
http://www.perldoc.com/perl5.6.1/lib/Text/Soundex.html http://search.cpan.org/search?mode=module&query=soundex Have some info on this -- at least something exists already. Knuth's Art of Computer Programming apparently has info on it in Vol. 3. Only real issue with it is US-English bias, apparently. It was originally created for indexing immigration records where original spelling was phonetic by an English-language listener, AFAICR. Nick
participants (3)
-
Chris Cormack -
Nicholas Rosasco -
Tonnesen Steve