Error during bagit creation

[Rondineli Gama Saad]

Hello,

I have installed the dataverse version 6.5 and I am trying to create individuals bagit from each dataset. But when I try to create them I got the error bellow: 

https://gist.githubusercontent.com/rondinelisaad/404499647693d600272a1293a90c865e/raw/2fc39d4bbe39c69ac12b60ac5fad91ec9f0bc408/bagit-error

To create the bagit package I did:
curl -H X-Dataverse-key:$API_TOKEN  http://localhost:8080/api/datasets/:persistentId/?persistentId=doi:10.48331/SCIELODATA.OVAOFJ
export ID=13150
export API_TOKEN='MY API TOKEN'
curl -X POST -H "X-Dataverse-key: $API_TOKEN" http://localhost:8080/api/admin/submitDatasetVersionToArchive/$ID/1.0

During create the package stay in this situation:

-rw-rw-r--. 1 glassfish glassfish   5618 Aug 25 11:48 doi-10-48331-scielodata-rwevda-datacite.v1.0.xml
-rw-rw-r--. 1 glassfish glassfish    375 Aug 25 11:49 doi-10-48331-scielodata-rwevdav1.0.zip.partial

The package it supposed to be saved in the directory /preservacao/dataverse. The owner of this directory is the same as it is running dataverse.

drwxr-xr-x.  9 glassfish glassfish 4.0K Aug 25 11:56 dataverse

I hope someone can help me! 

Best Regards,

[James Myers]

With a quick look - from your log, it seems that the account/api token being used doesn’t have access to read the files. I expect that’s the source of the later null pointer problem.

 

-- Jim

Esta mensagem pode conter informação confidencial, sendo seu sigilo protegido por lei. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não pode usar, copiar ou divulgar as informações nela contidas ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor, avise imediatamente ao remetente, respondendo o e-mail e em seguida apague-a. Agradecemos sua cooperação.


This message may contain confidential information and its confidentiality is protected by law. If you are not the addressed or authorized person to receive this message, you must not use, copy, disclose or take any action based on it or any information herein. If you have received this message by mistake, please advise the sender immediately by replying the e-mail and then deleting it. Thank you for your cooperation.

--
You received this message because you are subscribed to the Google Groups "Dataverse Users Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dataverse-commu...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/ec82e693-f758-4186-b116-533123e7c0f2n%40googlegroups.com.

[Rondineli Gama Saad]

Hi Jim,

my user is super admin. It is supposed to work, right?

Best Regards,

[Rondineli Gama Saad]

Dear Jim,

I found out the problem. I set on my nginx configuration to block many bot agents. I created an exception and now it is working. Tks for you help

Best Regards,

[Rondineli Gama Saad]

Hello,

the other problem is to send again the datasets that I sent and got the error. Because now, when I try to send again I get the error: {"status":"ERROR","message":"Version was already submitted for archiving."}

Somebody know how to force to create the bagit again?

Best Regards,

[Rondineli Gama Saad]

Hello,

I got the solution. To see the status in the database dvndb I run the command:

SELECT
    id, versionnumber, minorversionnumber, versionstate,
    archivetime, archivalcopylocation, externalstatuslabel, archivenote
FROM datasetversion
WHERE dataset_id = 'YOUR DATASET ID'
ORDER BY versionnumber DESC, minorversionnumber DESC;

The result:

  id  | versionnumber | minorversionnumber | versionstate | archivetime |                 archivalcopylocation                 | extern
alstatuslabel | archivenote
------+---------------+--------------------+--------------+-------------+------------------------------------------------------+-------
--------------+-------------
 3469 |             1 |                  0 | RELEASED     |             | {"status":"failure","message":"Bag not transferred"} |  

To clean the row table I run:

UPDATE datasetversion
SET archivetime = NULL,
    archivalcopylocation = NULL,
    externalstatuslabel = NULL,
    archivenote = NULL
WHERE id = 3469 ;

Where ID corresponding to the id field in the result above.

After that I run the command:

curl -X POST -H "X-Dataverse-key: $API_TOKEN" http://localhost:8080/api/admin/submitDatasetVersionToArchive/$ID/1.0

[James Myers]

Glad you got it working. There is an api call as well: https://guides.dataverse.org/en/latest/api/native-api.html#delete-the-archival-status-of-a-dataset-by-version .

To view this discussion visit https://groups.google.com/d/msgid/dataverse-community/93a263da-95d9-4059-9b93-0ffb90185012n%40googlegroups.com.

[Rondineli Gama Saad]

Thanks for share the link. I think it is much easier following the link instruction.

Best Regards,