Before this fix :
* was harcoded to 12,5%
* some bugs in template parameters prevented the javascript to work.
* some bugs prevented some calculations to be done properly.
z3950 search and import seems to works fine.
Let me explain how :
* a "search z3950" button is added in the addbiblio template.
* when clicked, a popup appears and z3950/search.pl is called
* z3950/search.pl calls addz3950search in the DB
* the z3950 daemon retrieve the records and stores them in z3950results AND in marc_breeding table.
* as long as there as searches pending, the popup auto refresh every 2 seconds, and says how many searches are pending.
* when the user clicks on a z3950 result => the parent popup is called with the requested biblio, and auto-filled
Note :
* character encoding support : (It's a nightmare...) In the z3950servers table, a "encoding" column has been added. You can put "UNIMARC" or "USMARC" in this column. Depending on this, the char_decode in C4::Biblio.pm replaces marc-char-encode by an iso 8859-1 encoding. Note that in the breeding import this value has been added too, for a better support.
* the marc_breeding and z3950* tables have been modified : they have an encoding column and the random z3950 number is stored too for convenience => it's the key I use to list only requested biblios in the popup.
* adding a syntax column in z3950 table = this column will say wether the z3950 must be called with PerferedRecordsyntax => USMARC or PerferedRecordsyntax => UNIMARC. I tried some french UNIMARC z3950 servers, and some only send USMARC, some only UNIMARC, some can answer with both.
Note this is a 1st draft. More to follow (today ? I hope).
* many bugfixes
* adding value_builder : you can map a subfield in the marc_subfield_structure to a sub stored in "value_builder" directory. In this directory you can create screen used to build values with any method. In this commit is a 1st draft of the builder for 100$a unimarc french subfield, which is composed of 35 digits, with 12 differents values (only the 4th first are provided for instance)
* bugfixes and improvements
* manage mandatory MARC subfields
* new table : authorised_values. this table contains categories and authorised values for the category. On MARC management, you can map a subfield to a authorised_values category. If you do this, the subfield can only be filled with a authorised_value of the selected category.
this submit contains everything needed :
* updatedatabase
* admin screens
* "links" management
* creation of a html-list if a subfield is mapped to an authorised value.
Note this is different from authorities support, which will come soon.
The authorised_values is supposed to contains a "small" number of authorised values for a category (less than 50-100). If you enter more authorised values than this, it should be hard to find what you want in a BIG list...
It creates a thesaurus table and fills it with data in bibliosubject. Thesaurus
contains 2 columns : freelib and stdlib. This permits connecting differents forms for a word/sentence (HUGO may be mapped to V. Hugo, Victor Hugo...)
In modbib.pl, you will see "..." near subject. If you click on this ..., a popup appear. It has 4 parts : the Subject field, a search field with Search button. If you enter a value here and click Search, a list of thesaurus entries starting by what you enter appear.
If you select a value and click "OK", the value is added to the subject list.
When you've finished, click END. the window is closed, and the value copied to main subject window.
Make heavy use of javascript. TESTED UNDER MOZILLA 0.99. Please test under IE.
Administration of thesaurus table will come soon (with html::template) ...
branchtransfers table
Circ2.pm has been changed a little
admin/branches.pl alows branches to be added, edited and deleted.
updatedatabase needs more fixing
changes the type of the datesent and datearrived fields in the
branchtransfers table from date to datetime.
completely re-organises the branchcategories table. As this has previously
been unused it shouldnt effect anyone.
adding, modifying or removing any fields from existing tables.
This is in very early stages. Need to go through and ascertain which
tables and fields need to be added/modified. Also need to add a "backup"
before any modifications are made. Thoughts on this are welcome.
