[OBSPROC-35] add ob_code column to the target table in the targetdb Created: 04/Dec/22 Updated: 07/Dec/22 Resolved: 07/Dec/22 |
|
| Status: | Done |
| 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: | Done | Votes: | 0 |
| Labels: | targetDB | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Epic Link: | targetDB |
| Reviewers: | monodera |
| Description |
|
eric requested to add a column, ob_code, to indicate an unique target in a proposal to target table in the targetdb. It is useful to identify entries corresponding to a pair of (obj_id, input_catalog_id) recorded in pfsDesign/pfsConfig files and opdb.
Requirements for ob_code is the following.
I think it is reasonable and won't make any side-effects, so will implement before the December 2022 commissioning run. |