### Overview This issue contains a list of (supposed) bugs which should be fixed before the release of ArunaServer version 1.0.0. ### Task list 1. - [x] Implement check for object reference creation in collections which are already pinned to a version. 2. - [x] Use existing versions from table `collection_versions` instead of creating a new entry on collection update/pin 3. - [x] Staging object update should not delete internally used labels 4. - [x] Adapt path validation regex to prohibit empty path parts 5. - [x] Extend object reference creation with the possibility to provide custom sub path 6. - [x] Deletion of all ObjectGroup revisions with single request 7. - [x] Collection pin clones active paths and replaces relevant path part with provided version 8. - [x] Delete all paths of collection with last object reference 9. - [x] Restrict project and collection names to valid [RFC3986 unreserved characters](https://www.rfc-editor.org/rfc/rfc3986#section-2.3) for path compliance 10. - [x] Fix broken access management of `get_object_by_id` function 11. - [x] Prevent reference creation for staging objects 12. - [x] Object reference with `auto_update == true` can only be created for latest object revision 13. - [x] Prevent ObjectGroup creation/update with staging objects 14. - [x] Clone existing location(s) on object clone 15. - [x] Check if path exists before creation 16. - [x] Check if object exists in collection provided by `GetReferencesRequest` ### Discussions * This thread is specifically to discuss all above tasks / proclaimed changes / intended fixes.
Overview
This issue contains a list of (supposed) bugs which should be fixed before the release of ArunaServer version 1.0.0.
Task list
collection_versionsinstead of creating a new entry on collection update/pinget_object_by_idfunctionauto_update == truecan only be created for latest object revisionGetReferencesRequestDiscussions