1026 allow subcategories for inst names

[juzen2003]

• Fixes #1026
• Were any Django, import pipeline, or table_schema files modified? Y
  • If YES:
  • Database used: re-import
  • All Django tests pass: Y
  • FLAKE8 run on modified code: Y
• Were any JavaScript or CSS files modified? Y (CSS)
  • If YES:
  • JSHINT run on all affected files: NA
  • Tested on Chrome, Firefox, Safari, Edge, and iOS: NA (Remember to test all browser sizes)
  • Tested for race conditions (with delayed API calls if applicable): NA
• Was the documentation reviewed for necessary changes or additions? NA
  • About
  • Getting Started
  • FAQ
  • API Guide
  • Tooltips

Description of changes:

• Group ground based instruments into a subcategory ""Ground-based" in instrument widget.
• Add "Ground-based" to the mult_options of instrument_id field in obs_general.json.
• Update the logic to handle Django form when there is a mix of grouping and non-grouping checkboxes.

[juzen2003]

Progress of cleaning up the code related to mult table

• Changes:
  • Remove the usage of mult_target_name_template.json
  • Remove MULT_TABLES_WITH_TARGET_GROUPING
  • Add grouping & grouping_disp_order columns to all mult tables
    • Update all mult_options in .json files
    • We can set disp_order and group_disp_order in mult_options
  • Remove grouping_target_name table
  • Remove ZZGroupingTargetName in search/models.py
  • Remove GroupingTargetName in metadata/models.py
  • For mult tables with preprogrammed options:
    • add grouping column to store the group names
    • add group_disp_order column to store the group order
  • For mult from field_* functions:
    • We return either a string or a dictionary with this structure:

      {
          'col_val': value for the mult option, 
          'disp_name': display name on the UI,
          'disp_order': display order of this option within the same group, could be None
          'grouping': group name associated with this value, could be None
          'group_disp_order': display order of this group, could be None
      }

    • if disp_order or group_disp_order is not specify, they will be ordered alphabetically
  • Update the following mult field functions:
    • In obs_general.py
      • field_obs_general_target_name
      • field_obs_general_target_class
    • In obs_instrument_ebrocc.py:
      • field_obs_general_target_name
      • field_obs_profile_quality_score
      • field_obs_profile_source
      • field_obs_profile_host

NOTE:

• For now only the ebrocc is updated, please import just the ebrocc volume. Errors will be raised if other instrument is imported. Possible issue:
• For non-preprogrammed mult, if we want to specify display order or group display order, we have to know all the possible options. For now, we use TARGET_NAME_GROUP_MAPPING in config_targets.py to specify the order and display name of different groups for non-preprogrammed mult. Previously we store the info in the db. Do we want to keep this info in db (then it will be like the old grouping_target_name table existing for display order only)? Or should we keep all the customized grouping info in another file?

[juzen2003]

• Update the field_.* functions with GROUP/TARGETS form type to call _create_mult
• Update mult_options in these table schemas:
  • obs_general.json
  • obs_instrument_cocirs.json
  • obs_instrument_coiss.json
  • obs_instrument_couvis.json
  • obs_instrument_covims.json
  • obs_instrument_gossi.json
  • obs_instrument_nhlorri.json
  • obs_instrument_nhmvic.json
  • obs_instrument_vgiss.json
  • obs_mission_cassini.json
  • obs_mission_galileo.json
  • obs_mission_hubble.json
  • obs_profile.json
  • obs_wavelength.json
  • obs_type_image.json

[juzen2003]

Updated based on above comments

[juzen2003]

Updated based on the latest comments.

[juzen2003]

• Group HST filter by instrument names.
• Group HST aperture type by instrument names.
• Group part of OCC receiver host by DSNs and Ground-based Telescopes.
• Group part of OCC signal source by Stars