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.

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

Publishing: When trying to use the overwrite publishing option, error message with failed to publish #8400

Closed
sbarbosadataverse opened this issue Feb 4, 2022 · 5 comments · Fixed by #8562
Assignees
Labels
Feature: Publishing & Versions Type: Bug a defect User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured
Milestone

Comments

@sbarbosadataverse
Copy link

sbarbosadataverse commented Feb 4, 2022

Navigate to this dataset and updates the related publication fields to include metadata for "id type" "id number" and "url" field: https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi%3A10.7910%2FDVN%2F0C3BTS

Select save and get a successful draft.

Select publish and choose the overwrite option and error message shows up

superuser functionality

Expected that the publish would overwrite the existing version.

Screenshots:

Screen Shot 2022-02-04 at 2 21 38 PM

@sbarbosadataverse sbarbosadataverse added Type: Bug a defect Feature: Publishing & Versions User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured labels Feb 4, 2022
@scolapasta scolapasta added this to the 5.10 milestone Feb 4, 2022
@pdurbin pdurbin added the Medium label Feb 9, 2022
@pdurbin
Copy link
Member

pdurbin commented Feb 9, 2022

This is the "curate new version" feature (superuser only).

@scolapasta @qqmyers and @sekmiller have discussed briefly. @sekmiller unable to reproduce.

Has happened on multiple drafts. Draft still able to be deleted.

Related to inter versions? If one version has a space?

Code assumes previously published version from list. Could it have the wrong version? Line 102. More details in Slack. #8382 is about version differences.

@scolapasta can probably upload the stacktrace.

No actual file metadata changes. Probably from the draft.

Around line 155, curate command is trying to delete links to file metadatas. Watch out for references to file metadatas.

@sekmiller sekmiller moved this from Up Next 🛎 to IQSS Team - In Progress 💻 in IQSS/dataverse (TO BE RETIRED / DELETED in favor of project 34) Feb 10, 2022
@sekmiller sekmiller self-assigned this Feb 10, 2022
@valentinapasquale
Copy link

Hello,
I have just encountered the same error, but I am still working with Dataverse 5.3. Can anyone help?
I have checked the "id" that is mentioned in the error message: I suspected it referred to a file id and that it had been removed for some reasons, but all files are there and there is no file with that id (so it probably refer to another id...). Is it working if I create a new version instead of overwriting?
Thanks for the help!
Valentina

@scolapasta
Copy link
Contributor

@valentinapasquale The removal is a technical aspect of how overwrite works (since what the code for overwrite copies the info from the draft to the last published, then deletes the draft, effectively "removing" the filemetadata objects the draft created). We are still trying to determine the cause of the error, so any additional info you have about that dataset - since it doesn't always happen - would be helpful.

Creating a new version instead should definitely work.

@scolapasta scolapasta removed this from the 5.10 milestone Mar 10, 2022
@valentinapasquale
Copy link

@scolapasta this is the dataset: https://dataverse.iit.it/dataset.xhtml?persistentId=doi:10.48557/TRGQOD. We want just to correct the spelling of one of the authors' names (Paniello --> Panniello), that was the only change in the draft. That's why I thought overwriting was the best option.
Thanks for the quick and clear answer!

@scolapasta
Copy link
Contributor

@valentinapasquale One other approach you could do is to make the change directly in the DB. It's obviously more risky, but with a relatively simple change like this, shouldn't be too bad. Let me know if you'd like any help to walk you through it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature: Publishing & Versions Type: Bug a defect User Role: Superuser Has access to the superuser dashboard and cares about how the system is configured
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants