Hello, as asked here before, we moved from Book2DB to Koha which was quite a quest as Book2DB is saving all information data set-based. So in every catalogued book there is also the signature saved. So I rebuid the exported *.csv-file to match MARCMaker as to make an *mrk and *mrc-file. I've tried to do my best to re-route all MARC-fields to the given scheme. text file is saved as ANSI. <http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Upgrade_Textdatei_aus_Book2DB_ANSI_001.jpg> <http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Buecherliste_mrk.jpg> Although it seems to have worked so far, I have some troubles also. The search results look as following <http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Ergebnisliste.jpg> I'm not sure if this should look like this Also there were problems for the proper display of mutation signs. Not to mention that I have to move the signatures out of the 500 category to form single issues. Perhaps someone can look over the whole thing and I can tell me, if I have transformed it right or if I should re-import the database with other settings? Currently I have Koha 16.05 installed. I'm running OMV 2.0.21 (i.e Debian Wheezy) and the new Koha build isn't installing. If anyone want to look into it for yourself: http://koha.enne.at Searching without logging in is possible. I'm thankful for any assistance. With kind regards Martin -- View this message in context: http://koha.1045719.n5.nabble.com/Converting-to-Koha-16-05-some-issues-tp592... Sent from the Koha-general mailing list archive at Nabble.com.
Dear Koha Friends, Can someone point me to a how-to on upgrading from an old version? We have 3.10. I am presently reading this page: http://kohageek.blogspot.com/2013/05/how-to-upgrade-to-koha-312-in-koha-live... Thank you. David
You should definitely install a fresh Koha on a new server, and migrate the DB. El jue., 16 feb. 2017 a las 13:45, David (<david@intknowledge.com>) escribió:
Dear Koha Friends,
Can someone point me to a how-to on upgrading from an old version? We have 3.10. I am presently reading this page:
http://kohageek.blogspot.com/2013/05/how-to-upgrade-to-koha-312-in-koha-live...
Thank you.
David _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Thank you for that. So, you got me reading: https://www.linkedin.com/pulse/step-guide-migration-old-koha-database-new-du... If there's a clearer step by step for migrating, I'd love to hear about it. Many thanks again for your help. David On 18/02/2560 01:00, Tomas Cohen Arazi wrote:
You should definitely install a fresh Koha on a new server, and migrate the DB.
El jue., 16 feb. 2017 a las 13:45, David (<david@intknowledge.com <mailto:david@intknowledge.com>>) escribió:
Dear Koha Friends,
Can someone point me to a how-to on upgrading from an old version? We have 3.10. I am presently reading this page: http://kohageek.blogspot.com/2013/05/how-to-upgrade-to-koha-312-in-koha-live...
Thank you.
David _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz <mailto:Koha@lists.katipo.co.nz> https://lists.katipo.co.nz/mailman/listinfo/koha
-- Tomás Cohen Arazi Theke Solutions (https://theke.io <http://theke.io/>) ✆ +54 9351 3513384 GPG: B2F3C15F
Hi Martin, I took a quick look at the screenshot and noticed a few things: - Your Umlauts don't look right. Make sure your data is encoded in UTF-8 before you import. - There is no label showing in front of the publisher and publication year - this looks a bit odd. I'd try to combine your multiple 264 into one with $a$b$c. Same for 245 and 100 that are actually not repeatable. - Your authors appear as surname | firstname. This is because of the problem noted above. Usually this would look like: surname, firstname from a single 100$a. - 689 is a custom field only used in Germany for 'Schlagwortketten' - you might want to change that to 650 or another more standard field that will work better with Koha. Hope this helps, Katrin On 16.02.2017 11:48, Sir_Charles82 wrote:
Hello,
as asked here before, we moved from Book2DB to Koha which was quite a quest as Book2DB is saving all information data set-based. So in every catalogued book there is also the signature saved.
So I rebuid the exported *.csv-file to match MARCMaker as to make an *mrk and *mrc-file. I've tried to do my best to re-route all MARC-fields to the given scheme. text file is saved as ANSI.
<http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Upgrade_Textdatei_aus_Book2DB_ANSI_001.jpg>
<http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Buecherliste_mrk.jpg>
Although it seems to have worked so far, I have some troubles also. The search results look as following <http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Ergebnisliste.jpg>
I'm not sure if this should look like this Also there were problems for the proper display of mutation signs. Not to mention that I have to move the signatures out of the 500 category to form single issues.
Perhaps someone can look over the whole thing and I can tell me, if I have transformed it right or if I should re-import the database with other settings?
Currently I have Koha 16.05 installed. I'm running OMV 2.0.21 (i.e Debian Wheezy) and the new Koha build isn't installing. If anyone want to look into it for yourself: http://koha.enne.at Searching without logging in is possible.
I'm thankful for any assistance. With kind regards Martin
-- View this message in context: http://koha.1045719.n5.nabble.com/Converting-to-Koha-16-05-some-issues-tp592... Sent from the Koha-general mailing list archive at Nabble.com. _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
Hello Katrin, thank you for your reply. So i will try to convert the text file from ANSI to UTF-8 before doing anything else. My Problem is that the data is coming like seen in http://koha.1045719.n5.nabble.com/file/n5922009/Koha_Upgrade_Textdatei_aus_B... there are single fields for name, surname,2nd firstname etc. and I've tried to route it correctly. But i guess I have to re-catalogue the whole data once I have corrected the file to UTF-8. thanks for the hint with 689, i will change it to 650 Thanks again for the help! -- View this message in context: http://koha.1045719.n5.nabble.com/Converting-to-Koha-16-05-some-issues-tp592... Sent from the Koha-general mailing list archive at Nabble.com.
participants (4)
-
David -
Katrin -
Sir_Charles82 -
Tomas Cohen Arazi