Purging record produces a 400 bad request message

Project:RUcore dlr/EDIT
Version:7.7
Component:Code
Category:bug report
Priority:normal
Assigned:triggs
Status:closed
Description

The selected object 'rutgers-lib:201752' is an ordinary object...
The user purging this object is 'datacenter'. Updating DOI:

400
bad request - invalid identifier status change

Comments

#1

Version:7.4» 7-x

This seems to be a DOI issue. When an object with a DOI is purged, we try to change the state to unavailable with a reason of "object purged". If there is a problem with the DOI of the object (it might never have made it to a public DOI), an error changing state like this might be generated. Since the object is purged, it may be impossible to tell exactly what was wrong with the DOI. I think we should watch to see if any more of these come up.

#2

Version:7-x» 8.x

Have we seen more of these? I'm moving this to 8.x for now, though it may become a non-issue if the DOIs are all cleaned up.

#3

Status:active» fixed

I just purged an object without any problems.

#4

Fixed.

#5

Version:8.x» 7.7
Status:fixed» closed

Back to top