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

Clarification for the “Submit Incomplete Dataset” feature #9942

Closed
stevenferey opened this issue Sep 20, 2023 · 6 comments · Fixed by #9966
Closed

Clarification for the “Submit Incomplete Dataset” feature #9942

stevenferey opened this issue Sep 20, 2023 · 6 comments · Fixed by #9966
Milestone

Comments

@stevenferey
Copy link
Contributor

entrepot.recherche.data.gouv.fr team

  • What happens?

Version 5.14 of Dataverse allows the creation of partial dataverse with the API with only the author's information:

https://guides.dataverse.org/en/5.14/api/native-api.html#submit-incomplete-dataset

It's not always the case !
When the setting ":MetadataLanguages"
is configured and the dataverse has the value "Dataset Metadata Language" to "Chosen at Dataset Creation":

https://guides.dataverse.org/en/5.14/installation/config.html?#allowing-the-language-used-for-dataset-metadata-to-be-specified

Capture d’écran du 2023-09-20 16-55-43

In this case, a language that is part of the ":MetadataLanguages" list must be declared in the incomplete dataset.

  • To whom does it occur (all users, curators, superusers)?

To users wanting to create a partial dataset with the API

  • What did you expect to happen?

Is this the expected behavior?
If so, add clarification in the documentation for this scenario?

Which version of Dataverse are you using?

5.14

@pdurbin
Copy link
Member

pdurbin commented Sep 21, 2023

Heads up to @ErykKul and @DieuwertjeBloemen who added the feature originally:

@ErykKul
Copy link
Collaborator

ErykKul commented Sep 21, 2023

Hi. I think we will add that scenario in the documentation. We should also add the information about the solr index schema update and reindexing when you are planning to use that feature, as I do not see it being mention yet in the documentation.

@stevenferey
Copy link
Contributor Author

Hi @ErykKul,

The functionality being available from V5.14, updating the schema and reindexing the data is automatically done when upgrading Dataverse to V5.14 I think?

Maybe no need to mention this in the feature documentation. Only the difference in behavior when ":MetadataLanguages" is specified.

Thank you
Steven.

@ErykKul
Copy link
Collaborator

ErykKul commented Sep 28, 2023

Hi @stevenferey

Reindexing is needed for the MyData page to work correctly after each time the feature is turned on. See also #9836 and the PR I did to address it #9964
With that PR merged, only the reindexing during the installation of the new version will be needed. Before that, you will need to reindex after turning this feature on.

@ErykKul
Copy link
Collaborator

ErykKul commented Sep 28, 2023

@stevenferey
I did update the documentation in the PR. Feel free to comment on it, suggest changes, or push commits directly to the PR branch.

@pdurbin pdurbin added this to the 6.1 milestone Sep 28, 2023
@stevenferey
Copy link
Contributor Author

Hello @ErykKul ,

The additional documentation is very clear !
Thank you very much

Steven.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants