IQSS / IQSS/dataverse

Harvesting : message "javax.ejb.EJBTransactionRolledbackException, Exception thrown from bean: java.lang.NullPointerException"

Open
#7,546 9 comments 1 reaction 1 assignee View on GitHub

@tjouneau is already working on this.

Since Oct 13, 2022.

Feature: Harvesting Type: Bug User Role: API User
Dominant language
Java
Stars
1.1k
Forks
564
Avg merge
2d 2h
Merged PRs (30d)
29

Description

Hi
I'm going on here with other harvesting problems from Dataverse 5.2. I'm opening another issue, the behaviour and messages obtained being different.
I get the message
javax.ejb.EJBTransactionRolledbackException, Exception thrown from bean: java.lang.NullPointerException
for every record from these two repositories :

Regarding Ortolang, a look at the XML record shows three entries for dc:identifier (I checked this after having read https://github.com/IQSS/dataverse/issues/7497) ; they're however the same and the first one is valid. It's a handle, which I believe Dataverse should manage?

Here are the client configurations :

Alias : ordar_test
Server URL : https://ordar.otelo.univ-lorraine.fr/oai
Local dataverse : moissonnage_ordar_test
OAI set : HYDROLOGY
Metadata format : oai_dc
Repository type : Generic OAI archive

Alias :ortolang_test
Server URL :http://repository.ortolang.fr/api/oai
Local dataverse : 
OAI set : a73bcbad-4c94-47f0-97e3-08c9846d791d
Metadata format : oai_dc
Repository type : Generic OAI archive

These two repositories both present oai_dc and oai_datacite metadata. If I try the latter I get the message
Exception processing getRecord(), oaiUrl=https://ordar.otelo.univ-lorraine.fr/oai, identifier=info:doi:10.24396/ORDAR-56, edu.harvard.iq.dataverse.api.imports.ImportException, Unsupported import metadata format: oai_datacite.

Here are the logs for the attempts in the oai_dc format :
harvest_ortolang_test_2021-01-27T10-06-53.log.gz
harvest_ordar_test_2021-01-27T09-32-46.log.gz

Again, thanks in advance for your time or any insight.

Best
Thomas

EDIT : DV version changed (5.2 and not 5.3)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.