...
Open your CSV and sort or filter on those columns to find the blank ones. Enter appropriate values or remove affected rows from the CSV.
Processing
Report type: processing_report
...
The report contains one row per unique not-found term. That is, if you have used a new term for a given vocabulary/authority in 100 different records or fields, it will appear here once.
The report has four columns: term type (i.e. personauthorities), term subtype (i.e. person or ulan_pa), identifier (the “shortID” the mapping process created for the new term), and value (the term value as it was found in your original data)
The intent of this report is two-fold:
If new terms are unexpected, you can use this information and searching your CollectionSpace instance to investigate whether case differences, punctuation differences, or typos caused your terms not to match. Then you can update your original file with the expected term form. OR…
If you want to create fuller term records, before linking this data to the terms, you can use the values in this form to create new CSVs for separate batch import of term records. To do that:
Filter this report to a given type/subtype combination (i.e. local person names)
Copy the values out into the termDisplayName column of the Person CSV template
Add in any more details you’d like to import
Batch import each of those CSV forms (one batch per term type).
After importing your new Terms, you need to delete the batch you started with start over with it. The processing step on the new batch will match to the terms you just imported.
If you proceed with this batch, it will create new stub records with the identifiers generated by the batch processor, which don’t match the identifiers generated by CollectionSpace when you imported the fuller term records. You will end up with duplicate term records!
If you do not want to create fuller term records, you can proceed with this batch without importing the terms separately, and the CSV Importer will create “stub” records for the new Terms that only include a Display name.
Transferring
WARNING: Some records did not transfer. See CSV report for details
This one is pretty self-explanatory. Look in the CSV report in the Files box to learn which records did not transfer. Filter the spreadsheet to rows where “XFER_status” column = “failure”. Details on the failure(s) will be in the “XFER_message” column.
ERROR: no appropriate transfer action detected for record
There was a mismatch between the status of this record in CollectionSpace and the type of transfer action(s) you selected. Examples could include:
Record status = new, but you checked only “Update existing records?” or “Delete existing records?”
Record status = existing, but you checked only “Create new records?”
If any of these errors was unexpected and the Transferring step is finished, you will need to start over:
Use the CSV report to create a new import file
Delete rows for records that transferred successfully
Delete any INFO, WARNING, or ERROR data columns added by the CSV Importer
Create a new batch and make sure to select appropriate transfer actions on the Transferring step