All, In 3.4 and on, I somehow got the impression (dream/nightmare?) that biblioitems was to no longer exist, and that certain MARC fields that are repeatable - particularly the 300, will no longer be. Did I dream that or is that the case? If it is true, will Koha have a way to handle those repeatable fields? I would appreciate hearing from someone about this right away, as it may scuttle our whole migration plan. Thanks! -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Linda, The biblioitems table could really stand to be merged with the biblio table, as ever since Koha 2.0 and MARC support, the two have been in 1-1 correspondence. Having them separate introduces complication for development and for reports. Unfortunately, I have not seen anything come down the pike to merge them together for 3.4. Fortunately, these database tables have nothing to do with the repeatability of MARC fields. The full MARC record is stored in biblioitems, true, and will continue to be until we get a merge in place, at which time it will be in whatever the merged table is called. So, do not worry. You can repeat any MARC subfield that the standard (in your case, I assume MARC21) will allow to be repeated (so, not 245, for example), and shall be until MARC is completely wiped from the face of the earth. Cheers, -Ian On Wed, Apr 6, 2011 at 8:49 AM, Linda Culberson <lculber@mdah.state.ms.us>wrote:
All, In 3.4 and on, I somehow got the impression (dream/nightmare?) that biblioitems was to no longer exist, and that certain MARC fields that are repeatable - particularly the 300, will no longer be. Did I dream that or is that the case? If it is true, will Koha have a way to handle those repeatable fields?
I would appreciate hearing from someone about this right away, as it may scuttle our whole migration plan.
Thanks! -- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
-- Ian Walls Lead Development Specialist ByWater Solutions ALA Booth 732 Phone # (888) 900-8944 http://bywatersolutions.com ian.walls@bywatersolutions.com Twitter: @sekjal
* Linda Culberson (lculber@mdah.state.ms.us) wrote:
All, In 3.4 and on, I somehow got the impression (dream/nightmare?) that biblioitems was to no longer exist, and that certain MARC fields that are repeatable - particularly the 300, will no longer be. Did I dream that or is that the case? If it is true, will Koha have a way to handle those repeatable fields?
I would appreciate hearing from someone about this right away, as it may scuttle our whole migration plan.
I can confirm as 3.4 Release Manager that removing repeatable fields was not ever planned for the 3.4.x series (or any other release series for that matter). Merging biblio and biblioitems may happen in the future, (not for 3.4.x) but it will not ever result in a regression of features like this. I'm not sure where you got them impression, if you can recall, and correct anyone else who has this fear also that would be awesome. The nice thing about Koha is all development and discussion is done in the open, so at any point anyone can see exactly what is going to be in 3.4.x. No hidden suprises, no unreleased code, it's all there for everyone to see. Which is why I recommend (well I would wouldn't I, being Release manager and all) that people run from official Koha releases. No hidden nasties. Chris -- Chris Cormack Catalyst IT Ltd. +64 4 803 2238 PO Box 11-053, Manners St, Wellington 6142, New Zealand
All, I couldn't remember where I'd seen the reference to biblioitems being merged with biblio, so went back to my notes. It was in an RFP on the wiki. Now, I see that the RFC has been listed as abandoned. Thanks to all for your reassurance. By way of explanation we have done numerous test migrations, checking and rechecking that things convert properly, and then fixing in our current catalog what doesn't work in Koha. We are getting very close, and I've be going over my notes to make sure I didn't miss anything. Out of over 100,000 biblios, I'm now down to two (that I know of) that have serious problems. One of those has multiple 300 tags, although that isn't creating its problem. It helps to know everyone is out there and so willing to help, and I appreciate your patience. Thanks, Linda On 4/6/2011 12:17 PM, Chris Cormack wrote:
* Linda Culberson (lculber@mdah.state.ms.us) wrote:
All, In 3.4 and on, I somehow got the impression (dream/nightmare?) that biblioitems was to no longer exist, and that certain MARC fields that are repeatable - particularly the 300, will no longer be. Did I dream that or is that the case? If it is true, will Koha have a way to handle those repeatable fields?
I would appreciate hearing from someone about this right away, as it may scuttle our whole migration plan.
I can confirm as 3.4 Release Manager that removing repeatable fields was not ever planned for the 3.4.x series (or any other release series for that matter).
Merging biblio and biblioitems may happen in the future, (not for 3.4.x) but it will not ever result in a regression of features like this.
I'm not sure where you got them impression, if you can recall, and correct anyone else who has this fear also that would be awesome.
The nice thing about Koha is all development and discussion is done in the open, so at any point anyone can see exactly what is going to be in 3.4.x. No hidden suprises, no unreleased code, it's all there for everyone to see. Which is why I recommend (well I would wouldn't I, being Release manager and all) that people run from official Koha releases. No hidden nasties.
Chris
-- Linda Culberson lculber@mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives & History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824
Chris Cormack <chrisc@catalyst.net.nz>
[...] Which is why I recommend (well I would wouldn't I, being Release manager and all) that people run from official Koha releases. No hidden nasties.
I think you mean run official Koha releases, not run from them! :) Thanks for making me smile, though! Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha
On 7 Apr 2011 07:27, "MJ Ray" <mjr@phonecoop.coop> wrote:
Chris Cormack <chrisc@catalyst.net.nz>
[...] Which is why I recommend (well I would wouldn't I, being Release manager and all) that people run from official Koha releases. No hidden nasties.
I think you mean run official Koha releases, not run from them! :)
I do indeed, or run code from official releases, run away from the non official, or never even released code :)
Thanks for making me smile, though!
I aim to please :) Chris
Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op. http://koha-community.org supporter, web and LMS developer, statistician. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire for Koha work http://www.software.coop/products/koha _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (5)
-
Chris Cormack -
Chris Cormack -
Ian Walls -
Linda Culberson -
MJ Ray