Henri-Damien Laurent has pointed out that I answered too quickly without attending to what I should have remembered. The tab where the subfield may be edited in the editor is set by marc_subfield_structure.tab . Mere visibility is controlled by marc_subfield_structure.hidden . In my haste, I had incorrectly inferred and implied a less flexible combined function for .marc_subfield_structure.hidden that it does not have. Sorry for any confusion. At least the values that I supplied for the SQL statements were valid values as I had taken the time to confirm from my own installation.. The complete two SQL statements.should be as follows. UPDATE marc_subfield_structure SET hidden = "0", tab = "0" WHERE tagfield = "050" AND tagsubfield = "a"; UPDATE marc_subfield_structure SET hidden = "0", tab = "0" WHERE tagfield = "050" AND tagsubfield = "b"; Thomas D Quoting Thomas D <koha@alinto.com> :
---------------- Beginning of the original message ------------------
[Message included this time.]
Assuming that your biblioframework is still the default one. The following two SQL statements should set 050 to visible if you log into your Koha database in MySQL.
UPDATE marc_subfield_structure SET hidden = "0" WHERE tagfield = "050" AND tagsubfield = "a"; UPDATE marc_subfield_structure SET hidden = "0" WHERE tagfield = "050" AND tagsubfield = "b";
I have no clue about the Windows specific bug that would prevent the Koha web form from operating correctly.
Thomas D
Quoting Chris Cormack <chris@katipo.co.nz> :
---------------- Beginning of the original message
Carol Ku wrote:
Thanks for the prompt response. However, there seems to
be
a bug or
something about editing the subfield. I sent a message several weeks ago about the error, it says something like web server error. A programmer said he can duplicate the problem for Windows version of Koha, that's all I hear from them.
Hi Carol,
It was Rob who duplicated the problem, he packages Koha for windows. Unfortunately none of the programmers (that I know of) use windows, so we havent worked on it.
I hope this can be fixed in the next release of version 3.
Otherwise,
this put us in quite a handicapped position. Thanks.
Im sure it will be, but to make sure you should bug report it at http://bugs.koha.org
Chris -- Chris Cormack Katipo Communications Programmer www.katipo.co.nz 027 4500 789 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------- End of the original message
--------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
------------------- End of the original message ---------------------
--------------------------------------------- Protect your mails from viruses thanks to Alinto Premium services http://www.alinto.com