-
Notifications
You must be signed in to change notification settings - Fork 2
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
Indexing: Failure to index one dataset, results in exception when clicked. #69
Comments
So to me it looks like it may be more of a curation issue, rather than dev. - if it's just a matter of going into the db. and fixing whatever is wrong with the author for the dataset? But then it may also be something in our code, that allows a user to create a dataset with "bad" author field; or allows to edit it in a way that saves it, but then breaks the dataset... The dataset passes our validation API btw - so it's not an outright constraint violation. |
We have changed something about author affiliations in 4.20 - correct?
that throws a null pointer. so it looks like it is now possible to have an affiliation field that's no null; but has a null value. Hmm. |
The PR at IQSS/dataverse#6619 removes parenthesis from author affiliation values in the Search API results. |
|
If we want to delete the offending record here is the diagnostic query(hat tip Leonid): SELECT v.id, f.datasetfieldtype_id, t.name, fp.datasetversion_id The "v.id" in the result can be used in the delete query. /4776468 - this is the id from the production clone that I had locally delete from datasetfieldvalue where id = xxxxxx; |
Just to document it, this was fixed without running direct db queries; by creating a draft version (by edit -> save - no need to make any actual changes), then publishing, as a superuser, without incrementing the version. This updates the latest version, removing the empty/null values in the process. (and then deletes the draft) |
With v4.20, index all worked for all datasets but one. That one has an existing record but when you click on it, throws an exception.
Indexing directly throws an error.
Leonid reported seeing these errors in the log on page load:
It looks like it's something with the author of the dataset: (L.A.)
The dataset: https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/2U2N87
The text was updated successfully, but these errors were encountered: