duplication_handling.pdf
|
Relates |
|||
| relates to |
|
Define the schema of prototype of tar... | Won't Fix |
[OBSPROC-18] Handling duplicates in targetDB Created: 17/Feb/22 Updated: 22/Sep/23 Resolved: 22/Sep/23 |
|
| Status: | Won't Fix |
| Project: | PFS observation processing/procedure |
| Component/s: | ets_target_database |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Normal |
| Reporter: | monodera | Assignee: | monodera |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | targetDB | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
duplication_handling.pdf
|
||||||||
| Issue Links: |
|
||||||||
| Epic Link: | targetDB | ||||||||
| Description |
|
We need to handle duplicated targets from different programs. I'm still wondering what is the easiest and efficient implementation. |
| Comments |
| Comment by monodera [ 07/Apr/22 ] |
|
The current idea is summarized in duplication_handling.pdf |
| Comment by monodera [ 22/Sep/23 ] |
|
After discussing with Eric-san and others, I decided not to check duplicates in the target database. |
