Opened 14 years ago

Closed 14 years ago

#435 closed defect (fixed)

'???' added to 'sources' table on single/multiple XML file import

Reported by: awalsh Owned by: Developer
Priority: major Milestone: v2.7.0
Component: General Version: v2.6.3
Keywords: sources, XML import, MEF import Cc: craig.jones@…

Description

Using GN 2.6.3 a '???' is added to the 'name' column of the 'sources' table whenever a single XML file or multiple XML (batch) file import is done. It appears to be because the source XML file has no siteName so the program inserts a '???' instead for the name column and the local siteID (uuid) into the uuid column. The side effect of this bug is that a '???' appears on the Advanced Search->Restrict To->Catalog drop down list which is confusing as this list will already an entry containing the local siteName.

I shown this issue to Craig Jones a BlueNet Geonetwork developer in Australia. Craig has kindly written a patch (attached) to fix this issue. The patch has been tested and it works with the BlueNet Geonetwork.

I have also tested other import cases of XML copy/paste, MEF file upload: single/multiple and MEF file upload from another siteID. For these other import cases the local siteID and local siteName are added to the sources table except in the case of a MEF file from another siteID in which the other siteID and siteName is added.

Finally a comment about the sources table. Looking at the way the table is used it makes my wonder why we need to be adding entries to the sources table from 'local' sources. I would have thought that the sources table was supposed to show 'non-local' sources such as harvests from other sites of harvest uuid's.

Attachments (1)

importer-gn-trunk.patch (640 bytes ) - added by awalsh 14 years ago.
Patch for trunk

Download all attachments as: .zip

Change History (2)

by awalsh, 14 years ago

Attachment: importer-gn-trunk.patch added

Patch for trunk

comment:1 by simonp, 14 years ago

Resolution: fixed
Status: newclosed

Fixed in svn rev 7321 for 2.6.x and 7320 for trunk

Note: See TracTickets for help on using tickets.