G'Day all,
We have about 350 records in a 6.x biblio which I've exported (simply) using the XML link, and am trying to import to a different site running 7.x

On attempting import we get a notice (and no import):
Notice: Undefined index: filetype in biblio_import_form_validate() (line 187 of /home/.../htdocs/drupal/sites/all/modules/biblio/includes/biblio.import.export.inc)..
I went to check the import/export mapping to see if anything jumped out, and got this notice:
Notice: Undefined variable: rows in biblio_admin_io_mapper_page() (line 1012 of /home/.../htdocs/drupal/sites/all/modules/biblio/includes/biblio.admin.inc).

There are cck fields in the 6.x biblio installation which are not needed/relevant in the 7.x version. Is it possible that cck fields are causing these problems or is there something more?

CommentFileSizeAuthor
#1 import_issue.png40.38 KBrjerome
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

rjerome’s picture

FileSize
40.38 KB

The first issue (undefined index "filetype") would indicate that you may not have selected a file type from the dropdown on the import form (see attached), although it should have generated a more user friendly message.

The second leads me to believe that you may not have enabled any of he import/export modules on the D7 side. If you exported in Endnote XML format from your D6 installation, you would have to enable the "Biblio EndNote XML" module on the D7 side.

Cheers,

Ron.

boabjohn’s picture

Hi Ron,
Thanks for the patient response...I've tried to bring a bit more focus to the matter this time.
We're still not there.
The export xml is set up on the D6 side using the export field mappings for EndNotex3
The link I use to export is provided by Biblio ass at: http://www.track.gov.au/publications/bibliography
The XML link produces a file titled BiblioEndNote8.xml
This file, when opened in an XML editor, throws a parsing error:

xmlParserEntityRef: no name
Line 189, Col: 1651

Now that I've enabled the Biblio EndNote module in the D7 site, we have a better chance of importing :-) but we still get an unexpected result.
On import in the D7 site, we get only 23 records instead of the expected 350. Perhaps this is due to the parser problem above...
Where should I be looking for problems?
Thanks in advance!

rjerome’s picture

This seems to be an issue with encoding of the URL's. Which version of Biblio are you using on the D6 side?

boabjohn’s picture

Hi Ron,
We're at 6.x-1.15. I guess we could update if necessary?
JB

rjerome’s picture

Ahh, that explains it. I just created a 6.x-1.17 release that rolls up all the accumulated bug fixes in that branch.

boabjohn’s picture

Brilliant Ron!
Import wass successful after the update to 6.1.17
Thanks indeed,
JB

rjerome’s picture

Excellent!

I'll get that other kit to you soon. I was talking to the XC maintainer and he was very happy to hear of the developments made on that front.

Ron.

boabjohn’s picture

Status: Active » Closed (fixed)