Shipping configuration
This issue is part of the following use case:
3.1.1. As a user I want to send samples to the beamline.
a) Create a shipment
Problems
So far we have a page that lists the shipments associated to the investigations a user has access to. This CRUD interfaces are problematic for the following reasons:
1) Shipments are abstractions users don't need to know about.
- Users send parcels, not shipments, so the term "shipment" is sure to be confusing for them.
- One investigation = one shipment, so for users the step of creating a shipment actually amounts to configuring shipping for a given investigation. Listing all the shipments associated to investigations a user has access to provides very little value.
2) Managing addresses on an independent page breaks the user's flow.
If they don't know or forget how the system works, they'll go to configure shipping for an investigation first, then they'll realise they have to leave the page to create the addresses first, and then they'll have to find their way back to the investigation's shipping configuration page.
While a separate page is still useful, users should be able to create new addresses seamlessly while configuring shipping or adding parcels.
Solution
-
Remove the "Shipments" page. -
On investigation page, add tab "Shipping" with the following route: /investigation/:investigationId/shipping
-
The "Shipping" tab contains a form to select the default sender and/or return addresses and add an optional comment. -
The shipment is created in the back-end when the user submits the form. -
When the user comes back to the page after submitting, they see the same form pre-filled with the shipment's details. -
The user can select an address from their address book, which includes the addresses associated to every investigation the user has access to). -
The form allows entering new addresses, which are then created on submit- moved to #331 (closed)
-
Edited by Axel Bocciarelli