Hello, does anyone know how koha saves biblio and item data? Obviusly the data gets saved in different places twice. When I change the data for a biblio or an item in the mysql database it is only changed in the opac fields or the simple view fields in opac. When I switch to the complete view in opac I see a different value. For exapmple when I change a title in the database (without going through the koha intranet interface) it only gets changed in the simple view in opac. The reason why I am asking is that for checking errors the koha intranet is way too slow and time consuming. Through the mysql database it is much faster and easier. Thank you Regards Octavee __________________________________ Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686 -- View this message in context: http://www.nabble.com/how-does-koha-save-data-tp14764224p14764224.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
Octavee-- You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query. Depending on whether or not you use zebra indexing, a manual reindex can be called by: misc/migration_tools/rebuild_zebra.pl misc/migration_tools/rebuild_nozebra.pl Rebuilding indexes is typically accomplished each night with the same scripts via scheduled job. In full production, it doesn't make sense for cataloguers to rebuild all the indexes each time they add a record. If you manipulate data directly through mysql, you are no longer using Koha. It is up to you to figure out how the application may be broken by this, why MARC relationships or table pointers may no longer be valid, etc. Basically, whatever problems result are not attributable to the application. On the other hand, if you are using Koha's interface, and the logic breaks down, then it may be a bug developers can address. Some of the behavior of indexing and in particular MARC manipulation have been greatly improved in the newest versions of Koha. In particular, you might benefit from examining the 3.0 alpha just released. -joe atzberger LibLime On Jan 11, 2008 3:43 PM, Octavee Uhl <octavee@gmail.com> wrote:
Hello,
does anyone know how koha saves biblio and item data? Obviusly the data gets saved in different places twice. When I change the data for a biblio or an item in the mysql database it is only changed in the opac fields or the simple view fields in opac. When I switch to the complete view in opac I see a different value. For exapmple when I change a title in the database (without going through the koha intranet interface) it only gets changed in the simple view in opac. The reason why I am asking is that for checking errors the koha intranet is way too slow and time consuming. Through the mysql database it is much faster and easier.
Thank you Regards Octavee __________________________________ Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
Hello Joe, thanks so much for this info. How do I find out if that indexing is scheduled? Just to be sure, when I enter a change in the homebranch via MySQL and rebuild the index it will be correct and reflect in both views? I am ware that the koha intranet gives a certain security and I don't want users to mess with the data, but for me as the main Administrator I need to understand how things do work and sometimes interact via mysql. I want to wait until version 3 is stable and running fine before changing the system to version 3. Octavee Joe Atzberger wrote:
Octavee--
You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query. Depending on whether or not you use zebra indexing, a manual reindex can be called by:
misc/migration_tools/rebuild_zebra.pl misc/migration_tools/rebuild_nozebra.pl
Rebuilding indexes is typically accomplished each night with the same scripts via scheduled job. In full production, it doesn't make sense for cataloguers to rebuild all the indexes each time they add a record.
If you manipulate data directly through mysql, you are no longer using Koha. It is up to you to figure out how the application may be broken by this, why MARC relationships or table pointers may no longer be valid, etc. Basically, whatever problems result are not attributable to the application.
On the other hand, if you are using Koha's interface, and the logic breaks down, then it may be a bug developers can address. Some of the behavior of indexing and in particular MARC manipulation have been greatly improved in the newest versions of Koha. In particular, you might benefit from examining the 3.0 alpha just released.
-joe atzberger LibLime
On Jan 11, 2008 3:43 PM, Octavee Uhl <octavee@gmail.com> wrote:
Hello,
does anyone know how koha saves biblio and item data? Obviusly the data gets saved in different places twice. When I change the data for a biblio or an item in the mysql database it is only changed in the opac fields or the simple view fields in opac. When I switch to the complete view in opac I see a different value. For exapmple when I change a title in the database (without going through the koha intranet interface) it only gets changed in the simple view in opac. The reason why I am asking is that for checking errors the koha intranet is way too slow and time consuming. Through the mysql database it is much faster and easier.
Thank you Regards Octavee __________________________________ Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- View this message in context: http://www.nabble.com/how-does-koha-save-data-tp14764224p14766036.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query.
That would be true under 3.0 or dev_week, but is this accurate?
Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
2.2.8 doesn't use zebra indexing does it? -- Owen -- Web Developer Athens County Public Libraries http://www.myacpl.org
You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query.
That would be true under 3.0 or dev_week, but is this accurate?
Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
2.2.8 doesn't use zebra indexing does it? Just to clarify, there is no need to run an index script under normal circumstances, and running an index script as a scheduled job wouldn't be that useful as everything is indexed in real time in 3.0 (not in dev_week however, as Owen
On 1/12/08, Owen Leonard <oleonard@myacpl.org> wrote: points out). Also, indexing isn't handled with a batch script in the 2.2 version. Cheers, -- Joshua Ferraro SUPPORT FOR OPEN-SOURCE SOFTWARE President, Technology migration, training, maintenance, support LibLime Featuring Koha Open-Source ILS jmf@liblime.com |Full Demos at http://liblime.com/koha |1(888)KohaILS
You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query.
That would be true under 3.0 or dev_week, but is this accurate?
Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
2.2.8 doesn't use zebra indexing does it? Just to clarify, there is no need to run an index script under normal circumstances, and running an index script as a scheduled job wouldn't be that useful as everything is indexed in real time in 3.0 (not in dev_week however, as Owen
On 1/12/08, Owen Leonard <oleonard@myacpl.org> wrote: points out). Also, indexing isn't handled with a batch script in the 2.2 version. Hello Joshua, not quite sure what that means. We have version 2.28 (not 3.0) and as described I am trying to optimize certain entries via MYSQL. Do I need to rebuild the index in that case? How do i do that? How can I install the rebuild script? Thanks, Octavee -- View this message in context: http://www.nabble.com/how-does-koha-save-data-tp14764224p14809205.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
I just looked for the rebuild scripts. They are not on our server. How can I install those scripts/packages? Thanks, Octavee Joe Atzberger wrote:
Octavee--
You are seeing the value that is preserved in the index. Clearly the index is necessary to avoid searching entire database tables for each query. Depending on whether or not you use zebra indexing, a manual reindex can be called by:
misc/migration_tools/rebuild_zebra.pl misc/migration_tools/rebuild_nozebra.pl
Rebuilding indexes is typically accomplished each night with the same scripts via scheduled job. In full production, it doesn't make sense for cataloguers to rebuild all the indexes each time they add a record.
If you manipulate data directly through mysql, you are no longer using Koha. It is up to you to figure out how the application may be broken by this, why MARC relationships or table pointers may no longer be valid, etc. Basically, whatever problems result are not attributable to the application.
On the other hand, if you are using Koha's interface, and the logic breaks down, then it may be a bug developers can address. Some of the behavior of indexing and in particular MARC manipulation have been greatly improved in the newest versions of Koha. In particular, you might benefit from examining the 3.0 alpha just released.
-joe atzberger LibLime
On Jan 11, 2008 3:43 PM, Octavee Uhl <octavee@gmail.com> wrote:
Hello,
does anyone know how koha saves biblio and item data? Obviusly the data gets saved in different places twice. When I change the data for a biblio or an item in the mysql database it is only changed in the opac fields or the simple view fields in opac. When I switch to the complete view in opac I see a different value. For exapmple when I change a title in the database (without going through the koha intranet interface) it only gets changed in the simple view in opac. The reason why I am asking is that for checking errors the koha intranet is way too slow and time consuming. Through the mysql database it is much faster and easier.
Thank you Regards Octavee __________________________________ Koha version 2.2.8 OS version Linux Librarian 2.6.18-4-686
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- View this message in context: http://www.nabble.com/how-does-koha-save-data-tp14764224p14778924.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
participants (4)
-
Joe Atzberger -
Joshua Ferraro -
Octavee Uhl -
Owen Leonard