AllenNeuralDynamics / AllenNeuralDynamics/aind-metadata-service
Merge duplicate procedures
- Lingua principale
- Python
- Stelle
- 3
- Fork
- 1
- Merge medio
- 17h 3m
- PR unite (30g)
- 15
Descrizione
# User story
There are sometimes the same surgery documented in different data sources, with different information. For example, LAS tracks very basic RO Injection info in Labtracks and more info can be found in Smartsheet (for exaspim). The current implementation of the procedures endpoint returns a list of procedures and returns the info as 2 injections despite referring to the same surgery. As a user, I want this info to be merged to not confuse other users.
# Acceptance criteria
- [ ] Given 2 procedures' start_date and procedure type are the same, merge the 2 to create the most complete surgery.
# Sprint Ready Checklist
- [ ] 1. Acceptance criteria defined
- [ ] 2. Team understands acceptance criteria
- [ ] 3. Team has defined solution / steps to satisfy acceptance criteria
- [ ] 4. Acceptance criteria is verifiable / testable
- [ ] 5. External / 3rd Party dependencies identified
- [ ] 6. Ticket is prioritized and sized
# Notes
Related to the exaspim procedures ticket. We've considered this in the past but decided against it, but verified this assumption with @dbirman. The current acceptance criteria is generic to handle cases of duplicate info from any combination of sources, but make sure to test in dev thoroughly
Guida per i contributori
Nessuna guida per i contributori indicizzata per questo repository
Valutazione
Questa issue non è ancora stata valutata.