You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the ContainerHistory table to store the different container locations on site.
The last entry in ContainerHistory attached to a containerId will contain the last known location of the container.
Initial value set to dewarLocation.
Add methods in services and WS :
to update the containerLocation,
to create containerHistory entries,
to retrieve the history of a container
Open questions:
Create the first ContainerHistory when the dewar arrives on site (for example status "at ESRF" and location "STORES-IN") ?
Shall the container location be updated and a ContainerHistory entry added each time the dewar location is updated ?
The text was updated successfully, but these errors were encountered:
ContainerHistory EJBs and services created.
Rest WS to view the list of containerHistory attached to a container
Rest WS to update the location of a container and create a new containerHistory.
When updating a dewar location, a boolean is added to update also or not the containers attached to the dewar.
TODO:
Discuss the uses cases to refine the WS and define the web app and BCR interfaces
Use the ContainerHistory table to store the different container locations on site.
The last entry in ContainerHistory attached to a containerId will contain the last known location of the container.
Initial value set to dewarLocation.
Add methods in services and WS :
Open questions:
The text was updated successfully, but these errors were encountered: