When using Dublin Core in Archivematica with repeating fields it's not clear how they will be resolved in Scope. I believe only one of the fields will be used, but I believe because we're working with a dict type once it is parsed then the actual field that will come out in the display is unpredictable. (Though I'm largely seeing the second or last field value appear in the UI).
UI screenshot

XML as stored in my DIP
<mets:mdWrap MDTYPE="DC">
<mets:xmlData>
<dcterms:dublincore xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xsi:schemaLocation="http://purl.org/dc/terms/ https://dublincore.org/schemas/xmls/qdc/2008/02/11/dcterms.xsd">
<dc:title>Scope sample collection</dc:title>
<dc:creator>Creator One</dc:creator>
<dc:subject>Subject One</dc:subject>
<dc:subject>Subject Two</dc:subject>
<dc:subject>Subject Three</dc:subject>
<dc:subject></dc:subject>
<dc:subject></dc:subject>
<dc:description>Dublin core descriptive information</dc:description>
<dc:publisher>Publisher one</dc:publisher>
<dc:publisher>Publisher two</dc:publisher>
<dc:contributor>Contributor one</dc:contributor>
<dc:contributor>Controbutor two</dc:contributor>
<dc:date></dc:date>
<dc:type></dc:type>
<dc:format>Format one</dc:format>
<dc:format>Format two</dc:format>
<dc:identifier>id:one</dc:identifier>
<dc:identifier>id:two</dc:identifier>
<dc:source>Source one</dc:source>
<dc:source>Source two</dc:source>
<dc:language>en</dc:language>
<dc:language>fr</dc:language>
<dc:relation></dc:relation>
<dc:coverage></dc:coverage>
<dc:rights></dc:rights>
</dcterms:dublincore>
</mets:xmlData>
</mets:mdWrap>
</mets:dmdSec>
And this was generated from the Demo CSV sample transfer with an additional SIP level metadata row. I have attached it below for ease of testing in future.
DemoTransferCSVWithSIPDC.zip
The DIP for uploading (a zipped tar):
demoCSV-2ece5811-06c5-407c-8866-cd42088e9fdf.zip
When using Dublin Core in Archivematica with repeating fields it's not clear how they will be resolved in Scope. I believe only one of the fields will be used, but I believe because we're working with a
dicttype once it is parsed then the actual field that will come out in the display is unpredictable. (Though I'm largely seeing the second or last field value appear in the UI).UI screenshot
XML as stored in my DIP
And this was generated from the Demo CSV sample transfer with an additional SIP level metadata row. I have attached it below for ease of testing in future.
DemoTransferCSVWithSIPDC.zip
The DIP for uploading (a zipped tar):
demoCSV-2ece5811-06c5-407c-8866-cd42088e9fdf.zip