Member Node Wranglers 
    Fridays at 10:00 am AK
                    11:00 AM PDT
                    12:00 MDT
                    1:00pm CDT
                    2:00pm EDT) 
 
https://www1.gotomeeting.com/join/430697153
 
20 September 2013
 
Attendees:  Rebecca, Matt, Bruce, Dave, John, Laura, Amber
 
Regrets:  
 
Agenda: 
        1. High profile issues (or current items of interest)
        Documentation - Current status?  Rob is planning to put things on the "dev" website (throw some things on the wall and see what sticks) for everyone to look at re: what sorts of things we want on the MN page.  (here is something he's got out there for the ITK:http://129.24.63.92/itk-developer-guide-2)
        -  Dave:  Rob main guy on this right now, getting things ready for us to look at next week at the CCIT mtg; website and mule
        
        Immutability - USGS has updated their resource maps, see https://redmine.dataone.org/issues/3989  
        -  Dave:  process that should be followed is that when a change needs to be made to a data object, the original should be deprecated and the new one added with appropriate metadata and a pointer back to the old content (original file); what appears to have happened at USGS is that the resource maps were updated in place, identifiers stayed the same but content of resource maps stayed the same; consequence is that there is inconsistency in content, checksums no longer match and we can no longer verify/guarantee that users are retrieving correct/expected content.  DataONE has to come up with a manual fix.  Dave hasn't had a chance to talk with USGS about what happened on their end.
        - Matt:  D1 has recognized that people want to "reuse" DOIs, we've proposed the concept of a series; this may not work for USGS where their SOP is to change datasets in place (i.e. live), 
        - John:  difference between content of the data package vs DataONE's definition of content which includes metadata (simple metadata changes mean a different object, even if the data content is the same)
        - Matt:  we will need more of a policy decision beyond the series concept
        - Dave:  we need some mechanism to support operations at a data center with the understanding that requirements for reproducibility and immutability for DataONE are maintained
         - further discussion about ORNL DAAC, making small changes to system/science metadata but not to data forces a new DOI, DAAC (and other MNs) are required to make said changes from their external customers/funders/etc.; if we don't allow some level of mutability, we create this situation we are in now; need to trust MNs enough to let them decide if a change is significant or not to require a new DOI and the MN to communicate to D1; this issue is on next week's CCIT mtg agenda; also need some (automated?) mechanism to identify and communicate change
         
        OPeNDAP (Hyrax) member node:  We think Jing Tao is looking at the level of effort to do this.  Bruce, Matt, Dave telecon with James Gallagher and Dave Fulker yesterday (9/26/13):  http://epad.dataone.org/20130919-opendap-mn-implementation  
        - another meeting on 10/3/13, enthusiasm but still lots of questions
        - Rebecca:  do we know how many MNs we can attract if we serve OPeNDAP?
        - Matt:  500ish, may work with Hyrax or THREDDS depending on how we do this, NODC and JGOFS(Joint Global Ocean Flux Study) identified; this would be an unfunded project for OPeNDAP, hope to have a scope by the 10/3 meeting
        - Matt question: is this something we want to pursue (higher priority)?  
        - John: several people have mentioned OPeNDAP as in "can we do something simple like OPeNDAP?"
        
        - Rebecca: we need to either change our metrics or figure out how to implement a lot of MNs or explain why we cannot implement them
        
        
        2. Status of MNs 
 
 
 
 
 
 
        3. Old action items
             --  Laura to check into AKN/eBird tickets (3560 and 3209).   
             https://redmine.dataone.org/issues/3560  is eBird (operational)
             https://redmine.dataone.org/issues/3209 is what will be the broader AKN (in Product Backlog)
               Regarding URN,  Steve Kelling says CLOAKN is NOT the right name to associate with the current MN (eBird).  Previously, we had  said (at least amongst ourselves) that it would be really nasty to try to change the URN on a MN.  We probably ought to have a separate meeting, maybe with the eBird and AKN folks or maybe just us and then with them, to try to sort this out.  Laura to check with Chris and the subtask in redmine to see where it is re: changing CLOAKN to CLOeBird (or whatever)
                       
             --  Working on developing a reference architecture document as the intermediate level of detail. 
             
            --  DataONE website   - Action: Consideration of website structure and potential redesign MN under About? Participate?  Data? or as own Stakeholder Tab?).  Have  this conversation at the AHM in the context of the full website.  Hoping to have Dashboard ready by AHM. 
        
        4. Not-high profile issues
        
              Rebecca had asked: what is the status of the issue where some MNs think  they have more products than what DataONE shows?  Is it resolved? (USGS and ORNL DAAC have had this issue where they think they have more data products than we see in DataONE.)
        John: there are redmine tickets which track this issue
         - Dave: this should be resolved
         - Rebecca: Bob sees a difference in what he thinks DAAC should have and what D1 says he has
         - Matt: has talked with Bob, DAAC was not exposing data to harvesting as D1 expected; Ranjeet has changed things on their end so it should be fixed
 
            ... looking at tickets....
        Seeing a lot of tickets which show "new" are probably resolved but ticket hasn't been updated.
              ACTION: follow up on tickets that may not be necessarily assigned to us  - BIG job - let's talk about this again when Dave's with us.
              - Dave: maybe use the 10/4 meeting to go through the list
        
        5. Around the room
            Dave: nothing
            Rebecca: nada
            John: nope
            Matt: nothing
            Laura: all that stuff above  :)