Re-Posting my answer on dspace-commuity forum here just to give my final
solution.
Based on your answers i've discovered that ORE is nothing more than a
special XML bitstream, that define bitstreams as links. So i decided to
write a Python class to create a "Simple Format Archive" packager usin
We're still experiencing the same issue as well with Dspace 6.3 and XMLUI.
The workaround that I've been using so far is to create a custom segment in
Google Analytics to remove any traffic where the Landing Page is "(not
set)". That seems to bring the traffic down to where we would expect it to
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
Date: Friday, October 4, 2019 at 10:19 AM
To: Shawn Kiewel , Dspace Tech
Subject: Re: metadata fields are arrays in export?
Hi Shawn,
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
How to design dspace jspui home page communities in horizontal view?
--
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
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 re
