Hi all,
@Tim, I think Jacob issue is caused by the way he dumped his old database
and the way he tried to restore it. Those " thousands of invalid command
/N" should've not shown up if the database was dumped in a custom binary
format and the new server database was cleaned (emptied) or even
Hi Sean,
This issue is a known issue which some sites encounter during the upgrade to
DSpace 7 if they have previously ignored migrations which never ran during a
past 5.x ->6.x upgrade?. Essentially, to summarize, there are two "5.7"
migrations which can fail during the upgrade to 7.x...
I’ve tried importing with the postgres account, using an elevated command
prompt, in pgadmin and they are all giving the same errors. It’s still
failing. I’m at a loss now. There’s a ton of tables missing when it finishes
importing.
--
Jake Cameron, BCS(UNB)
Systems Support Specialist III
Hi Jorge,
As of DSpace 6 (and above), Communities & Collections have metadata just like
Items. So that means the Community/Collection name (or title) is stored in a
"dc.title" metadata field linked to the Community/Collection, in the same way
that an Item's name (or title) is also stored in a
Thank you, everyone!
Kim, I am working on recreating the error...
On Tuesday, January 17, 2023 at 11:42:19 AM UTC-5 Tim Donohue wrote:
> Hi Tianyi,
>
> The Batch Import / Bulk Upload command wasn't available in the DSpace 7
> Admin UI until the 7.4 release. See the release notes at
>
Hi Tim
Thanks for the quick reply , I will have a look and see if i can
successfully run that tool to generate a diagram.
Just a quick question and only reply if you got this on the tip of
your tongue where on earth is a collection/community name stored in
this new structure ? I cant ,
