Hi,
On Wed, Oct 30, 2013 at 7:21 PM, Elaine Bradtke wrote:
> Still, there's an underlying quirk - if Koha sees a character it doesn't
> like in the 008 editing window, it skips over it and collapses the rest of
> the data.
> While the non # characters were originally in the correct place - once
magmatic schreef op wo 30-10-2013 om 19:17 [-0700]:
> I'm pretty sure this will work. The reason I'm saying all this is
> just so
> that if anyone out there has any advice for me before I begin, I would
> take
> it. Perhaps there are pitfalls to guard against, or perhaps there is
> some
> feature
Still, there's an underlying quirk - if Koha sees a character it doesn't
like in the 008 editing window, it skips over it and collapses the rest of
the data.
While the non # characters were originally in the correct place - once we
touch that field in the editing window they are moved to a differen
We have a separate database of users that we want to sync (one way) with
Koha. Since I have experience working with databases, I plan to add a
column to the Koha MySQL patron table that I will use as a reference to the
record in the other database. Then everyday I'm going to run a cron job
that m
On Wed, Oct 30, 2013 at 5:05 PM, Galen Charlton wrote:
> Hi Elaine,
>
> On Wed, Oct 30, 2013 at 4:31 PM, Elaine Bradtke wrote:
>
>> Here's an example of the imported 008:
>> 130515s2006stka###gr#000#0#eng#d
>>
>
> Just to confirm, for the migrated records, "#" in the 008 represents a
> l
Hi Galen
Correct - # is literal. Not a space.
Elaine
On Thu, Oct 31, 2013 at 12:05 AM, Galen Charlton wrote:
> Hi Elaine,
>
> On Wed, Oct 30, 2013 at 4:31 PM, Elaine Bradtke wrote:
>>
>> Here's an example of the imported 008:
>> 130515s2006stka###gr#000#0#eng#d
>
>
> Just to confirm, f
Hi Elaine,
On Wed, Oct 30, 2013 at 4:31 PM, Elaine Bradtke wrote:
> Here's an example of the imported 008:
> 130515s2006stka###gr#000#0#eng#d
>
Just to confirm, for the migrated records, "#" in the 008 represents a
literal hash character, not a space?
> How important is the 008 field
Something is happening to our 008 fields, when we edit the 008 field
of an imported record (converted from our old database - this doesn't
seem to be a problem with Z39.50 downloads). I don't know if it's
always been a problem, or if it's just come up since we moved to 3.12.
Our cataloguer only re
I would like to apply to the list using my other email, as Yahoo has become
terribly confusing. My other email is doroth...@hotmail.com
Should I try accessing the list-serve through that email, or can you change me
over? Thanks for your help. It is much appreciated!
Have a great day, ~Estel~
O
Hi,
The October 2013 edition of the Koha Community Newsletter has been
posted to http://koha-community.org/koha-community-newsletter-october-2013/.
Cheers,
Daniel Grobani
Koha Community Newsletter Editor
___
Koha mailing list http://koha-community.org
I don't think EasyAnalytics does anything when you're importing
records. But we've had good success with linking between parent and
child records after importing them.
This is what we do:
We've linked ours using 773 and 774 in MARC21
Child = the analytical. Parent = the host .
The 773 field is
Hi there Željko,
I solved my problems in the meanwhile (thanks Zeno for the tip!), but BE
CAREFUL: I'm still testing it and I recommend you not to try it on a
production system yet since I'm not sure it's the correct way to set things
up.
Is OSB a built-in authority type or a custom one? I'm sorr
wow Suzuki thanks worked like a charm. Really appreciate
On 30 October 2013 14:31, Lighton Phiri wrote:
> Hello Sitali,
>
> Saw your post and got interested. Does your institution have an
> publicly accessible DSpace-based repository? What's the URL?
>
> Lighton Phiri
> http://lightonphiri.org
Hallo to everyone,
I am having a problem importing authorities into Koha 3.12.5 (Debian
Wheezy packaged version). When I import authorities into Koha the
Authority type gets replaced from what i put into field 152b (where Koha
keeps authority type code) to SNC. Because of that I can't search f
That really depends upon how they're linked in ISIS.. if they are using
standard 001 linking then koha will happily link upon import if you set
'UseControlNumber'.
If they are not already linked that way, then you'll need to do a little
more work. Someone else is probably better positioned to expl
15 matches
Mail list logo