Telecon (2019-07-03)

From Federation of Earth Science Information Partners
(Difference between revisions)
Jump to: navigation, search
(Analyzing keyword usage in the IMCR)
(Revisiting controlled vocabularies)
 
(5 intermediate revisions by one user not shown)
Line 18: Line 18:
  
 
====Revisiting controlled vocabularies====
 
====Revisiting controlled vocabularies====
'''Science domain'''
+
'''Science domain CV'''
 
* If broadly applicable, then better to include all domains rather than none.
 
* If broadly applicable, then better to include all domains rather than none.
 
* [http://vocab.lternet.edu/vocab/vocab/index.php Consider the LTER Controlled vocabulary "disciplines" category of terms]
 
* [http://vocab.lternet.edu/vocab/vocab/index.php Consider the LTER Controlled vocabulary "disciplines" category of terms]
 
'''IMCR CV'''
 
'''IMCR CV'''
 
* planning
 
* planning
** project management - Too broad. Remove
+
** project management - Remove (too broad), or change to "project planning"
** process management (e.g. Kelper) - Rename as "workflow management"
+
** process management (e.g. Kelper) - Rename as "workflow management". Move to integration.
 
* collection
 
* collection
** egress - Rename as "export", perhaps delete
+
** egress - Rename as "export" or delete.
 
** ingress - Rename as "import"
 
** ingress - Rename as "import"
** streaming data - to data streaming
+
** streaming data - to "data streaming" or "streaming"
** storage > data base design to planning
+
** storage - Rename as "storing", and move to preservation
 +
** data base design - Potentially new term to under planning
 
* assurance
 
* assurance
** cleaning falls under assurance or control
+
** spatial data editing - Remove term
** spatial data editing/spatial transformation - remove "spatial"
+
** spatial transformation - Remove term (already exists under integration where it belongs)
 +
** visualization - Change to "visual assurance"
 
* describing
 
* describing
** mind mapping to planning
+
** mind mapping - Move to planning
** metadata rendering to preservation or to transformation
+
** metadata rendering - Remove term since it falls under transformation
** semantic* sub-terms under semantic operations or annotation
+
** semantic* - Combine into new term "annotation"
 
* preservation
 
* preservation
** notification is esoteric (communication)
+
** Notification is esoteric - Remove
** transformation/formatting  
+
** transformation/formatting may belong under this hierarchy
 
* discovery
 
* discovery
** retrieval and mining under collection
+
** retrieval and mining - Move under collection
** crawling - might be too specific
+
** crawling - Remove (too specific)
 +
** delivery - Move under "integration"
 
* integration
 
* integration
 
** aggregation - add term
 
** aggregation - add term
Line 48: Line 51:
 
** interoperatbility - move to preservation
 
** interoperatbility - move to preservation
 
** conversion and reformatting are very simmilar - reformatting under conversion
 
** conversion and reformatting are very simmilar - reformatting under conversion
**
 
  
 
====ESIP summer meeting plans====
 
====ESIP summer meeting plans====

Latest revision as of 08:57, 4 July 2019

Return to Archive

Contents

[edit] Attendees

  • John Porter
  • Colin Smith
  • Stevan Earl

[edit] Agenda

  • Analyzing keyword usage in the IMCR Extracting metadata from Ontosoft, parsing, and analytical approaches.
  • Revisiting controlled vocabularies Review IMCR terms, identify and integrate science domain into IMCR best practices.
  • ESIP summer meeting plans Review summer meeting presentation and participant activities.

[edit] Discussion

[edit] Analyzing keyword usage in the IMCR

Some cursory ideas for analyzing the IMCR contents, primarily for purposes of the summer ESIP meeting in a few weeks.

  • Perhaps a cluster analysis of keywords
  • Word cloud of term use
  • Histogram of term use

[edit] Revisiting controlled vocabularies

Science domain CV

IMCR CV

  • planning
    • project management - Remove (too broad), or change to "project planning"
    • process management (e.g. Kelper) - Rename as "workflow management". Move to integration.
  • collection
    • egress - Rename as "export" or delete.
    • ingress - Rename as "import"
    • streaming data - to "data streaming" or "streaming"
    • storage - Rename as "storing", and move to preservation
    • data base design - Potentially new term to under planning
  • assurance
    • spatial data editing - Remove term
    • spatial transformation - Remove term (already exists under integration where it belongs)
    • visualization - Change to "visual assurance"
  • describing
    • mind mapping - Move to planning
    • metadata rendering - Remove term since it falls under transformation
    • semantic* - Combine into new term "annotation"
  • preservation
    • Notification is esoteric - Remove
    • transformation/formatting may belong under this hierarchy
  • discovery
    • retrieval and mining - Move under collection
    • crawling - Remove (too specific)
    • delivery - Move under "integration"
  • integration
    • aggregation - add term
    • merging - added term
    • interoperatbility - move to preservation
    • conversion and reformatting are very simmilar - reformatting under conversion

[edit] ESIP summer meeting plans

We never got around to discussing this.

[edit] Action items

Revise the IMCR CV considering the notes above and feedback from the RFC. (Colin)

Personal tools
Namespaces

Variants
Actions
Navigation
Toolbox