Community Dynamics Weekly call

• Date: 2014-10-10
• GoToMeeting: https://global.gotomeeting.com/join/305378669
• Participants: Matt, Peter, Lauren W., Scott, Chris, Corinna, Andrew

Agenda and Notes

Design/Development update

• Run Manager: Peter checked in run-manager document describing features

  • https://github.com/DataONEorg/sem-prov-design/blob/master/docs/PROV-capture/Run-manager-API.rst
  • a. Need feedback from Bertram and others
  • b. Should there be a different API for multiple languages?
    • No. Should promote consistency and ease-of-learning
    • Should be feature similar within language constraints

• Starting on prototypes

  • a. Need DataPackage class to be formalized to start
    • can we just use the existing Java-based DataPackage?
    • Peter: yes, we could
    • Matt: we could convert all of DataPackage to native R except for the ORE serialization
  • b. Tasks for prototype
    • task: start prototype record() implementation
      • task: design data storage for run metadata (runId, dates and times of exectution, sessionInfo(), package dependencies and versions, etc.)
        • possibly follow codemeta specification for software metadata (https://github.com/mbjones/codemeta)
    • task: prototype view(RunID)
      • task: design the view output format, keyed on RunID
      • should view(RunID) be the proper call, versus view(DataPackageID)? probably RunID?
    • task: prototype listRuns()
      • task: design the run listing output format, keyed on RunID
    • rdataone -- Matt: continue on moving to native R v 2 api
  • c. R dataone query functions
    • what should query function return?
      • XML SOLR output
      • JSON SOLR output
      • parsed data structure of all of the fields into data frame
        • or separate (as.data.frame(XMLSOLR as input))
    • Needs to be extended to query both object and event indexes

Use Oct 24th meeting for:

• the codyn R package discussion
• review the recordr package design with the science community