Patch resets status
Opened this issue · 5 comments
Using the edit/patch functionality results in item status being reset to 'submitted'.
This was unexpected, and inconvenient.
I also tried to do selective reset of status values by patching the RegisterItem, but haven't figured out what the payload should look like.
(i) is CSV column heading 'reg:status' or '@status' ?
(ii) should the payload contain a row for both the entity and the register item ? Or is just the register item enough ?
(iii) Is the rdf:type of the register item 'reg:RegisterItem' ?
I've tried various combos, but an consistently getting error 'Missing entity'.
This seems like a discussion rather than a single issue and so would be better on the forum.
Agree that an existing entry should not have status reset. You could raise that as a separate issue (though no chance of me working on it in the foreseeable future).
(i) The CSV column is @status (download with metadata to see an example).
(ii) Should be just an entity with @id and optionally @Notation and @status (though sounds like it's not as optional as I thought). This is not a tool for management of the RegisiterItems. There's already ways to do that including the API for setting status. This (the CSV representation) was designed for users who just want to access, add or update the entities in a register.
(iii) Neither, the CSV is about the entity.
OK - perhaps I could have moved the second para to the forum, but the issue is real (and I would argue is a bug.) Do we really need a new Issue?
No fine, leave as is
I tried including @status column in a patch payload, but its value doesn't stick.
I seem to recall there being tests for @status so this is a bug rather than an omission. In which case whoever investigates this will need details of your set up and the specific test payload.