Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Container tracking on site #452

Open
delageniere opened this issue Oct 31, 2019 · 1 comment
Open

Container tracking on site #452

delageniere opened this issue Oct 31, 2019 · 1 comment
Assignees

Comments

@delageniere
Copy link
Collaborator

delageniere commented Oct 31, 2019

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 ?
@delageniere delageniere self-assigned this Oct 31, 2019
@delageniere
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant