A user can save query results. A user can define and share "lists" of data with other users.

Users will be able to create data collections. Depending on the query outcome, the data collection could be created in the data management system, or a list of data products or collections would need to be stored. Each data collection will be connected to (owned by) a group in the AAI system. Both the group ID and the identifier of a data collection (mapped to one, or multiple DIDs in Rucio) are string values. This functionality is intended to be focused at the administration of a group of researchers working together on a set of data products, and will not make any changes to the underlying data system, of which the metadata is the single source of truth.

When a user is logged in, they will want to see what groups they are a member of (there is already a placeholder for this in the view), and what data that is assigned to the group when selecting a group.

Currently there is an API for user preferences, which has a database backend and could be an appropriate place for this functionality.

We will for now assume that if a user can find a data product, they will be able to store the query result (but for the initial phases of the projects, we assume that the data products are all public). Data products that a user can see can be added to the group, irrespective of the data access rights of the other members (but again, given the products are supposed to be public, this is not currently an issue). This will have to be refined later when use cases for private data have been well-defined.

At a fundamental level, any activity by a user will be undertaken as part of an SRCnet project, which will have an allocation of resources and an understanding of data access to members of a group associated with that project. It will be valuable for users to have a concept of a project and that project's associated artefacts (e.g. data products in a project-specific data collection and software products / workflows, and ultimately, project accounting (resources available / used). This concept needs to be shared across members of the project and persistent so that a user can jump into a gateway and pick up where they left off / share with collaborators. Whilst this is not a requirement for SRCNet0.1, it may be possible to begin exploration of scalable solutions for the project concept with some prototyping to help inform future designs.