Hi Josh, I think this would be a great idea to figure out now before we do the move to the 3.0. I know I changed all of my records to 952 when I originally started migrating to Koha. It would be a help when librarians wanted to get records from vendors to have them match the usual manner.
Darla Grediagin District Librarian Bering Strait School District Unalakleet, Alaska Web Address : http://bssdonline.org/course/view.php?id=51 Blog: http://aklibrarian1.edublogs.org/ OPAC: http://opac.bssd.org:8181/cgi-bin/koha/opac-search.pl Joshua Ferraro wrote: > Hi folks, > > It's recently come to my attention that many ILSes store their items data > in a 949 tag by default. Thusfar, we've stuck with the historical convention > of 952 (which was our version of a 'localized' 852). 852, in the MARC21 > standard, is reserved for 'holdings' data (holdings data is separate from > items data, and there will be a future RFC addressing how Koha should > handle holdings data). > > As Koha popularity expands, we should consider switching to the 'de facto' > standard for items data (949). The need was brought to my attention recently > on an OCLC list where it was discovered that OCLC uses 952 for internal > codes, and therefore, it can't be exported. So libraries using OCLC for > cataloging, who want to manually add their items data to their records, > download them from OCLC, and them upload into Koha, will have to use > another tag for items data. > > I'm thinking this would primarily consist of: > > 1. updating the default frameworks for MARC21 (UNIMARC too?) > 2. updating the XSL stylesheets for MARC21 > 3. creating a script that moves stuff from 952 into 949 > > Thoughts? > > Cheers, > > _______________________________________________ Koha-devel mailing list [email protected] http://lists.koha.org/mailman/listinfo/koha-devel
