Difference between revisions of "Documentation Cluster Minutes 2016-04-25"

From Earth Science Information Partners (ESIP)
 
Line 11: Line 11:
  
 
'''* Presentation about GCMD Keywords API - Tyler Stevens with Thomas Cherry (developer)'''
 
'''* Presentation about GCMD Keywords API - Tyler Stevens with Thomas Cherry (developer)'''
- GCMD curating keyword list for over 20 years
+
* GCMD curating keyword list for over 20 years
- '''SKOS concepts:'''
+
* '''SKOS concepts:'''
- concept schemes (science, platforms, instruments, etc) - currently not related to each other (but COULD be), ids, definition, broader, narrower, related, pref label, alt labels, hidden labels, date, and uuids for each concept.  
+
* concept schemes (science, platforms, instruments, etc) - currently not related to each other (but COULD be), ids, definition, broader, narrower, related, pref label, alt labels, hidden labels, date, and uuids for each concept.  
- uuids will NEVER change
+
* uuids will NEVER change
- RESTful service, provides fragment URLs to capabilities. e.g. wildcard pattern searches
+
* RESTful service, provides fragment URLs to capabilities. e.g. wildcard pattern searches
- also have static KMS - to retrieve cached copy
+
* also have static KMS - to retrieve cached copy
- e.g. RDF for Atmospheric Pressure - has one broader concept and several narrower concepts
+
* e.g. RDF for Atmospheric Pressure - has one broader concept and several narrower concepts
- can request particular format in rest api (csv, json, rdf...)
+
* can request particular format in rest api (csv, json, rdf...)
- '''Users'''
+
* '''Users'''
--Doc Builder- QA Viewer and Metadata Management Tool fo CMR) - pull in keywords from KMS
+
* Doc Builder- QA Viewer and Metadata Management Tool fo CMR) - pull in keywords from KMS
-- GCMD Search client uses KMS to populate the facets, call KMS in real time
+
* GCMD Search client uses KMS to populate the facets, call KMS in real time
-- Earthdata Search Clients - pulls RDF and caches it on their end for a couple days
+
* Earthdata Search Clients - pulls RDF and caches it on their end for a couple days
-- Australian Antarctic Data portal
+
* Australian Antarctic Data portal
-- Ontology building - early version of SWEET used GCMD (years ago)
+
* Ontology building - early version of SWEET used GCMD (years ago)
-- slide has links to API, static directory, documentation
+
* slide has links to API, static directory, documentation
 +
* DocBuilder - QA Viewer has built in validation of keywords, can upload DIF/ECHO and will validate record against KMS, eventually ISO. -- no date for production yet
 +
** eventually would like to integrate ruleset options
 +
* Ed: can you go over how earthdata Search client is using the KMS? -- they developed an interface called the facets - queries the keywords with document counts for the keywords.
 +
* Ed: are they using the KMS to determine the ranking structure? -- don't know the strength of ranking in earthdata search client yet..
 +
* Ed: Chris Linus proposed a search relevancy hackathon at summer session. The KMS might interested in being involved.
 +
* Anna: organization keywords organized into "buckets" that are difficult to split up.. short name and long name with acronyms tacked onto the end is too long for metadata authors.
 +
* can contact Tyler Stevens directly if have more questions.
  
  

Latest revision as of 13:03, April 25, 2016

https://esipfed.webex.com/esipfed/e.php?MTID=mc78742141152f0a7f2f2557af0c733f2

Attendees

Aaron Sweeney, Ed Armstrong, Heather Brown, John Kozimor, Paul Lemieux, Phil Jones, Tyler Stevens, Annie Burgess, Lindsay Powers.

Agenda/Minutes

* Summer Sessions Planning -- Sean Gordon has ideas for the metadata lab- he and John Kozimor can take the helm for Metadata Lab Session -- Erin move metadata for events into user engagement Annie: Documentation lab is scheduled for Thurs at 4. Metadata for Events into user engagement on Tuesday morning. There is room for sessions to be merged. each session is an 1.5 hour block.

* Presentation about GCMD Keywords API - Tyler Stevens with Thomas Cherry (developer)

  • GCMD curating keyword list for over 20 years
  • SKOS concepts:
  • concept schemes (science, platforms, instruments, etc) - currently not related to each other (but COULD be), ids, definition, broader, narrower, related, pref label, alt labels, hidden labels, date, and uuids for each concept.
  • uuids will NEVER change
  • RESTful service, provides fragment URLs to capabilities. e.g. wildcard pattern searches
  • also have static KMS - to retrieve cached copy
  • e.g. RDF for Atmospheric Pressure - has one broader concept and several narrower concepts
  • can request particular format in rest api (csv, json, rdf...)
  • Users
  • Doc Builder- QA Viewer and Metadata Management Tool fo CMR) - pull in keywords from KMS
  • GCMD Search client uses KMS to populate the facets, call KMS in real time
  • Earthdata Search Clients - pulls RDF and caches it on their end for a couple days
  • Australian Antarctic Data portal
  • Ontology building - early version of SWEET used GCMD (years ago)
  • slide has links to API, static directory, documentation
  • DocBuilder - QA Viewer has built in validation of keywords, can upload DIF/ECHO and will validate record against KMS, eventually ISO. -- no date for production yet
    • eventually would like to integrate ruleset options
  • Ed: can you go over how earthdata Search client is using the KMS? -- they developed an interface called the facets - queries the keywords with document counts for the keywords.
  • Ed: are they using the KMS to determine the ranking structure? -- don't know the strength of ranking in earthdata search client yet..
  • Ed: Chris Linus proposed a search relevancy hackathon at summer session. The KMS might interested in being involved.
  • Anna: organization keywords organized into "buckets" that are difficult to split up.. short name and long name with acronyms tacked onto the end is too long for metadata authors.
  • can contact Tyler Stevens directly if have more questions.