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. * DSpace Angular UI Issues: https://github.com/DSpace/dspace-angular/issues (For any issues that look UI specific, or if you aren't sure feel free to log them here) * DSpace Backend / REST Issues: https://github.com/DSpace/dspace/issues (Also errors in Commandline can get logged here) Thanks in advance for your early testing! Tim ________________________________ From: [email protected] 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 ? 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 -- 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 [email protected]. 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. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/DM5PR2201MB11482EDFC2954119BFDCDDDEED979%40DM5PR2201MB1148.namprd22.prod.outlook.com.
