Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

OAI-ORE exporter fails for too deeply nested metadata #10809

Open
vera opened this issue Aug 28, 2024 · 0 comments · May be fixed by #11190
Open

OAI-ORE exporter fails for too deeply nested metadata #10809

vera opened this issue Aug 28, 2024 · 0 comments · May be fixed by #11190
Labels
Type: Bug a defect

Comments

@vera
Copy link
Contributor

vera commented Aug 28, 2024 •
edited
Loading

What steps does it take to reproduce the issue?

  1. Create custom metadata block with nesting level > 2 (e.g. our block contains "contributors", which contains "personal", which contains "givenName", "familyName",...)
  2. Create dataset with that block
  3. Publish dataset/trigger OAI-ORE export

What happens?

[#|2024-07-18T14:52:24.430+0000|SEVERE|Payara 6.2023.8||_ThreadID=208;_ThreadName=__ejb-thread-pool4;_TimeMillis=1721314344430;_LevelValue=1000;|
  java.lang.IndexOutOfBoundsException: Index: 0
	at java.base/java.util.Collections$EmptyList.get(Unknown Source)
	at org.eclipse.parsson.JsonArrayBuilderImpl$JsonArrayImpl.get(JsonArrayBuilderImpl.java:462)
	at org.eclipse.parsson.JsonArrayBuilderImpl$JsonArrayImpl.get(JsonArrayBuilderImpl.java:360)
	at edu.harvard.iq.dataverse.util.bagit.OREMap.getJsonLDForField(OREMap.java:478)
	at edu.harvard.iq.dataverse.util.bagit.OREMap.getOREMapBuilder(OREMap.java:121)
	at edu.harvard.iq.dataverse.util.bagit.OREMap.getOREMap(OREMap.java:92)
	at edu.harvard.iq.dataverse.util.bagit.OREMap.getOREMap(OREMap.java:88)
	at edu.harvard.iq.dataverse.export.InternalExportDataProvider.getDatasetORE(InternalExportDataProvider.java:63)
	at edu.harvard.iq.dataverse.export.OAI_OREExporter.exportDataset(OAI_OREExporter.java:28)
	at edu.harvard.iq.dataverse.export.ExportService.cacheExport(ExportService.java:387)
	at edu.harvard.iq.dataverse.export.ExportService.exportAllFormats(ExportService.java:269)
	at edu.harvard.iq.dataverse.engine.command.impl.FinalizeDatasetPublicationCommand.onSuccess(FinalizeDatasetPublicationCommand.java:289)
	at edu.harvard.iq.dataverse.EjbDataverseEngine.completeCommand(EjbDataverseEngine.java:343)
	at edu.harvard.iq.dataverse.EjbDataverseEngine.submit(EjbDataverseEngine.java:280)

What did you expect to happen?

OAI-ORE export to succeed

Which version of Dataverse are you using?

6.2, also tested on 6.3

Any related open or closed issues to this bug report?

did not find any

Are you thinking about creating a pull request for this issue?

yes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Bug a defect
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: fix bug in OAI-ORE exporter related to nested compound fields vera/dataverse
1 participant
@vera