Default file container for collection
Feature Request
🥅 Goal
As a shepard frontend user
I want to have a default file container for my collection
so that I can directly upload files in date objects of the collection without having to bother with the creation of containers
🏅 Acceptance Criteria
-
The collection knows its default file container if it has any.
- there is one default file container that can be stored for a collection . it can be any file container.
- the container does not need to know the collection it is assigned to. it could be the default file container for multiple connection.
-
there is an operation available that allows the user to assign a container as default file container
- the user needs read write on the file container and write right on the collection to do that
-
Create an ADR to decide how the additional information that links collection and its default file container shall be stored in Neo4j
- in the ADR it shall be considered that in the future the system shall be extended with templates for collections and data objects, that the collections and data objects want to retain a connection to the template they were created from. if possible, the architecture pattern used for the default file container should also enable templates.
⭐ Special Testing hints
💣 Out of Scope
- on creation of a collection the users should be asked whether they want to add a new default file container with the same permissions as the collection --> that could be a follow-up easily
💡 Hints
🤔 Risks & Open Questions
- should the permissions be inherited once at creation time or be referenced?
Edited by wiglef