HAPI Developer’s Working Meeting, January 27 to 29, 2025

Outcomes / next steps:

• some proposal ideas generated - next is check with Program Officer(s)
• nearly done with 3.3 release; still left:
  • test 3.3 schemas (and split) and integrate into verifier (Bob and Jeremy)
  • test servers for 3.3 features (Bob and Jeremy)
  • finalizing the CI/CD steps (Jon): make PDF, add to Zenodo, update web pages (Jon)
• slides for Jesper for SuperMAG at ISWAT
• keep pushing on SuperMAG install

Things not covered that still need doing:

• can HAPI serve digitalRF? (see GitHub for digitalRF)
• aliveness testing and notifications
• collection of all HAPI metadata
• semantic overlays of HAPI data
• who's going to which meetings?

Homework:

• Read ticket about error message for time requests outside of advertised startDate and stopDate: https://github.com/hapi-server/data-specification/issues/97
• Read NSF proposal opportunity: https://new.nsf.gov/funding/opportunities/fairos-findable-accessible-interoperable-reusable-open-science/nsf25-533/solicitation

Agenda

Monday Morning:

• finalize agenda for week
• roadmap to releasing HAPI 3.3
  • identify crucial issues to resolve
  • decide when to do CI/CD improvements
  • start working crucial issues to get most of them done
  • key one is adding location and geoLocation to dataset-level in info response; have PR ready by noon for review at HAPI telecon
• list out cleanup tasks:
  • small: divide up telecon notes doc by year

Monday Noon: HAPI telecon

Monday Afternoon: Continue working on crucial issues for 3.3

Tuesday: select set of harder, over-arching issues

• linkages
  • load all linkage-related issues into our heads
  • create envisioned use-cases, focusing on capabilities we know people want or that we want to push into
  • discuss ways to capture the use cases and meet all the constraints: keep HAPI simple, don't break backwards compatibility, allow HAPI to offer semantically recognizable entities
• semantic representations of content (file listings, image lists, availability, good time intervals)
  • active semantics (you must represent it this way)N versus passive (describe your heterogenous content so it can be properly interpreted)
• uploading of data to HAPI servers
• automated FAIR assessment and other newer data center standards
• Aliveness testing (Jeremy added)

Wednesday: collaborations and proposals - 10am Eastern if you want to join for this topic

• List future ideas / opportunities for HAPI proposals:
  • HAPI for Zenodo
  • FAIROS opportunity for NSF (not just GEO, but GEO proposals are requested to have a specific focus)
  • working with HDRL for 2026 and beyond
  • anything with NOAA?
• Collaborations:
  • PyHC
  • IVOA and astronomy community
  • Madrigal
  • SuperDARN
  • HAmSCI - need to verify DigitalRF can be represented by HAPI Server
  • continuing strengthening ties with ESA
  • how best to work with Canadian groups
    • Space Environment Canada - riometers and ionosondes
  • engaging Japanese project
• Upcoming meetings:
  • ISWAT: Canaveral, Feb 10-14
  • HamSCI: NJIT, March 14-15
  • Space Weather Workshop: Boulder, March 17-21; abstracts due Feb 17
  • EGU: Online (Vienna), Apr 27-May 2
  • CEDAR: Des Moines, June 22-27
  • GEM: Des Moines, June 22-27
  • Planetary Data Workshop: Cornell, maybe happening in 3rd week of June
  • Helio Software Stds Workshop (less relevant, but we will be there anyway)
  • NASA's Data Repositories Workshop (not sure if happening and dates)
  • Any NSF / GEO data commons / workshop meetings?
  • DASH 2025: San Antonio, Oct 19-24
  • ADASS 2025: Goerlitz, Germany, Nov 9-13
  • AGU: New Orleans, Dec 15-19
  • 2026: SMD-wide software workshop (not set yet - possibly at APL?)

Wednesday Meeting Closeout

• punch list of items for 3.3 release
• action items with people and dates