Difference between revisions of "2022-02-17Wintermeetingrecapandplanning"

From Earth Science Information Partners (ESIP)
Line 26: Line 26:
 
* information sharing and learning together.
 
* information sharing and learning together.
 
* analytics, content, ML, and UI.
 
* analytics, content, ML, and UI.
 +
Breakout Session Takeaway; Social asymmetries in usage based discovery:
 +
 +
* Group 7, UBD Data Architecture: Discipline boundaries are a source of fragmentation.  Investments in a discipline may not extend across the Earth Sciences.  UBD Cluster should address fundamental interoperability and governance issues, and build this in anticipation of disparate investments.
 +
* Group 1, Messaging UBD: identified an audience for UBD data and tools: early career scientists and interdisciplinary researchers.  UBD use case, where people need to get up to speed on dataset use within a discipline on a relatively compressed timeline.
 +
* Group 6, Machine Learning: Coolridge Initiative involved just three agencies: USDA/ERD, NSF/Economics Division, and NOAA.  NASA would like to get involved.  Need to test algorithms for use in Earth Science disciplines - concerns on whether the code can be generalized to other agencies publications and datasets.
 +
* Group 5, Topics and findings: Engineering the relevance ranking of search results; careful that UBD doesn't reinforce dataset popularity, because this group had an interest in leveling the playing field among different datasets.  Envisioned success criteria where UBD helps users identify the most useful dataset.
 +
 +
Discussion:
 +
 +
Vinny Inverso: NASA Heliophysics Division interested in UBD.  How do we connect knowledge graphs.
 +
 +
Megan Carter: ESIP Knowledge Graph Cluster: Wednesday at 4PM.
 +
 +
Jonathan Blythe: Knowledge Graph is different enough from UBD that this wouldn't be duplicative, though we want to stay informed on the emerging cluster's progress.

Revision as of 07:52, February 18, 2022

Usage Based Discovery Cluster February 2022 Meeting

February 17, 2022

Agenda:

  1. Recap winter meeting and takeaways
  2. Plan next for next six months of activity on the Discovery Cluster

People who attended:

  • Simon Goring
  • Douglas Rao
  • Lindsay Barbieri
  • Chris Lynnes
  • Tyler Christensen
  • Vinny Inverso
  • Jonathan Blythe
  • Megan Carter

Notes:

Opportunities to Work Together on usage based discovery?

Cross-Agency goal

Objectives:

  • messaging usage based discovery.
  • information sharing and learning together.
  • analytics, content, ML, and UI.

Breakout Session Takeaway; Social asymmetries in usage based discovery:

  • Group 7, UBD Data Architecture: Discipline boundaries are a source of fragmentation. Investments in a discipline may not extend across the Earth Sciences. UBD Cluster should address fundamental interoperability and governance issues, and build this in anticipation of disparate investments.
  • Group 1, Messaging UBD: identified an audience for UBD data and tools: early career scientists and interdisciplinary researchers. UBD use case, where people need to get up to speed on dataset use within a discipline on a relatively compressed timeline.
  • Group 6, Machine Learning: Coolridge Initiative involved just three agencies: USDA/ERD, NSF/Economics Division, and NOAA. NASA would like to get involved. Need to test algorithms for use in Earth Science disciplines - concerns on whether the code can be generalized to other agencies publications and datasets.
  • Group 5, Topics and findings: Engineering the relevance ranking of search results; careful that UBD doesn't reinforce dataset popularity, because this group had an interest in leveling the playing field among different datasets. Envisioned success criteria where UBD helps users identify the most useful dataset.

Discussion:

Vinny Inverso: NASA Heliophysics Division interested in UBD. How do we connect knowledge graphs.

Megan Carter: ESIP Knowledge Graph Cluster: Wednesday at 4PM.

Jonathan Blythe: Knowledge Graph is different enough from UBD that this wouldn't be duplicative, though we want to stay informed on the emerging cluster's progress.