Hmm. Did they go missing at the import step or are they missing at the
export stage?

I ask because I had weird things happen when I was first building my Koha
database up that item-level data would affect the import and some would not
import.

Certain records would get read as duplicates because of holdings mistakes
(field 952) and then they would not import.

Do you have 952 data in your test records?

Anyway, this comes from my relatively newbie experience...
Thank you,

Jesse



On Fri, Oct 23, 2015 at 10:57 AM, David Liddle <david_lid...@wycliffe.net>
wrote:

> I'm preparing to help a library switch to Koha over the next few months. In
> testing the "Export data" tool today, I discovered that 2 of the 4
> bibliographic entries are missing from the export. (The entries are only
> samples used to test the import and linking of records.) The XML export
> file and the MARCXML files saved from the individual records are attached
> to this message, assuming they passed through any list filters. Can someone
> help me understand what causes the omission of these two records?
>
> Thank you!
>
> ------------------------------
>
> *David Liddle*
>
> *IT Support Specialist*
> Wycliffe Global Alliance - Europe Area
> Siegenweg 30, 57299 Burbach, Germany
>
> *Direct:* david_lid...@wycliffe.net
> *Support:* sos_eur...@wycliffe.net
> *Bomgar:* https://sos.wycliffe.net
> <
> https://sos.wycliffe.net/download_customer_connector.ns?id=65&name=David+Liddle
> >
>
> *Office:* +49 2736 298 302, Ext. 107
> *Mobile:* +49 176 421 473 69
> *Skype:* dfliddle
> _______________________________________________
> Koha mailing list  http://koha-community.org
> Koha@lists.katipo.co.nz
> https://lists.katipo.co.nz/mailman/listinfo/koha
>



-- 
Jesse A Lambertson
Librarian
Sultan Qaboos Cultural Center <http://www.sqcc.org/>

Ph: (202)-677-3967 Ext. 104
jlambert...@sqcc.org
_______________________________________________
Koha mailing list  http://koha-community.org
Koha@lists.katipo.co.nz
https://lists.katipo.co.nz/mailman/listinfo/koha

Reply via email to