Member Node Wranglers  - please note time change to half-past the hour
    Fridays at 10:30 am Alaska
                    11:30 am Pacific
                    12:30 noon Mountain
                    1:30 pm Central
                    2:30 pm Eastern

Please note new GTM info, also:
25 July 2014
                                                                  
Attending:   Laura, Rebecca, Mark, Amber, Bruce

Regrets:   Dave 


Agenda: 

NOTE:  New meeting time at least through the end of July - 2:30p Eastern

        1. High profile issues (or current items of interest
        
        FOLLOW-UP -- DUG activities/outcomes:
            

        1.5   Current MNs
               
                
        2. Status of upcoming MNs
     
    Future
        3. Old action items
              MN Documentation - MN Deployment and MN Ongoing Operations - Laura to do  this>>>>   use Ask.dataone.org - where can I find? is there  documentation  on....?  
             
        4. Not-high profile issues
            (Was under Current MNs related to SANParks, CDL, etc.)
            LT  to address Memorandum of Understanding (re: operations and service expectations) between DataONE and MNs
            suggestion: compile a list of common hangups from both perspectives - these might be good points to include in the MOU, such as:
       
        5. Around the room
        Rebecca - nothing new
        Bruce - nothing else
        Amber - dashboard does not display on the mobile version of the website, so for time being remove that functionality and display tabular MN information (not data)
        Mark - ARCTOS (hosted at TACC) - Mark knows Gordon Jarrell and can follow-up with them.
                - will alternate weeks focusing on DataONE and LTER
        


Tickler (things to revisit periodically)

Purpose of MN Description Document (past and future) 
    Intent is to describe the (potential) MN, identify the types/quantity/formats of data they hold, - perhaps we need a  "friendlier" format, perhaps an interview process;
    Workflow: should this information (MNDD) be collected at the beginning of the process, or is the way we've been doing it lately (after the fact) a new way of doing business??  Also consider if  this information gathering (form or interview) is the best use of resources for those potential MNs who may or may not become a MN if implemented as a first step.  Possibly change the workflow? Is a pdf the best way to view the information?
    Next steps:  Laura to come up with alternative(s) to current MNDD - content is good, but format/mechanism needs some work.  
    Another thing: Laura and Amber to look at workflow for last stages of implementation, test with EDAC  too late for that, need to pick another one.
    Also -- how does the MN DD relate to: 
                    the node document:  https://cn.dataone.org/cn/v1/node  - developers have/create this information (node registration, see updateNodeCapabilities)
                    and redmine??    <--- work with redmine as mostly-authoritative source
    Could a spreadsheet be a viable solution?  Maybe.  A database would work.  In any case, some information is appropriately "private" -  how  would we handle that?
                

Revisit the default "only results with data" checkbox to unchecked; plan is to move the   checkbox from search page to results page but remain checked by default, initial draft in development environment.
               
Bob's feedback about the dashboard - he suggested a count of MNs on the dashboard (MNs, RNs), probably/maybe an easy thing to do a count of MNs and RNs and display