Re: [Koha-devel] feature list for Koha 2.4/3.0 (hdl & paul coding planning)

[Thomas D]

4 July 2005


Quoting Paul POULAIN <address@hidden> :
> ---------------- Beginning of the original message ------------------
> 
> Hi,
> 
> Here is a list of features that hdl & me will code soon
> (reminder for 
> thos who didn't follow : hdl & me are working together)
> 
> All of them will be in next major version, some of them being
> backported 
> to 2.2.x (that will be specified in this mail. when it's
> written 
> "backported soon", it means that the backport will be done
> asap, as it's 
> requested by one of my customers. otherwise, will be
> backported when 
> hdl/me has time & if requested by someone)
> 

[snip]

> 
> *2- OTHER IMPROVEMENTS*
> ==========================
> 2-C tracking who does what
> Koha will save which librarian creates/modify a biblio, and
> when (but 
> not what he changed ? open question here, as saving what he
> changed can 
> be very complex) Needs a new table in DB, will be in head
> only.

What are the special difficulties in doing a comparison of strings from the
original to the currently submitted state after trimming them?  I have
considered it a great advantage to know at least what was contributed or
modified by local cataloguing as opposed to what had been obtained from an
original copy catalogued record.  Who makes modification for the local
system is less important except for concern about transaction control over a
particular user's mistakes.

Think of what might need to be restored in case of data corruption, when one
had to return to the source of an original record.  Basic fields may have
been improved or modified to match a particular expression or manifestation
not found in the original record source.

More interesting is the value of knowing what improvements or variant
expressions and manifestations might exist from a standard national
bibliographic record when searching a union catalogue.  There should be an
advantage to readily distinguishing the elements of variance as
distinguished from the current practise of examining every whole record
individually.

Some sort of versioning system could be very useful.  There may be some
simpler means of using diff in a batch mode on the whole record to obtain
some equivalent result.  There should be no reason to slow the system
unduely in real time to accomplish this.

[snip]

> 
> -- 
> Paul POULAIN
> Consultant indépendant en logiciels libres
> responsable francophone de koha (SIGB libre
> http://www.koha-fr.org)
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration
> Strategies
> from IBM. Find simple to follow Roadmaps, straightforward
> articles,
> informative Webcasts and more! Get everything you need to get
> up to
> speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id?492&op¿ick
> _______________________________________________
> Koha-devel mailing list
> address@hidden
> https://lists.sourceforge.net/lists/listinfo/koha-devel
> 
> ------------------- End of the original message ---------------------


Thomas D

---------------------------------------------
Protect your mails from viruses thanks to Alinto Premium services 
http://www.alinto.com