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:
1 August 2014
Attending: Laura, John Cobb, Amber, Rebecca, Bruce, Dave, Mark
Regrets:
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:
- MPC Progress - still working on getting DC information to Tracy et al. BEW: need to resolve the container question and propose specific fields that should be mapped to the indexing.
- DUG discussion re: increased MN involvement with DataONE - letter drafted, intend it to come from Bill with current/prospective MN representatives as recipents. Who do I need to get the distribution list to? Rebecca
- current MNs: eBird, Dryad, EDAC, LTER-Europe, AOOS-GoA, KNB (Matt), LTER, UC3-Merritt, ONEShare, ORNL DAAC, PISCO, SANParks (Matt), SEAD, KUBI, USA-NPN, USGS-CSC
- upcoming/prospective MNs: GLEON, NKN, MPC, PPBio, GBIF, U S Carolina, UIC, IARC, EU BON, TERN-Australia
1.5 Current MNs
Dryad listObjects issue, see https://redmine.dataone.org/issues/6010
Robert queried a particular date range but results returned records out of bounds; Robert has talked with Ryan and he is aware of the issue and will address next week; potential for impact in synchronization if dates are being interpreted incorrectly (doesn't look like a time zone issue - conversation with BEW and LM yesterday)
LTER on schedule to transition from metacat instance to GMN tomorrow; name/nodeID will not change but will update description; LTER would like to deprecate current metacat content but that may change... content moving forward on the GMN - some is identical to current data, some is new; all new identifiers (even content that is the same in new as in old)
2. Status of upcoming MNs
- Y5Q4--> Phase 2 Y1Q1
- GBIF (4730) - development paused while GBIF does their annual planning; thinking about working with Atlas of Living Australia (VERY early discussions). Discuss the MoC request from GBIF
- ORNL MNs (RGD (4248) and EDORA (4247)) - news item out for review; meeting 8/7/14
- GLEON (3422) - Nothing new. passed the MNDD template on to Corinna - she will pick up when she gets back in August
- MPC (3708) - Bruce to get DC "wrapper" info to Tracy, Tracy to apply DC to a couple datasets in sandbox and we'll see what happens/what works best
- USCarolina (3689) - awaiting response
- DFC (3532) - Lisa doing development and running WebTester. Next step - get DFC in development environment
- UIC (3213) - they're having a project prioritization meeting next week, will have a better idea of schedule for next 3 months after that (completion required by 31 Oct).
- PPBio (3748) - MNDD/logo submitted, Listed on public website as upcoming
- SAEON (3205) - Chris or Mark will be able to help Alex at SAEON.
- NKN (3238) - at MNF yesterday, Ed said they are ready to set up MN in sandbox (after switching to redhat); he asked if they could use the same certs, and we said probably (if there's a problem we can issue new certs) - awaiting response
- IARC (4700) - working on who will be his DataONE POC
Future
- Montana State University Institute on Ecosystems (IoE) (3687) - in testing, nearly ready to go to production (news item drafted, MNDD/logo available) Listed on public website as upcoming
- TERN-Australia - Rebecca and Bruce working on wording of MOU -
- FigShare - Bruce is POC
- NODC - revisit, target for next 18mos (Bruce/Matt) - Bruce to talk with Ken Casey
- EU BON -- Looking to deploy a test MN (probably Sierra Nevada - August/Sept (Aug 10-Sep 7 we think) in Albuquerque to talk with DataONE developers) in the next 6-9 months. Rebecca/Mark to talk about the Sierra Nevada visit (timing, discussions, etc.)
3. Old action items
MN Documentation - MN Deployment and MN Ongoing Operations - Laura to do this -- working on identifying needs and best methods to address those needs, including ask.dataone.org, documentation in mule1 or on dataone.org, etc.
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:
- does the MN need to have harvesting turned on all the time, even if they aren't adding new data to their repository?
- what's the harvest frequency? MNs may not know, need to document (John already asked this in ask.dataone.org and Matt replied)
- what about certificates? does the MN need them? what kind (client/server)? can I use the same certificates in all environments (sandbox, stage, production)?
- what are the expectations regarding uptime? ideally a MN would be up all the time, but there are times when it cannot be (upgrades, backups, etc.); minimal downtime is acceptable, but what if a MN is down a lot (infrastructure problems, power outages, etc.)?
5. Around the room
Amber - Laura/Amber talked this week about the process near the end of implementation, timing issues, when a MN appears as an upcoming MN on the dashboard, defining the MN "name" - pull from the NodeDocument??
more talk about the dashboard - wonky things happening 7/31 and 8/1 - different protocols (http vs https) and different browsers saw different results; Dave and others are/have been investigating (right NOW, FF and Chrome return results immediately (at UTK) and IE croaks) - this is not something that DataONE can "fix"
Dublin Core conversation - there was some discussion at a developers meeting last week about using DC (specifically for MPC and in general); concern that use of DC is not the way we want to go, but there are many potential MNs who use/can use DC, so there is a (potentially) greater demand for DC;
one option is to have a more generic method of identifying and pulling DC fields from a given container (EML, FGDC, OAI-PMH, etc.)
there isn't a specific DC container (so we could put DC fields in a file labeled "metadata" and we would pull from there for indexing)
what if you have multiple title fields? pick one (consistently)
Rebecca - question for Mark (done)
John - nothing
Mark - nothing MN related today
Dave - nothing else today
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