Details
-
Story
-
Resolution: Done
-
High
-
None
-
None
-
None
-
[2.5] - Sprint 2
Description
This is required in order to know where we are going with a content object without a published version.
Outcome:
- reusing the existing status 'archived' in the kernel
- being able to change the status of a content object (Admin UI, command line or database) (version and object level)
- list interfaces where the system throws an error because of this new status
- verify the impact on the APIs used on the frontend. Are items with this status returned ? Are they meant to ?
Attachments
Issue Links
- links to