Difference between revisions of "Telecon (2019-08-07)"

From Earth Science Information Partners (ESIP)
Line 4: Line 4:
  
 
===Agenda===
 
===Agenda===
TBD
+
'''Refine IMCR scope''' - Uncertainty about project scope largely stems from an inability to prioritize use cases.
 +
* Who are the primary constituents we are trying to serve and what are their use cases?
 +
* Who are ancillary constituents and what do they need?
 +
* Prioritize this list, constrain scope to the current priority, and add future scope to a project road map.
 +
* What science domain(s) are we serving?
 +
* What level of software maturity does the IMCR contain?
 +
* What do the registered software items represent (e.g. single scripts, packages, both)?
 +
* Explicitly communicate this in a project scope.
 +
 
 +
'''Improve software metadata so IMCR is useful to platforms like the [http://datadiscoverystudio.org/geoportal/#searchPanel Data Discovery Studio]'''
 +
* What level of detail needs to be added?
 +
* How can we perform this task?
 +
* How much effort will it require?
 +
* What priority does this task have?
 +
 
 +
'''Reconsider controlled vocabulary structure and terms''' - The current controlled vocabulary is a customized construct designed to serve the non-expert data manager to the detriment of excluding others. Aligning the IMCR vocabulary with established vocabularies (e.g. SWEET, GCMD) would enable machine actionability and inclusion in platforms like the Data Discovery Studio.
 +
* Do we want to continue with the custom vocabulary or align with established vocabularies (can we do both)? - An answer to this depends on our discussion of scope above.
 +
 
 +
'''Scraping and sorting the web for IM software''' - This is being done by others, whom we can collaborate with.
 +
* Where does this fit into project priorities?
 +
* How much effort will this require? - This will likely require a fact finding expedition. Who will lead it?
  
 
===Discussion===
 
===Discussion===
  
 
===Action items===
 
===Action items===

Revision as of 10:50, August 2, 2019

Return to Archive

Attendees

Agenda

Refine IMCR scope - Uncertainty about project scope largely stems from an inability to prioritize use cases.

  • Who are the primary constituents we are trying to serve and what are their use cases?
  • Who are ancillary constituents and what do they need?
  • Prioritize this list, constrain scope to the current priority, and add future scope to a project road map.
  • What science domain(s) are we serving?
  • What level of software maturity does the IMCR contain?
  • What do the registered software items represent (e.g. single scripts, packages, both)?
  • Explicitly communicate this in a project scope.

Improve software metadata so IMCR is useful to platforms like the Data Discovery Studio

  • What level of detail needs to be added?
  • How can we perform this task?
  • How much effort will it require?
  • What priority does this task have?

Reconsider controlled vocabulary structure and terms - The current controlled vocabulary is a customized construct designed to serve the non-expert data manager to the detriment of excluding others. Aligning the IMCR vocabulary with established vocabularies (e.g. SWEET, GCMD) would enable machine actionability and inclusion in platforms like the Data Discovery Studio.

  • Do we want to continue with the custom vocabulary or align with established vocabularies (can we do both)? - An answer to this depends on our discussion of scope above.

Scraping and sorting the web for IM software - This is being done by others, whom we can collaborate with.

  • Where does this fit into project priorities?
  • How much effort will this require? - This will likely require a fact finding expedition. Who will lead it?

Discussion

Action items