Member Node Discussion 10 May 2013 Attendees: Laura, Rebecca, Amber, Dave, Mike Regrets: John Cobb(on the phone from the road),Suzie, Matt Discussion: MetaAgenda: Reforming the standing agenda structure 1. High profile issues (i.e. SEAD's push for NSF demo) 2. Status of MN's (run quickly thorugh the list and highlight a few - touch-base with redmine status) 15 min (list them all, flag things we want to discuss at the meeting) See the overview (backlog) in redmine that Dave put together, copy that over here in the meeting's epad. 3. old Action items (update before the meeting so status is available at mtg) 4. not-high profile issues 5. around the room Ancilliary issues: Agenda formed by Wed for Fri. mtg. Updates and queries initiated before Friday meeting General focus: leaning more to actual MN interaction rather than process. Move to a single epad per meeting proposed url for: (Yeah! wonderful idea) Redmine issue review In looking at open redmine tickets for MNDeployment, I see several that are "stale" that we haven't touched in some time. Either things are happening and we're not updating, or nothing is happening. We suggest as a tickler I should note the tickets which are stale, which will send out a notification to all of us, and the person who is responsible will hopefully be able to respond appropriately. Highest priority - things in progress, MN implementations have everything they need to move forward to production; be on top of these MNs Next priority - people who have expressed interest; we need to check back with someone either on MN side or CCIT side to get information about where this potential MN is in the process (just interested, gathering information, etc.) As we go through the list of MN tickets, we should have a better idea of where each one is in the process. Who's on first? - MN implementation ticket is assigned to one person, with sub-tickets assigned to others, perhaps, who will accomplish these subtasks. The primary person should be the one who keeps track of the ticket and updates it. Ensure essential info is on each ticket, main contacts at MN, point to any other relevant documents, other attributes. ACTION at/before next MNW: look at open redmine tickets and ensure they are assigned to the right person. Important to do this periodically (monthly? biweekly?). What defines "stale"? Not touched in 2 weeks? a month? Rebecca: Perhaps include in the ticket a deadline/timeframe for action. John: use that timeframe as the tickler to revisit Dave/Matt: let's just pull up redmine during the meeting to make changes, link in epad Rebecca: maybe focus on the top three MNs at each meeting - must define what it means to be in the top three Dave: maybe use the sprint concept, or set up sensible milestones to be met and as MN approaches milestones Rebecca: heard back from Todd, who says their implementation is "imminent" Dave: set a deadline, and if Dryad isn't "on" by the deadline.... consequences Amber: Todd registered for DUG Dave: sit on it another couple weeks, then follow up Rebecca: will copy email from Todd into Dryad's redmine ticket Mike: when does Dryad have their next advisory board? perhaps discuss there if DataONE membership is a priority for them Rebecca: board meeting May 24; probably not something that will have an effect SEAD as a production MN, they need to validate their content and are no technical issues holding them back. (Yay!-LM) There are some access issues that they need to investigate before proceeding. KU (Kansas) - Dave: people in the know are on vacation right now. Bob Sandusky at DSpace meeting this week, pushing the notion of a general D1 plugin for DSpace, has gotten feedback from Kavitha and Ryan re: their respective implementations. Rebecca: Isn't DSpace being rewritten right now? Dave: Yes, one of the issues we're looking at now re: its relationship to D1. Dave: TFRI MN very close, in stage testing, need update to ONEMercury (pushed out this afternoon) for them to proceed Amber: ARCTOS has a "rejected" ticket Dave to add "duplicate" as a status in redmine; Laura to update ticket 3693 recapping action items Rebecca: we want to make sure we use the great feedback we received at the SC/UA meeting last week John: notes from epads being collected/massaged for public consumption personas are taking longer than we thought, but they are progressing, we have AmberO to help us policy/procedure Rebecca: need to John: external website stuff available in the next two weeks, policy/procedure revisit at DUG based on what we drafted plus feedback from SC/UA Amber: link to mockups from Matt https://docs.dataone.org/member-area/member-nodes/coordination-work-area Dave: dashboard is near the top of the priority list Rebecca: as we approach end of our 4th year, we need to stay on top of our priorities and ensure accomplishment/completion Rebecca: do dashboard items need a lot of work or are they straightforward Dave: content is straightforward, design needs some work; unless there are major changes in requirements, can be done fairly quickly; would like to have this done as well as usability testing before the DUG SC&UA recap Persona status and progress Comments on proposed documents Assessment/metrics - John showed the metrics we currently have available and solicited input from participants re: are these good metrics, do we need something different MN Scaling - range of 20-4800 MNs suggested in the meeting, some people put calculations on those estimates; what are roadblocks?; what can we do to mitigate these roadblock issues. Around the room Amber: with DUG coming up, we need to start encouraging people to register, esp w/respect to MNs and their MN showcase activity - we need to provide them some guidance re: what aspects of their MN they are to present; Amber to send Laura list of DUG registrants, Laura to check against MN contact list and ask them if they want to participate in the showcase. ACTION: Amber and Laura to come up with template to deliver to participating MNs so they will have a starting point. Laura to look at unregistered MN POCs. Need the MN's slides beforehand. Rebecca: nothing today. Dave: nothing today. ================================================================== No meeting 3 May 2013 ================================================================== 26 April 2013 Attendees: Rebecca, John, Amber, Suzie, Bill, Amber B, Dave, Laura, Matt Regrets:Mike Discussion: SC&UA WG Mtg Prep Personas: Comments Fewer complete is better than more incomplete MN Persona template draft: https://repository.dataone.org/documents/Committees/MNcoord/Coordination%20Work%20Area/SC%20UA%20Joint%20WG%20mtg%2030Apr-2May/DataONE%20Member%20Node%20Persona%20Template%20-%20DRAFT.docx) MN Persona definitions (categories we've come up with so far): https://repository.dataone.org/documents/Committees/MNcoord/Coordination%20Work%20Area/SC%20UA%20Joint%20WG%20mtg%2030Apr-2May/DRAFT%20Definitions%20of%20MN%20personas.docx Some dimensions to categorize: Type of content Large - satellite Small data with high metadata/data ratio MN resources in Operations (L,M,H) Organizational type independent research laboratory institution/enterprise Government lab Level of curation Main purpose of repository Funding (related to organization type) "Divide it up and hit on all the axes" Ex: KNB (long-term presevation) is different from DAAC (agency repository) is different from a senior scientist's lab Extract the essences of how they differ. Document review How to assess and measure MN actvities Scaling Caveat: Don't restate the obvious. How to capture ex-post-facto case study analysis what to "write-up"? How to keep short but informational (Redmine or something else?) How to communicate effectively to MN's as a body of knowledge Modifications of process document - ongoing operations communications connection to ask.dataone.org Comments on common examples mis-undersanding of DataONE Possible solutions: put in documentation add into checklists DataONE should try to be aware and sensitvie to "latent" issues that may indicate mis-understanding Effectively communicate back to DataONE when an error is detected. (Matt) Over time we will build a community of understanding. (Does this lead to a best-pracitce/tutorial process) Bill: How to lower the barrier of integrating MN's MN-lite Also in context of phase -II Possible: slightly re-orient Th. Morn session. MATT: MN-lite is a good idea Tier-1 is a light-wieght MN b/c we were trying to achive a certain level of Functionallity. Dropping some interoperabiltiy requirements could make it even easier C.F> Kunze "Slender node" concept - just harvet ... --> Approved Policy John: External page draft (in process darft expected 20130311) (ack: Rebecca query - what's up?) Initiate contact with GLEON and Triana (correction probably Corinna Gries): (In Process: who is tagged for this?) Global Lakes Environmental Observatory network (part of PRAGMA - indirectly related) Corinna Gries has a NSF proposal under consideration to get a DataONE set setup. Status unknown.status deferred. assign to Dave. * Agenda: MNF Item: Plan to incorporate MN contacts into Redmine, Action Item: automate Redmine issue creation authorization when docs access granted. (Dave Volunteered) MNF Item: Need two new information locations to help development. a. cross map SW versions for DataONE SPI and ITK tools - what is current? What levels are compatible? b. location of proper repository and location of DataONE extensions for externally hosted ITK components MNF Item: Need a channel of some sort for "how do you ...?" questions during implementation and testing. Approach? (Dave mentioned an approach similar to stackoverflow on the 20130308 LT call) - default installation EDAC: How do we add people add to MNF dist list. Is it Idea: creat MNForum@dataONE.org EDAC status: testing Rob Nahf working to help. Identifying some issues with the tester. Then register EDAC in a test environment - maybe next week Lesson learned: communication r=Rebecca: this is a good data point of how communication is working for non-DateONE insiders. AI: contanct Soren to followup to insure communications working AI: SEAD coming soon - asisgn someone eBird, AKN name change and process?: urn for existing node will change from CLOAKN to EBIRD, new node (AKN) will probably have urn of AKN. AKN POCs are Andrea Wiggins, Leo Salas, and Katie Koch. eBird's POCs are Steve Kelling and Kevin Webb. Changing urns is a big no-no, since a lot (all?) infrastructure is tied directly to the URN. Dryad Status: waiting on Dryad at this point. CCIT Santa Barbara meeting wa productive. A discussion would be worthwhile next step: Have Chris or Skye contact Ryan. Maybe go over the document about outstanding issues needing resoluton. Q: Are all issues contained in tickets already? A: not yet. Note: There is a Dryad ticket system that may contain many of the "go do's" DataONE liason: Robert, Chris, or Skye Status of replication nodes? registered but are not receiving content. We have 5 replication nodes: 2 OR 2 UNM 1 UCSB Matt: About to start to do a sweep for replication content. We are going to move to a state where replication is on. Why 2 RMN's? Different technology stats. One is GMN and one is Metacat. other tier 4 nodes: KNB, maybe LTER tier 3 nodes (by desire. Technically could be tier 4) SANparks, PISCO AI: complete replication and "celebrate" with external communication. Also follow-up with Amber May USGS workshop: We may have some sequester limbo: ** New News/around the room: Rebecca: 1 Public web-site will have pointers to information locations: 2. "How to become a member node" 3. "process approval" ====================== 2013-02-15: Attendees:John Cobb, Laura, Suzie, Rebecca, Amber, Bill, Matt, Mike\ Regrets: Link to view Member Nodes backlog: https://redmine.dataone.org/rb/master_backlog/mns Previous Action Items: Bill: Contact Duraspace no update. John: External page draft (in process) MN office hours call: John & Laura: (Done) Now called the MN Forum. Update Redmine (John) All: (ongoing) ensure Redmine reflects state of contacts and contains contact communications. update operational nodes tickets Also search etherpad for MN related discussion (Laura)(John) - posted at (All) transfer information from scraps of paper into Redmine Contact new member nodes EDAC - Soren is working through a few more items this week, checking in again next week We have received a new MN description document from Soren for EDAC. "Very close" they have a full implementation and are testing. Low probabilty of making it by RSV. NKN: (Mike Frame, JWC): (no update) eBird (and not AKN), (JWC) : up! SEAD: (In Process) Ryan contacted by SEAD. They are interested in the Dspace implementation. Laura is inviting the SEAD folks to the MN Forum meeting next week. Dryad - waiting to free up a developer to work through final testing (blocked by work on 1.1 release) (Status after CCIT?) CCIT Santa Barbara work went well. Dryad has a complete SW stack. Test ran yesterday and failed a couple of tests. Does DRYAD represent a generic DSPace implementation? Ryan says it will be a good basis. Prepare submission for a MN workshop in Denver May 20. Abstract due: Feb. 22 (JWC, Mike Frame) - Mike is working on 1st DRAFT and will send to John NEXT WEEK (Done?) Begin to prepare. Prepare policy document for MN process workflow (JWC) (in process) Initiate contact with GLEON and Triana: (In Process) clean up tickets in Redmine for operational nodes (John Cobb) ongoing remove from list EDAC Description Form (In Process) Soren is in E-mail contact with Laura and others (see above) * Agenda: ** New News: - First MN Forum call Th. Feb. 21 2:00-3:00 PM EST : "Office Hours" type of forum - this turned out to be the best time for the MN's that responded to the Doodle poll Update on project and then provide a chance for people to ask questions - Amber Owens SciData graduate student at UTK and is joining the MN Wrangler group. She will work for 18 months. PLease welcome her - Amanda Andrews (PR masters student) and Paul Domingo (AD masters student): They are using DataONE for their STEM communications calss project. They will draft a communications campaign that will hopefully to be use to DataONE. They have discussed an overview with Allard, Moyers, and Cobb. They will look at some previous messaging ** New Discussion Items: SEAD: interested in moving forward. Has an implementation in testing. Has a question about resource maps. EDAC: In process. Issues? Dryad: Testing? Status? Does progress with Sryad tran ** Around the room: Amber; MN area of the web-site to make more inviting to MN information. Suggestion, bring up the current MN pages as the MN page. Mock up at: sent via email at 11.23am (MN Mock Up) Also at: https://docs.dataone.org/member-area/member-nodes/current-working-folder-for-mn-documents/MNMockup MAybe insert a MN highlight into the homepage rotation Matt: PELD node still in progress. They have upgraded Metacat. Setting up SSL certs. Moving along. PELD group is discussing what it means to be a member. They wanted to write up a DataONE MOU. DataONE encourages just assenting to partnership guidelines. Issue: DataONE needs to think about how to address the MN agreement form. Hope that PELD comes up a few weeks after the RAV. UK node: testing now. May be online by review. Technically might be there. ** Next Meetings: Feb 22 No - March 1 - No, March 8! ====================== 2013-02-01: Attendees:John Cobb, Laura, Bill Michener, Amber, Regrets: Rebecca, Suzie Link to view Member Nodes backlog: https://redmine.dataone.org/rb/master_backlog/mns ToDos: Bill: Contact Duraspace John: External page draft External website MN office hours call: John & Laura: Update Redmine (John) All: ensure Redmine reflects state of contacts and contains contact communications. update operational nodes tickets Also search etherpad for MN related discussion (Laura)(John) - posted at (All) transfer information from scraps of paper into Redmine Contact new member nodes EDAC - Soren is working through a few more items this week, checking in again next week NKN: (Mike Frame, JWC) eBird (and not AKN), (JWC) SEAD: (who?) Dryad - waiting to free up a developer to work through final testing (blocked by work on 1.1 release) Prepare submission for a MN workshop in Denver May 20. Abstract due: Feb. 22 (JWC, Mike Frame) - Mike is working on 1st DRAFT and will send to John NEXT WEEK Prepare policy document for MN process workflow (JWC) [also incorporate principles and other ether pad comment ] Initiate contact with GLEON and Triana ******** Agenda: New to DO's clean up tickets in Redmine for operational nodes (John Cobb) EDAC Description Form ************************* New Discussion Items: 1) Examination of the MN prioritization in Redmine 2) Status of description forms: (Laura) 5 updated. 5 outstanding 3) Info: student assistance: (John) 4) EDAC detailed near-term need needs Last communication with Soren at EDAC: A few minor issue to correct. Current status not certain but they are in testing. Proceeding apace with no roadblock. CCIT: contact: currently Dave V. (was Roger) Good chance that it will be up by site visit. 5) Dryad near-term needs needs: In final stages of testing. Ryan's lastest this AM - it was passing tests. Move to staging and production next week hopefully. Mutability issue is not resolved in this release. It will be a member node before the mutability issue will be resolved. 6) NODC contacts: We are having periodic discussions with NODC and ESRI. ESRI needs t ogo back and review the effort involved in setting this up. Especially the levle of reporting required for access. There is a descrepency in reporting in that ESRI's geoserver does not record some loggin information. NODC: National Oceanagraphic Data Center (Miami) Mike: ESRI is also asking do others need this besides NOAA. We are trying to push that the answer is yes - DOI/USGS needs it. ************* Discussion: Laura: setting up dist. lists and outreach commnications. Is there a dedicated CCIT person to add to the distribution. Dave: It is me until we find someone else. LauraL: what to call this meeting? not office hours not "hepldesk" Dave: Call it a forum Mike: If we add new USGS data, will it get into the metadata index in time for the site visit. We are working on the park ervice items. For the tickets: Are there any aspects of the NODC's do we want to put in a ticket? Mike: Matt had been on this issue. conclusion: add a ticket on ESRI outreach. add a ticket to discover agency interest in ESRI geoserver supporting DataONE interoperability. invlve Mike and Matt Mike: USGS workshop abstract. also fix up the line numbers in ====================== 2013-01-25: Attendees: Rebecca, Dave, Laura, Mike, Bill Regrets: Link to view Member Nodes backlog: https://redmine.dataone.org/rb/master_backlog/mns 1/18 ToDos: * Bill: Contact Duraspace - Still need to get in touch with those * John: External page draft (reviewed and up by RSV - 1.5 weeks) * Still in process: Expected 1/23/2013 * Check with amber for preferred Style * Exernal website * John & Laura: preparation for MN's support call - accepted and closed. * All: ensure Redmine reflects state of contacts and contains contact communications. * Reach out to EDAC, NKN, eBird (and not AKN), and SEAD * NKN: (JWC) * eBird: (JWC) * SEAD: (jWC) * RK to add to Redmine * Also search etherpad for MN related discussion (Laura) * List of Etherpads: http://epad.dataone.org/_index/ * Search all Etherpad http://epad.dataone.org/_index/search.html * (All) transfer informatio from scraps of paper into Redmine * Contact new member nodes * EDAC - Soren is working through a few more items this week, checking in again next week * NKN, * eBird (and not AKN), and * SEAD * Dryad - waiting to free up a developer to work through final testing (blocked by work on 1.1 release) Agenda: * Status of ToDos from 1/11 * Items * MN Call coordination * Status of existing Nodes * Status of prospective nodes * other items * Docs location to put new items: https://docs.dataone.org/member-area/member-nodes - confirmed. Laura: 2 more MN Description dcuments are about ready to be deployed Redmine co-learning: Can we group by MNdeplyoment What are the status fields and are they up to date? AI add "operational" Mke: In May in Denver USGS is having a data-managers (?) meeting. Do we want to try to do a MN workshop in or around this meeting? This will include NKN AI: Work to get DataONE representation in Denver USGS mtg. week of May 20 Abstract due Provide MN Wranglers RSV prep - See Dave's EAB slides on this issue - Present a strategy - Present a top5-10 - Metrics for prioritization <--- think about this next week. how many data sets Funding resources Expected usage Expected science impact meta: metrics should be obtainable early-on on MN proposal process Diversity of collections, Institution Type, etc. represented in DataONE. By: Topic Implementation technology Focus (large vs. small , well curated versue "at risk data", cit sci (publicly collected)..) Agency focuse Geographical focus Geographical location of MN Idea: Identify and seek to fill gaps in the union of collections included in DataONE MN's Expected effort for implementation Relevance to DataONE "vision" (scope) - Identification of MN posisbilities - Description of workflow - Be willing to tolerate some WAG - Include the "principles" discussion inthe epads below. Direct access of data from DataONE rather than indirectly (Rebecca) There was an Etherpad discussing MN issues: http://epad.dataone.org/2012Apr17-MN-Prioritization ?? (jwc) other epads http://epad.dataone.org/20110408-MN-subgroup http://epad.dataone.org/2010-11-02-MN-BOF ??? Mike: Are their operational metrics about MN's? Dave: Experience with arious MN's Hard/esy to work with. JWC: There will probably be an metrics/ science impact presentation Rebecca: are any of the MN's Generic MN's now? Dave: All are metacat or Merury now. Slightly off-topic: It would be nice to have somewher - say public web page informations about DataONe collective metrics Bill M. : We did have a mock-up of "DataONE by the numbers" and this might hit that need. Rebecca/Dave: 1.1. release will make some of this possible via log integration. Dave : IS there is "must have by RSV" list of MN's? * Dryad * EDAC also some of the metacat nodes with international representation (i.e. Brazil) Dave: hey are very formal in this partnerships. Current challenge is MOU development. Very low hanging fruit (since RAV is soon) KU could be turned on. Reference spatial data modelling (?) NKN would be good. But I do not know where we are. (May be stuck in politics) NODC would be good, but there are issues. ESRI is looking forbetter justification to continue. * Biota * == good possibilities for in place by RSV Other discussions GLEON Triana See https://redmine.dataone.org/rb/master_backlog/mns for a interative view (similar to CCIT sprint views) ====================== 2013-01-18: Attendees: Rebecca,Dave, Laura Regrets: Mike,Amber,Suzie,Bill 1/18 ToDos: * Bill: Contact Duraspace * John: External page draft (reviewed and up by RSV - 1.5 weeks) * Still in process: Expected 1/23/2013 * Check with amber for preferred Style * Exertnal * John & Laura: preparation for MN's support call - accepted and closed. * All: ensure Redmine reflects state of contacts and contains contact communications. * Reach out to EDAC, NKN, eBird (and not AKN), and SEAD * NKN: (JWC) * eBird: (JWC) * SEAD: (jWC) - RK to add to Redmine * SAlso search etherpad for MN related discussion (Laura) * List of Etherpads: http://epad.dataone.org/_index/ * Search all Etherpad http://epad.dataone.org/_index/search.html * (All) transfer informatio nfor mscarps of paper into Redmine Agenda: * Status of ToDos from 1/11 * Progress Update * New Items Status of 1/11 ToDos: * Bill: Contact Duraspace (Bill Michnenr) * John: External page draft * Still in process: Expected 1/23/2012 * John & Laura: preparation for MN's support call - accepted and closed. * All: ensure Redmine reflects state of contacts and contains contact communications. * Reach out to EDAC, NKN, eBird (and not AKN), and SEAD * EDAC:Dave has contacted Soren - there are some issues with the test environment and Rob Nahf is working on these * NKN: (JWC) * eBird: (JWC) * Laura is working and refining description form * * SEAD: (jWC) * Rebecca: Contact Todd re: Dryad MN Hi Rebecca, The Trello card with current status is here: https://trello.com/card/feat-refine-dataone-api/4f9563b87072e3eb5f06951a/9 I just spoke to Ryan and asked him to resolve the issue of the remaining DataONE API tests with Dave (2 tests fail, but they may not matter), update this card, and document for us exactly what remains to be done both on Dryad's end and DataONE's. As you can see from the Trello board, the DataONE API is currently #2 priority in our development queue. #1 is fixing a similarly long-standing issue with the metadata we provide to EZID. I hesitate to put a time estimate on completing this work, but if all goes smoothly it could be done as early as next week. Is there more you want to discuss about this issue? If not, I'd suggest we simply revisit this once the developers have had a chance to confer. Todd Progress Update: Dryad: (Dave) should happen soon after 1.1 into a test environment looking good for RSV EDAC: (Dave) Testing harness issue ,skes it tought for DataONe to veify EDAC. Continue ntesting next week. possibly available for RSV MN call: Use GoTo meeting and ePad Build list from ist od MN's Create Mailing list and add other interested parties Send out Doodle and start it up. New Items: From Amber: MN discussion: Relating to the idea of having two different documents - one for information gathering and housing on the docs site and one for publishing on the website * The URN field as written received a lot of discussion. It was kept that way because Matt Jones (and CI)strongly felt that in making things user friendly we shouldn't introduce error. They argued that in any documentation, the official MN name (URN) needs to be used for cross reference. * The form can be edited so that the 'instructions' (areas within brackets) can be written into the grey fields such that once a MN starts completing the field, the instructions disappear. This means the help information will be there for MNs completing the form but reduces the need to create a second document for the public website. If agreed, I can implement. * Any editing of the form questions should also be done by this group (and reviewed by the LT?) at this time and again, I can implement. * Another option might be to create an html form - either google doc or on our website. Less of a paper trail (which can be a bad thing) but more user-friendly? At our current scale I don't think this is needed but wanted to put it out there. Docs location to put new items: https://docs.dataone.org/member-area/member-nodes - confirmed. Laura: what happends when a Member nodes leaves? Preservation WG has had a discussion. Answer (provisional) Default: Content remains in the system MN can request content to be marked "archive" Actual content removal is "frowned upon" "content" means registered metadata as well as replicated copies of data. Replication target stops replicating: in the architecture. ====================== 2013-01-11: Attendees: John Cobb, Laura, Suzie, Mike, Rebecca, Bill, Amber Regrets: ToDos: Bill: Contact Duraspace John: External page draft John & Laura: preparation for MN's support call All: ensure Redmine reflects state of contacts and contains contact communications. Reach out to EDAC, NKN, eBird (and not AKN), and SEAD Rebecca: Contact Todd re: Dryad MN Progress: (previous action items) - Work continues on identifying documentation/communication re: MNs in docs, mule1, repository. Most of what I see in mule1 and repo is of a more technical nature and not necessarily what a prospective MN wants/needs to see at first. - All currently operational MNs have been contacted to confirm currency/correctness of their MN Description Documents or to submit a Desc Doc. Responses back from all 10, with 3/10 current/correct as of 1/10/13.(5 had a document of some sort on external web page - 3 of the 5 are current) - John and Laura think that Dave V's Road Map to a Member Node https://redmine.dataone.org/projects/mns/wiki is a great place to start, with few if any changes, in development of a procedure. There is quite a bit of documentation in this area. We just need to consolidate and tailor to target audience. Agenda items: + update progress Documentation continuing. Some technical information is coming to light. Useful but not first contact information. 10 operational member nodes. All have responded 3 of 10 have current and correct information on the public web-site Examined Dave's roadmap for member nodes (see EAB documents and redmine WIKI. another expanded process document (no electronic version) PErhaps a S&G source documents (https://docs.google.com/drawings/d/1VGK80N56wYj9qovBBAgL6d0Xld1mPY6onyQjFwgJu1Q/edit) + potential member nodes: - Earth Data Analysis Center (EDAC) at UNM - Karl Benedict has questions that aren't being answered so far. How do we help? (related: email from Soren Scott on building up MN communicaiton - possibly via DUG) Roger is coordinating with EDAC. Note in redmine who is the developer/coordinator associated with each MN. - Northwest Knowledge Network (NKN)- USGS - Greg Gollberg at UIdaho (link to Climate Data Centers) EAB has endorsed regional climate centers as a good near-term set of candidates. Some internal UIdaho discussions about data sharing policies that need to be resolved. Berrian Moore would like USGS to work with a single architecture rather than let a lot of flowers bloom. Mike: Greg was funded to pilot data management for cliamte centers. Becoming a DataONE MN is part of that effort - SEAD (developer: Kavitha Chandrasekar - will put this in Redmine) + John's homework - strawman of external web page material - IN PROGRESS External facing: A series of question and answers: 1. What is DataONE? 2. What is a MN? 3. What is the value of DataONE for scientists? 4. What is the value of DataONE to a prospective MN? 5. What is the process to become a member node (answer is Dave's process workflow) Also see the DUG packet in the Docs area. IT is a goto poi In Process: approach: A set of questions and answers + It has been suggested that we implement regular MN meetings for MN representatives to bring questions/issues to the table so that we may address them in a timely fashion. Should be a virtual meeting on a weekly/biweekly basis, with attendees being John, Laura, MN Technical POCs or their designees. Queue up questions. Users can eventually help new users solve problems via this meeting (sustainability?). Dave: Think about google+ hangouts as well. Mike: I'd suggest you just use this 1 meeting (all you will be able to do before the RSV anyway) as "Hey here is what we are talking about doing, help us frame how you want us to do this, what issues you are currently having, etc.... Suzie's comments were right on in that this would show we have some process in place for sustainability, MN supporting each other, etc... I also wonder Again (I know it has been talked about several times) is a dedicated CCIT full-time MN support person. If MN is a priority, resource it appropriately. I think some of the communication issues is due to our piece mealing of that support function.... Maybe include some far along prospective member nodes. + LT followup item: Interaction with MN's on ingest to prevent understanding mismatches of uploaded mata/metadata (i.e. the resource map issue occurnace during the DAAC update) The difficult learned lesson is that once incorporated into the CN, it is hard to back it out. The lesson learned is that we should coordinate before going live. Monday Devleoper's call will also discuss how to make the back-out process easier + (Bill) We were approached by Michel Kimpton (sp?) they were interested in incorporating DataONE to their offering for turnkey university deployment opportunities. Technical contact is Tim donohue contact @duraspace.org . This is a good way to expand DataONE market penetration by hooking up with Duraspace, Fedora, ... Start with a Conference call. Must have are Kimpton, Dave, V., John Cobb, Tim Donohue, {Bill or Rebecca} AI: Bill M. RSV expected question: "You are in production one. How are operations going?" We need to frame a story here. AKN eBird discussion: snippet from KEvin Webb and Steve Kelling The Member Node Description, Name of resource, and Node identifier are pulled from the existing node configuration which is AKN centric (work on the node started in late 2011). If we are re-branding from AKN to eBird, some work on D1’s part is required followed by some reconfiguration on our end. It might be as simple as changes on our end only, but I will defer to D1 how they want to proceed as far as the re-branding is concerned. Dave V: name change okay. Keep ID the same. ====================== 2013-01-04: Attendees: Suzie,John Cobb, Laura Moyers, Dave, Amber, Rebecca Regrets: Mike Frame,Bill ToDos: - Strawman for external web page (John & Laura) - Inform all necessary about using Redmine for tracking MN contacts (John) - Rough effort estimations for MN deployment as presented at EAB are available in: https://repository.dataone.org/documents/Meetings/20121217_EAB_DC/presentations/20121217_MemberNodeImplementationPlan.pptx - Get MN Description documents (John et al) Also periodically touch base and revise specifically: AKN, LTER, EDAC, OneShare, USGS, Dryad, PISCO, - Template: MN Delpoyment including tasks expected of every MNDeployment. I.e. implement a node deployment checklist as a template deployment. - Modify MN description form to be more general and less changing. proposal: leave the form the same but before publishing in web-site remove site and usage info. slots since these may be changing. remove fields that are nor absoutely needed followup on some fields after deployment, periodically try to automate some fields (size of holdings, ...) - Create a pubic page on usage stats. MN Descriptions: ONEShare, UC3Merritt - John Kunze (jak@ucop.edu) ESA, SanParks - Matt Jones (jones@nceas.ucsb.edu) AKN - Steve Kelling (stk2@cornell.edu) Agenda: ? ad hoc Comments from Laura Moyers: docuemnt review: lookings at Docs and mule. We are getting there RSV wish list: Cobb: 1) Goldberg: Northwesten Knowledge Network ready - what is the process? Moyers: what would a prospect be looking for in answers. Goal: "So you want to be a member node" needs to be done. Workflow: merge Mike and Dave's workflow and present on the external page. EAB question: who is the actor at each step. EAB Feedback: We need to work on a priority list for MN's We need a process We need a prioritization We need to mesh with the prospect list With an eye toward being strategic opportunistic best use of DataONE resources diversity of implementation Materials: output of S&G meeting at Shattuck in Berkeley; and conference call output (http://epad.dataone.org/2012Apr17-MN-Prioritization) giving guidance and lists Goal: Have a story to tell. Approaches to MN's RSV will come up quickly Needed to have a story for RSV REbecca: Herd cats. Many ongoing conversations are occurring. MN discussions ESRI How much information needs to be in here? REdmine Process: MNDeployed "tracker" is one for each MN Tasks are attached to one or more MNDeployments. Completing all tasks under a MNDeployment should lead to MN complete discussion on regular reporting on MN metrics. REcord counts, usage, ... ====================== 2012-12-14: Attendees: Bill, Dave, Matt, John C, Amber, Carol, Laura Moyers, Rebecca Matt listed possibilities for MNs in Brasil - Discussion re Biota and EMBRAPA There ws interest in a in-country CN Funding: stuck at UNM; will talk to Bob Chadduck at EAB meeting next week Laura Moyers is on board at UTK & on this call! D-Space solution for adding new MNs Dave's concerns: * Timing is tight due to RSV at end of February * Several hundred new MNs would impact DataONE operations Timing is important - need to get in contact with Michele Kimpton and DSpace architect plus show interest in Fedora rewrite at Stanford Subgroup meet at EAB next week Next Meeting: January 4, 2013 2012-11-30: Attendees: Dave, John, Rebecca, Amber, Bill, Suzie, - AKN online now or soon - ONEShare likely ready next few days Action items (2012-11-30): - EDAC - DataONE needs to contact to move through next steps - Need a cheat sheet for redmine, especially for MN tracking Notes from the meeting are also starting at line 144 in this epad (can be moved here if appropriate) 2012-11-19: Attending: Dave, Amber, Bill, Mike, Rebecca, Suzie, Matt, John .. meta: :keywords: member node, wrangler, participant, DataONE AI: - plan to have these calls every 2 weeks - on Nov. 30 do a quick review of the highest priority MN's - ensuring we are aware of new MN opportunities - Understand process and impact on CCIT - harmonize the spreadsheet at and the Redmine tasks - Next steps: - white paper on the process - (re)collated list of prospective nodes. Preferably in RedMine - evaluate and adjust hte process for working with the nodes. - get infromation on the external website that gives information (so you want ot be a member node) - Develop a MN - big brother process where existing MN's can shepaerd prospective MN's - EAB meeting preparations, presentation on status and future member nodes. Agenda ------ 1. Status and role of group, meeting schedule, goals for regular meetings Members: John Cobb, Amber Budden, Rebecca Koskela, Bill Michener, Suzie Allard, Mike Frame, Matt Jones, Dave Vieglais Schedule: Call every two weeks, tacked onto the end of the LT call. Expected duration 10minutes or so. First call on the 30th November. Current Status of the Group - Paperwork to DOE/ORNL in support of MN WG is in process. Estimated Timeline is: John has developed a list of Draft Tasks for the group. Will re-circulate to the group. Detailed task planning for Member node coordination UT is hosting/interview and is offering a PostMasters (Will begin Dec 10 - Laura Moyers). MN Totals - 40 Total by Year 5 2. General process for adding member nodes John's SoW: https://docs.google.com/open?id=0B2uOOMpSMNgLdVF5YkI5cGhUY00 - Process overview: https://redmine.dataone.org/projects/mns/wiki - Project in Redmine: https://redmine.dataone.org/projects/mns Task: (Dave) Need to investigate simplifying issue entry / update in redmine, and generation of reports on status of MN implementations 3. Current list of member target nodes - https://redmine.dataone.org/projects/mns/issues?query_id=54 (Amber - can I get authorized for this page?) Next 4 Member Nodes: * AKN * EDAC * EVOS (?) - policy issue * KU - static spatial layers * Dryad needs testing - sounds ready to go MF: question about spreadsheet - Tiger Team approach considered? JC: yes, he was thinking about this approach - talk with prospective MN about policy issues (navigating the DataONE bureaucracy); also the speed dating approach of potential MNs talking to existing MNs, for example ESA meeting Strategy: D1 has been opportunistic; how do we decide on the 40 MNs that should be in place at the end of Year 5 priority matrix (from 1st 2nd DUG meeting?). Also from a S&G Meeting Discussed this issue. size alignment with DataONE objectives Data Holdings Available Resources ...... SA: consider using recommended new MN's from existing MN's MJ: There is some MN's that will take quite a bit of work. Ex. NODC's but they may be important new MN's while some iLTER nodes can almost boot-strap themselves to participate. Bill: there is some very low hanging fruit that is ready to come on as MN's w/ the new SW stack MF: It does also depend on what is considered to be the MN? For instnace, in USGS, we have potentially suggested we would have multiple MN. WM: One criterion was developer support from the MN's such as EDAC and Dryad. DV: Another criterion - if a MN is able to use an exsiting MN SW-stack implementation (GMN, ...) MJ/DV: What is a MN comes up with a single record that fronts their entire data collection? Action - align the spreadsheet entries and redmine entries Priorities: Top Level MN Web Page is needed - Bullets with links to the details Policy, Technical, Existing MN Stacks, What is required.... Next steps: Role of this group? MJ: There are probably some holes that we need to fill. I (MJ) do outreach as part of what I do, but I miss some areas. For example, I am not at SA: I would hope we could create some really thoughtful presentations of the DataONE value proposition. MF: Perhaps we group member can provide John some suggestions as to what they can contribute, how they should be invovled (I know John started this Discussion with some us).... Next CALL: 1. Review High Priority MN 2. Current Status of MN 3. Identification of New Node Opportunities (Brazil - USP; Taiwan) 4. Impact on CCIT when New MN is starting to come onboard 5. Discuss Role of potential "online" MNs - Do we need a MN Support/Self-Help Group - DUG only issue is 1 time per year - needs to be ONGOING 6. EAB presentation DV: try to capture issue resolution in Redmine (Lessons Learned) EAB mtg presentation: Status from Dave: AKN MN will be online shortly - just serving up one record; discussing with them on how to expand on this ONEShare will also be online shortly Discussing Taiwan Forestry Institute next week about becoming a MN Matt having discussion this week with E... Next week Matt and Bill having a workshop about becoming DataONE MNs in Brazil What about EDAC? Karl's presentation indicates that they have >100K items **Action item for Dave (or someone in CI): contact Soren re: EDAC MN Has anyone worked with RedMine? - May not be a familiar idiom, but is usable - Rebecca: Need a quick cheat sheet (JWC: also, an intro to REdmine and a pointer to Redmine features that we do not use but show up on tabs, etc.) - How to assign tickets - example of a good ticket Q: Who would be interacting with RedMine Formalization of the process is needed We all need to look at what is in RedMine - check status of tickets; divide them up among ourselves; work on the tickets; discuss next call AI on Redmine: - update list of members for MemberNode task area on Redmine - (JWC) We also need to add "Moyers, Laura B (Laura)" a role. (she also needs DataONE LDAP entry) - Re-assign RedMine tasks - Write a Redmine cheatsheet - work the tickets - Define a process of "task nagging" **Action item for Dave - add members to the MN project in RedMine **Action item for Matt - create mailing list for this group ** Action item for Rebecca - send link of consolidation of policy on docs site to this group https://docs.dataone.org/member-area/working-groups/sustainability-and-governance/policy-work