UFAL/Run Metadata QA curation task on Oxford data

[Paurikova2]

ahoj, az budes mit chvili muzes pustit https://github.com/dataquest-dev/DSpace/pull/1237 nad tema zmigrovanejma datama z Oxfordu? Jen by me zajimalo, jestli tam maj taky itemy, ktery jsou ve vice "versionhistory", nektery u nas jsou mirne necekany (napr. http://hdl.handle.net/11234/1-3719 ve vztahu k http://hdl.handle.net/11234/1-5415 )

[Paurikova2]

Based on the migrated data on our instance (8443), for handle 11234/1-3719
there are two records in the Version table. The first one represents the current item, while the second one (handle: 11234/1-5415
) is not clickable and is marked as a Workspace item.
This is comparable to Lindat, where for the given handle there is only a link to the current item (i.e., not to 11234/1-5415).

For handle 11234/1-5415
, the table contains two records, similarly to Lindat, and both are clickable. The current record corresponds to version 2.

[Paurikova2]

Identified Issues (Metadata QA on migrated Oxford data)

Invalid type values (Text, text, Corpus) [20.500.14106/5010, 20.500.14106/0163] - needs lr.curation.metadata.expected.types to be configurated
Non-repeatable metadata misconfiguration - dc.date.accessioned should be allowed as repeatable in lr.curation.metadata.nonrepeatable
dc.subject should be removed from required/recommended fields lr.curation.metadata.recommended (missing in some data)

Specific Data Errors

20.500.14106/5001 → local.submission.note is empty
20.500.14106/5002 → duplicate title Beowulf (duplicate of 20.500.14106/1897)
20.500.14106/0572 → missing dc.rights.uri, dc.rights
20.500.14106/0270 → has labels but no files
20.500.14106/0673 → missing back-reference from 20.500.14106/A03924 as dc.relation.replaces

Summary

Configuration issues in metadata QA rules
Data inconsistencies in migrated records
Missing or invalid metadata values
Broken relationships between items

[Paurikova2]

#1288

[Paurikova2]

[NODE_VERSION][YARN_INSTALL] Incompatible Node.js version

Error

Dependency installation failed with: The engine "node" is incompatible with this module (typically on Node 20+).

Steps to reproduce

Run yarn install --frozen-lockfile using Node 20+.

Solution

Switch to Node 16.x or 18.x, then run yarn install --frozen-lockfile again.

[Paurikova2]

[CYPRESS][INSTALL_BINARY] Cypress download failed

Error

Installation failed with: The Cypress App could not be downloaded.

Steps to reproduce

Run yarn install --frozen-lockfile in an environment with restricted or unstable access to Cypress download servers.

Solution

Disable Cypress binary download during install: CYPRESS_INSTALL_BINARY=0 yarn install --frozen-lockfile.

[Paurikova2]

[BUILD][MEMORY][OOM] Out-of-memory during build

Error

Production build failed due to Node.js memory limits (out-of-memory).

Steps to reproduce

Run production build with low memory available for the Node process.

Solution

Increase Node memory limit and rerun build: NODE_OPTIONS=--max-old-space-size=4096.

[Paurikova2]

[YARN_LOCK][MERGE_CONFLICT] Merge conflict in lockfile

Error

Install/build failed after merge because yarn.lock had unresolved conflicts.

Steps to reproduce

Merge branches with conflicting dependency updates in yarn.lock.

Solution

Resolve yarn.lock conflict by selecting a consistent lockfile state, run yarn install to regenerate dependency integrity, then continue with commit/build.