You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just changed this line in commit 319ff15 to make it tolerate multiple results. However, it should be investigated in more detail why there are multiple DataSubmission objects with the same doi. I found 6 examples:
These all date from the early days of hepdata.net in 2017/2018 when the submission code was buggy and the procedure for replacing uploads was not done cleanly. It should be investigated how to clean up the database to remove the duplicate DOIs.
The text was updated successfully, but these errors were encountered:
When reindexing the QA instance after deploying PR #766 some of the records gave an exception:
sqlalchemy.exc.MultipleResultsFound: Multiple rows were found when exactly one was required
from the line:
hepdata/hepdata/ext/opensearch/document_enhancers.py
Line 153 in 21ed044
I just changed this line in commit 319ff15 to make it tolerate multiple results. However, it should be investigated in more detail why there are multiple
DataSubmission
objects with the samedoi
. I found 6 examples:10.17182/hepdata.78551.v1/t3
appears twice)10.17182/hepdata.77606.v1/t54
appears twice)10.17182/hepdata.78402.v1/t29
appears twice)10.17182/hepdata.80608.v1/t14
appears twice)10.17182/hepdata.77761.v1/t3
appears twice)10.17182/hepdata.76842.v1/t3
appears twice)These all date from the early days of
hepdata.net
in 2017/2018 when the submission code was buggy and the procedure for replacing uploads was not done cleanly. It should be investigated how to clean up the database to remove the duplicate DOIs.The text was updated successfully, but these errors were encountered: