That explains it perfectly! I was just worried that I had both dc.title and 
dc.title[] in my full export. Thank you so much!

 

 

 

From: Tim Donohue <[email protected]>
Date: Friday, October 4, 2019 at 10:19 AM
To: Shawn Kiewel <[email protected]>, Dspace Tech 
<[email protected]>
Subject: Re: metadata fields are arrays in export?

 

Hi Shawn,

When using the CSV export (with Batch Metadata Editing), DSpace always exports 
metadata fields using that "array-like" format.  It's not an actual array, but 
is simply how DSpace represents multi-language metadata fields in that CSV 
format (so the exported columns are structured like 
"schema.element.qualifier[language]").  See the final FAQ question ("Metadata 
values in CSV export seem to have duplicate columns") on this page for more 
details: 
https://wiki.duraspace.org/display/DSPACE/TechnicalFAQ#TechnicalFAQ-MetadatavaluesinCSVexportseemtohaveduplicatecolumns

 

So, what you are seeing in CSV export is expected behavior.  However, there are 
ways to clean up fields that have no language specified (as they sometimes 
appear as "dc.title" and other times as "dc.title[]"), see that FAQ again for 
details.

 

If you have further questions let us know on this list.


Tim

From: [email protected] <[email protected]> on behalf of 
Shawn Kiewel <[email protected]>
Sent: Friday, October 4, 2019 8:03 AM
To: Dspace Tech <[email protected]>
Subject: [dspace-tech] metadata fields are arrays in export? 

 

As you may know, I’ve been working on importing ETDs into my repository. I have 
determined that for items that need embargoing or for new items, I need to 
import via Simple Archive Format. I have successfully written records to the 
format and have imported those records. I am able to view the records just fine 
in the interface, view the bitstream, and when I view the full item record, all 
the expected metadata is in the correct fields. However, I’ve discovered 
something weird: when I export the metadata of the item that I have imported 
via SAF, all of my metadata fields are the array version, i.e. instead of 
having dc.title, I have dc.title[]. The only fields that are repeated in either 
dublin_core.xml or metadata_local.xml are dc.description.committee and 
dc.subject. Here are those files as well as the exported csv for an example 
record that has this behavior: 
https://gist.github.com/smkiewel/e8d8a30df55117ede41671b4b545e5b0. While I 
don’t still have the output of the successful import of this record, I have the 
output of a failure that happened right before the successful import that shows 
the processing of the metadata fields: 
https://gist.github.com/smkiewel/af6b3eaa8f701d4b2a5ae0c865ed82bc.

 

Thanks again for all the help.

Shawn

-- 
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/615DAE94-BE82-43B0-ADF7-6C34E725D075%40gmail.com.

-- 
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/AB7B37D2-8004-4BDF-99BB-8E9FCAF6DE9C%40gmail.com.

Reply via email to