We've been having problems with the Metadata Import function sometimes either
stopping after a few records or sending a "No changes detected" message. I
think I've narrowed the problem to the following circumstance:
* One or more records in the CSV file being imported contains a new
value for a field that in the existing DSpace metadata record is present, but
contains a blank/null value.
* For that record, the new value in the corresponding CSV file is the
only field that has a changed value.
* If the record is the first row in the CSV file, we will then get a
"No changes detected" message. If it occurs further down in the file, the
records above will process correctly, but then processing stops with the
problem row.
If the metadata field doesn't exist in the DSpace record at all, then there's
not a problem - the import will show that it is Adding the new field and value,
without Removing the original value (since it doesn't exist). But if the field
is present in the record but contains blank/null data, processing stops with
that record.
I cannot find any ERROR lines in the DSpace log file that appear to correspond
to this. Below are DEBUG lines that I *think* correspond to the last test I
ran, where the row in the CSV file contains a new value ("test") for the
dc.rights.license field, which exists in the matching DSpace record but
contains blank data:
2021-02-10 11:22:46,067 DEBUG org.dspace.storage.rdbms.DatabaseManager @
Running query "SELECT * FROM MetadataValue WHERE resource_id= ? and
resource_type_id = ? ORDER BY metadata_field_id, place" with parameters:
26629,2
2021-02-10 11:22:46,067 DEBUG org.dspace.app.bulkedit.MetadataImport @
[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test<mailto:[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test>,
2021-02-10 11:22:46,067 DEBUG org.dspace.app.bulkedit.MetadataImport @
[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test,,looking_for_schema=dc,looking_for_element=rights,looking_for_qualifier=license,looking_for_language=null<mailto:[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test,,looking_for_schema=dc,looking_for_element=rights,looking_for_qualifier=license,looking_for_language=null>
2021-02-10 11:22:46,067 DEBUG org.dspace.app.bulkedit.MetadataImport @
[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test,,found=null<mailto:[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadata_import:item_id=26629,fromCSV=test,,found=null>
2021-02-10 11:22:46,067 DEBUG
org.dspace.app.xmlui.aspect.administrative.FlowMetadataImportUtils @
[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadataimport:1<mailto:[email protected]:session_id=59CE8F97786E6F463ABBE0EBD1F95BCA:ip_addr=127.0.0.1:metadataimport:1>
items with changes identified
(I am new to DSpace support, and the log in DEBUG mode outputs an overwhelming
amount of data, so I could easily be missing something.)
Is this a known issue? I could not find any messages in the DSpace Issue
Tracker that seemed to match this circumstance.
Thanks, Kerry
[cid:F2F056B5-F514-4903-AFF0-0089CBD328C7]
Kerry Bouchard
DIRECTOR OF LIBRARY SYSTEMS
TCU LIBRARY
TCU BOX 298400
FORT WORTH, TX 76129
817-257-6809
[email protected]<mailto:[email protected]>
--
All messages to this mailing list should adhere to the DuraSpace Code of
Conduct: https://duraspace.org/about/policies/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/dspace-tech/5c10d8751b444045b04eae2521b6f06e%40tcu.edu.
