Re: [Koha] Importing Authority Records without Renumbering

2021-01-18 Thread Charles Kelley
Hello, Katrin et al!

In our latest exchange, on 18 Jan. 2021 at 23:22, Katrin Fischer <
katrin.fischer...@web.de> wrote:

to my knowledge there is currently no way to avoid this renumbering. Koha
> will assign the authority record the PK from the auth_header table on
> importing, you can't keep your own numbers. I think this would be a useful
> switch - please consider filing an enhancement request on bugzilla if there
> isn't one yet.
>

An excellent suggestion. I just found the Bugzilla reporting form. I'm
going to try. Thanks.


> I wonder: why don't you move the whole database to the new server instead
> of exporting and importing data?
>

I've been trying that, too, but that engenders a different problem:
'"Can't connect to local MySQL server through socket
'/var/run/mysqld/mysqld.sock'".

Most frustrating, to say the least.

-- 

気を付けて。 /ki wo tukete/ = Take care.

-- Charles.

Charles Kelley, MLS
PSC 704 Box 1029
APO AP 96338

Charles Kelley
Tsukimino 1-Chome 5-2
Tsukimino Gaadenia #210
Yamato-shi, Kanagawa-ken
〒242-0002 JAPAN

+1-301-741-7122 [US cell]
+81-80-4356-2178 [JPN cell]

mnogoja...@aol.com [h]
cmkelley...@gmail.com [p]

linkedin.com/in/cmkelleymls 
Meeting Your Information Needs. Virtually.
___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha


Re: [Koha] Importing Authority Records without Renumbering

2021-01-18 Thread Katrin Fischer

Hi Charles,

to my knowledge there is currently no way to avoid this renumbering.
Koha will assign the authority record the PK from the auth_header table
on importing, you can't keep your own numbers. I think this would be a
useful switch - please consider filing an enhancement request on
bugzilla if there isn't one yet.

I wonder: why don't you move the whole database to the new server
instead of exporting and importing data?

Katrin

On 18.01.21 10:59, Charles Kelley wrote:

Hello, everyone!

 My library is migrating our Koha ILS to a new machine. We are now ready
to upload the authority and bibliographic records. I tried a test upload of
the authority records, but I was surprised and disappointed when in the
upload of the authority records, the authority record number was changed.
The change reflects the deletion of duplicate and merged authority records
we have found in recent months.

 Needless to say, this cannot stand because the bibliographic fields
that are connected to a specific authority record through $9 subfield will
end up connected with a different authority record.

 Case in point: In the current database, I made a dummy author named Sam
Loesser, and Koha automatically assigned him authority record #197. In the
test database, Sam is assigned authority record #190 instead when the
record is imported.

 I have to admit I'm using the Import (Stage ... and Staged ...) Tools,
not the Perl script. Maybe the Perl script has a switch to force such
record assignment. I don't know; I'm just asking.

 Is there a way to fix this, i.e., is there a way to force the authority
record uploader to assign the authority record number that is in the 001
field of the incoming authority record?

 Thanks for your help, everyone.


___

Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha