Thanks Chris,
I feel like I just peeked behind the Wizard's curtain in OZ :--)
(http://www.imdb.com/title/tt0032138/) With this information and Bob's help I
feel like I can better assist our librarian with her needs.
Thanks,
Rick
---
Rick Forristall
Pr
2010/4/28 Richard Forristall :
> Bob,
>
> Thanks so much for the info. As the developer solely responsible for
> supporting our librarian, for me it has become both a development issue and
> end-user issue. Not being sure if it was code modification required or just
> ensuring the MARC record had
Bob,
Thanks so much for the info. As the developer solely responsible for
supporting our librarian, for me it has become both a development issue and
end-user issue. Not being sure if it was code modification required or just
ensuring the MARC record had the requisite data, I opted to ask the
Richard,
This is not a development question and might have been better on the general
list.
Koha stores item information in the 952 tag of the marc record. So the
first question may be whether all the records have a 952 tag. The fields
within that tag can be readily understood by viewing 'Koha t
Hi all,
Our librarian is having trouble with her MARC record imports. On some
of the imports, the record imports, but doesn't import the item. So in
an OPAC search the record appears, but shows "Availability: No items
available"
The librarian has worked with the vendors to modify MARC records,
On Ubuntu Lucid everything but HTTP::OAI and
MARC::Crosswalk::DublinCore is available in the universe repository.
Even idzebra. I've made a list for documenting it.
aptitude install libalgorithm-checkdigits-perl
libbiblio-endnotestyle-perl libcgi-session-perl \
libcgi-session-serialize-yaml-perl
My understanding is that the marcxml column is actually authoritative.
The table trio is more for quick work that doesn't need / can't wait for
the MARC data to be parsed. Also I think the zebra index is build from
either marc or marcxml column depending on an option to
rebuild_zebra.pl.
On Tue,
I've also got a working patch which targets MARC21. I've used it for
migration and importing from vendor supplied marc files. It's not as
nice or flexible as what Kyle is working on though, so I won't recommend
it for inclusion in the general code tree at this point. It would work
in a pinch tho
