bug #10172
closedRegistration not found in phycobank portal though it exists
100%
Description
e.g. http://phycobank.org/100097
I guess also https://phycobank.org/100172 and https://www.phycobank.org/cdm_dataportal/registration?identifier=http%3A//phycobank.org/100147 / http://phycobank.org/100147 => no these are different cases
are such issues.
Same problem exists on test: https://test.e-taxonomy.eu/dataportal/preview/phycobank/cdm_dataportal/registration?identifier=http%3A//phycobank.org/100097 with webservice https://test.e-taxonomy.eu/cdmserver/phycobank/registrationDTO.json?identifier=http://phycobank.org/100097
Updated by Andreas Müller over 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 60
The problem is that for http://phycobank.org/100097 exist 2 registrations with status "published". This is not allowed. However the wrong status message is sent back, probably because response.sendError is called 2x.
This has been changed. However, the main problem are the data.
We could also try to improve the message handling in this case.
Updated by Andreas Müller over 1 year ago
SELECT r.identifier FROM Registration r GROUP BY r.identifier HAVING COUNT(*) > 1
Updated by Andreas Müller over 1 year ago
- Status changed from In Progress to Resolved
- Assignee changed from Andreas Müller to Wolf-Henning Kusber
- Priority changed from New to Highest
- % Done changed from 60 to 70
Sent mail to WHK to clean the data itself. I guess we can close this ticket if we do not want to improve the error handling in the dataportal also. But I guess this is not so important, the resulting webservices do give more information now so the error can be easily debugged if it occurs again.
Updated by Andreas Müller over 1 year ago
Also check that specific identifier and identifier match
SELECT r.* FROM Registration r WHERE r.identifier <> CONCAT ('http://phycobank.org/', r.specificIdentifier);
Updated by Andreas Müller over 1 year ago
- Target version changed from Release 5.35 to Release 5.34
Updated by Andreas Müller over 1 year ago
- Status changed from Resolved to Closed
- % Done changed from 70 to 100
The data is also cleaned now so I guess we can close this ticket.