we may need to modify the vizdb tables for legacy reductions

For legacy reductions that have sdss_ids, we will want to know which release they were a part of. This could be a a latest release in which the final public data was produced, e.g. for manga DR17, or it could be a minimum release of the first release, e.g. DR13 for manga. We need to modify the vizdb.releases table.

We could also modify the vizdb.sdssid_to_pipes table to have multiple rows for each sdssid for every release it is in.

We might need to do this for LVM since they will have a different MJD cutoff compared to MOS observations.

Some MJD cutoff info for prior data releases, by survey.

boss ; apogee ; manga
dr17: 59029 ; [59236](https://data.sdss.org/sas/dr17/apogee/spectro/redux/dr17/exposures/apogee-s/59236/html/59236exp.html) ; [59085](https://data.sdss.org/sas/dr17/manga/spectro/redux/v3_1_1/11950/59085)
dr16: 58546 ; [58358](https://data.sdss.org/sas/dr16/apogee/spectro/redux/r12/exposures/apogee-s/58358/html/58358exp.html) ; [57944](https://data.sdss.org/sas/dr16/manga/spectro/redux/v2_4_3/9298/57944)
dr15: 57520 ; [57583](https://data.sdss.org/sas/dr15/apogee/spectro/redux/r8/red/57583/html/57583exp.html) ; [57944](https://data.sdss.org/sas/dr15/manga/spectro/redux/v2_4_3/9298/57944)
dr14: 57520 ; [57583](https://data.sdss.org/sas/dr14/apogee/spectro/redux/r8/red/57583/html/57583exp.html) ; [57580](https://data.sdss.org/sas/dr14/manga/spectro/redux/v2_1_2/7964/57580)
dr13: 57166 ; [56856](https://data.sdss.org/sas/dr13/apogee/spectro/redux/r6/red/56856/html/56856exp.html) ;[57199](https://data.sdss.org/sas/dr13/manga/spectro/redux/v1_5_4/8618/57199)
dr12: 56837 (5_7_2) 56755(5_7_0) ; [56855](https://data.sdss.org/sas/dr12/apogee/spectro/redux/r5/red/56855/html/56855exp.html)
dr11: 56432 ; [56629](https://data.sdss.org/sas/dr11/apogee/spectro/redux/r4/red/56629/html/56629exp.html)
dr10: 56107 ; [56121](https://data.sdss.org/sas/dr10/apogee/spectro/redux/r3/red/56121/html/56121exp.html)
dr9: 55752

This is a manga target (not observed in drpall), but has a boss specobjid . To get observed manga galaxies need to join with manga_drpall table.

  {
    "sdss_id": 69735520,
    "ra_sdss_id": 0.8838815388194464,
    "dec_sdss_id": -10.744689965218045,
    "catalogid": 63050395064754020,
    "version_id": 31,
    "n_associated": 1,
    "ra_catalogid": 0.8838815388194464,
    "dec_catalogid": -10.744689965218045,
    "rank": 1,
    "version": 31,
    "lead": "gaia_dr3_source",
    "ra": 0.8838815388194464,
    "dec": -10.744689965218045,
    "parent_catalogs": {
      "allwise": 15010701351036192,
      "gaia_dr2_source": 2422574280380383700,
      "gaia_dr3_source": 2422574280380383700,
      "guvcat": 6380415564945295000,
      "legacy_survey_dr10": 43981592443491310,
      "legacy_survey_dr8": 8796110636781511,
      "mangatarget": "1-100177",
      "panstarrs1": 402739083384879,
      "sdss_dr13_photoobj": 1237652629098987500,
      "sdss_dr17_specobj": "731837999058282496",
      "tic_v8": 176281280,
      "twomass_psc": 197395756
    }
  }

Start by inspecting the schemas for vizdb.releases and vizdb.sdssid_to_pipes, then use the manga_drpall join and listed MJD cutoffs to clarify release membership. Done means an agreed schema and data model for legacy reductions across releases, including survey-specific cutoffs, with the example observed-galaxy lookup still working.