APT Standard Target Name Agenda: History of APT Standard Target Name PR DMS Level 3 Data File Names SANTA: MAST Name Resolver Pros/Cons of adding Standard Target Name to APT -> DMS Approaches to add Standard Target Name to APT Decisions on moving forward & schedule/deadlines

History of APT Standard Target Name 2008: Discussion started; APT PR #61413 Goal: To help the GO easily select a "Standard Target Name" for each of their targets that will aid in the maintenance and searchability of the JWST Archive. 2013: Discussed adding MAST Name Resolver (SANTA) to get a Standard Target Name 2013: Concept was mostly rejected by the WIT (Bill B.) and MESA (Diane) Confusing for the user/proposer 2013: Standard Target Name Requirement downgraded to optional resolvable target name (but not implemented) 2015: DMS resurrects this PR due to Level 3 Science Product File Name dependency on the Standard Target Name

DMS Level 3 Science Data File Names Imaging Associations Design Document (SOCCER) The format for the L3 file name will be: jw _ _ _ _.fits is the program identifier; is the standard target name, which may contain an epoch; is nircam, nirspec, miri, niriss, or fgs; is the optical element or optical element combination used; and indicates the type of data product, image for imaging associations Underscores are used to separate fields within the file name. Dashes are used to separate values within fields. Non-alphanumeric characters should be removed from target names for the data product file name, but kept in the target name keyword values. Except the characters ‘+’, ‘-‘, and’.’ are kept in file names. Example DMS L3 product file names: A science data product file name for target “W51A+G ” would be: jw93060_w51a+g _miri_f1500w_image.fits jw65101_egs-01_nircam_f356w_image.fits (long wavelength) jw84140_ngc55_nircam_f090w_image.fits (short wavelength) An example science data product name with crossed filters would be: jw97011_2mass _nircam_f405n-f410m_image.fits

APT Standard Target Name DMS Workflow Target InfoAPTDMS FITS Header Keyword Usable DMS L3 File Name? Proposer’s Target Name TargetTARGPROPNO (input can be freeform) Standard Astronomical Target Name N/A “” TARGNAMEYES (standard astro name in most cases) Interim solution in DMS -> copy TARGPROP into TARGNAME header keywords, then clean up with unix-friendly conversion to use as L3 file names.

SODRM TARGPROP Summary

Pros/Cons of adding Standard Target Name to APT --> DMS ProsCons Observer/Proposer’s intent it preservedCan be confusing to the user; more work upfront by proposer Forces object/source spelling to a standard format Can be limiting when no standard source name is available DMS L3 file names can be auto generated (for the most part) Names have to be edited to be unix- friendly (all cases); coordinates are not science-friendly Improves Archive names searches, tagging data in the archive, publications Archive name-based searches are not as accurate Archive long-term data preservation (NASA mandate) Data are not as complete as they can be Needs of the many outweigh the needs of the few (archive vs proposer) It’s more work to get this into the system

Pros/Cons of NOT adding Standard Target Name to APT --> DMS ProsCons Less confusion, fewer tasks for the proposer Proposer intent is/may not be preserved Less work for APT developersDMS has increased complexity with automation of file names; may need human decisions in the pipeline

MAST Name Resolver (SANTA) SANTA name resolver has a local cache to reduce network bandwidth and minimize outages SANTA search order: “COORDINATES” (just normalizes coordinates) “NED” “SIMBADCFA” “SIMBAD” “KEPLER” (searches Kepler IDs) DADS (searches HST program and dataset names) (The order is subject to change based on the status of the external resolvers.) Suggested SANTA update for APT Standard Target name: Search with coordinates and return candidate objects and some associated meta data with a specified radius. This would include the current name return, the object classification within the aggregator and the angular separation between the submitted coordinates and the coordinates in SIMBAD/NED.

Use SANTA to get the Standard Target Name Using the SANTA API, APT could implement something like the following: Add a second target field regarding the "Standard Astronomical Target Name" This will call SANTA with the user input User can type in coordinates or name SANTA will return a list of suggestions The user will need to choose one of the following three options in order of preference: SANTA name/NAIF ID else, project acronym name is allowed to be used (user input) else coordinates can be used as last resort (HMSDMS or 9 digit format TBD)

Approaches to add Standard Target Name to APT Karla

Decisions on moving forward & schedule/deadlines Brief Notes: WebEx streaming recording link: 92a46eccadc0 APT Group will discuss options/scope/timeframe for basic implementation Karen’s group will discuss requirements/scope/timeframe for SANTA upgrade Meet in 2-3 weeks to go over the above before presenting this to Tom Brown for a decision on how to move forward.