decide between 1-to-n or n-to-n relationship user=>shopping items
Originally the ShoppingBasket mechanism was (partly) implemented (by Hugh Dickingson) as a many-to-many relationship with a userprofile.
Expanding this to a fuller implementation (by me, Nico) where the user could also remove items, lead to dangling items in the shopping basket after all users had removed the shared items.
To overcome this problem, I implemented an alternative where the relationship between users and their shoppingbasket items is 1-to-many.
This alternative lives on a branch, but we need to decide (asap) if we will use this implementation or if somebody (Hugh?) solves that problem in the many-to-many implementation. https://git.astron.nl/astron-sdc/esap-api-gateway/-/tree/esap-gateway-shoppingbasket2
Hugh noted that the many-to-many solution needs to stay in place for the ComputeResources and SoftwareRepository sections. But those sections have also been (partly) implemented in the ida app by Stelios, and depending on how the decision to move forward with that these sections in the accounts app may or may not disappear.