Hi all! This was already figured out. It was because of the server being
bloated because of the opac-error.log. There's this weird crawler from
Russia that takes up a considerable amount in the log=
http://www.abuseipdb.com/check/188.143.232.41
[Fri May 29 07:59:33.658328 2015] [cgi:error] [pid 368
And oh yes once the bloated error log was deleted and the server restarted,
the Koha ILS was already accessible. I'm particularly curious if that really
is the case.
--
View this message in context:
http://koha.1045719.n5.nabble.com/Help-Software-Error-tp5842000p5842198.html
Sent from the Koha
Happy Friday everyone.
I am also interested in seeing responses to this 952 $a/$b question because
we are very close to importing our very first records into our very first
Koha instance (running 3.20 on Debian).
I have been building records in Connexion, adding a 952, but now I want to
make sure
Curious,
What kinds of issues have people run into relative to the adding of 952 to
records or the importation of these records into KOHA?
I mean, is it better to add local holding info and barcode data into KOHA
directly or is it faster to have already added this info already?
I ask because I a
There is no problem to add 952 fields to import data,
I think is the preferred way.
You need to add 952 a,b and p at least.
Take a look at
http://translate.koha-community.org/manual/3.18/en/html-desktop/#itemcatguide
Hope that helps
Bernardo
--
Bernardo Gonzalez Kriegel
bgkrie...@gmail.com
On
Oh, great, that is helpful.
One follow-up question...
Should I add a separate 952 for each copy of an item (which would thus have
its own copy and barcode data)?
Thanks a bundle (and a bunch).
Jesse
On Fri, May 29, 2015 at 2:29 PM, Bernardo Gonzalez Kriegel <
bgkrie...@gmail.com> wrote:
> The
>
> One follow-up question...
>
> Should I add a separate 952 for each copy of an item (which would thus
> have its own copy and barcode data)?
>
>
Yes, you are right. One 952 for each copy.
Bernardo
___
Koha mailing list http://koha-community.org
Koha@
Yes, each physical item should have its own 952 with a unique barcode.
Katelyn Browne
High School Librarian & Technology Teacher
Capital City Public Charter School
100 Peabody Street NW
Washington, DC 20011
(202) 387-0309 x1745
kbro...@ccpcs.org
http://www.ccpcs.org/library/
On Fri, May 29, 2015
Thank you.
I will need to edit some 952 data now.
(Project for Monday methinks). :)
Cheers and happy weekend.
Jesse
On Fri, May 29, 2015 at 2:40 PM, Katelyn Browne wrote:
> Yes, each physical item should have its own 952 with a unique barcode.
>
> Katelyn Browne
> High School Librarian & Tec
Greetings,
Useful links:
http://wiki.koha-community.org/wiki/Holdings_data_fields_%289xx%29
http://bywatersolutions.com/2014/10/17/preparing-records-koha-import/
http://bywatersolutions.com/2012/01/18/using-marcedit-to-add-koha-items/
http://bywatersolutions.com/2012/02/29/altering-marc-records-i
Hi, Jesse--
I catalog on OCLC's Connexion Client, and use the "Text String" tool to set
up my most commonly used fields in the 952--it's really handy, and
generates my most commonly used 952 with a keystroke. I've found that it's
faster to create the item records on OCLC with 952 fields & import
Thank you Heather & Mark,
I am on the right track now..., but I am going to need to better edit my
text strings now in 952 (which means some going back and reworking etc).
I assume I can add the subfields in the order listed
numerically/alphabetically instead of the order you have them listed?
I
Hi, Jesse--
For the subfields that I use in the 952 field, the order doesn't seem to
matter. We're on Koha 3.18--I don't know if the subfield order matters for
other versions of Koha, or if there's any other variables to consider,
though.
It's easy to experiment--put the fields in the order that
13 matches
Mail list logo
