dspace-angular / DSpace 7 beta 4.1 / Bug with metadata schemes ?

112 views
Skip to first unread message

Michael Plate

unread,
Mar 4, 2021, 12:16:46 PM3/4/21
to DSpace Technical Support
Hi,

dspace-angular (e4454de from git), dspace 7 beta 4.1.

dspace-angular:
Could not compile prod, ends up out-of-memory (FATAL ERROR: Ineffective
mark-compacts near heap limit Allocation failed - JavaScript heap out of
memory), using the package.json from the build before (with
--max_old_space_size=8192) works.

Creating a new metadata scheme creates, but does not list after that
(same on build before).
Changing and revisiting urls does not help, reloading
/admin/registries/metadata helps.

Metadata fields with empty qualifier created in any scheme are written
to PostgreSQL as empty string, not "null".

I exported ind DSpace 5 via

~/bin/dspace packager -o filterBundles=TEXT,THUMBNAIL -t AIP -d -a -i
123456789/2013093044022 -e …

and copied the files to the new DSPace 7.

When ingesting via

~/bin/dspace packager -r -u -a -e <some mail> -p 123456789/0 -t AIP -f
-o skipIfParentMissing=true -o createMetadataFields=true <file>

I get the following error:

org.dspace.content.crosswalk.CrosswalkException: The 'price.null'
element has not been defined in this DSpace instance.
at
org.dspace.content.crosswalk.CrosswalkMetadataValidator.checkMetadata(CrosswalkMetadataValidator.java:107)
[…]

"price" is the element, the qualifier is not set - short solution is

update metadatafieldregistry set qualifier = null where qualifier = '';

in PostgreSQL.


Michael


Tim Donohue

unread,
Mar 4, 2021, 1:31:19 PM3/4/21
to Michael Plate, DSpace Technical Support
Hi Michael,

We'd recommend testing the new DSpace 7 "main" branch (latest code) if you'd like to do thorough testing & bug reporting.  Several of those bugs have already been fixed there (e.g. the out of memory build error is fixed by upgrading to Node 12 or 14, which we now require).  I'm not sure about the metadata schemes issue, but it'd be best to re-test with the latest code.

With any that are still reproducible on the "main" branch... If you are willing, it'd be wonderful if you could log each bug in our Issues (with steps to reproduce).  That way, I can get them scheduled for analysis from one of our developers.

Thanks in advance for your early testing!

Tim



From: dspac...@googlegroups.com on behalf of Michael Plate
Sent: Thursday, March 4, 2021 11:17 AM
To: DSpace Technical Support
Subject: [dspace-tech] dspace-angular / DSpace 7 beta 4.1 / Bug with metadata schemes ?

--
All messages to this mailing list should adhere to the 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 dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/4bc78481-125f-3cd2-85cd-775127f5bbb2%40bibliothek.uni-kassel.de.

Michael Plate

unread,
Mar 5, 2021, 12:23:28 PM3/5/21
to DSpace Technical Support
Hi Tim,

Am 04.03.21 um 19:31 schrieb Tim Donohue:
> Hi Michael,
>
> We'd recommend testing the new DSpace 7 "main" branch (latest code) if
> you'd like to do thorough testing & bug reporting.  Several of those
> bugs have already been fixed there (e.g. the out of memory build error
> is fixed by upgrading to Node 12 or 14, which we now require).

Yes, works now.

> I'm not
> sure about the metadata schemes issue, but it'd be best to re-test with
> the latest code.
>
> With any that are still reproducible on the "main" branch... If you are
> willing, it'd be wonderful if you could log each bug in our Issues (with
> steps to reproduce).  That way, I can get them scheduled for analysis
> from one of our developers.
[…]

I'll do the github stuff on monday - I checked out the current version
(I hope, just https://github.com/DSpace/DSpace.git), and after a short
try these problems still exists.

Nice weekend,

Michael

Reply all
Reply to author
Forward
0 new messages