Project

General

Profile

MNDeployment #3532

DFC Member Node

Added by John Cobb almost 12 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Dave Vieglais
Target version:
-
Start date:
2013-10-04
Due date:
% Done:

100%

Latitude:
35.91
Longitude:
-79.04
MN Description:
The DataNet Federation Consortium (DFC) Hydro-NEXRAD rainfall accumulation data for the Carolinas, Maryland, and Virginia uses Hydro-NEXRAD algorithms and NEXRAD data from the NOAA National Centers for Environmental Information (NCEI) to provide spatial datasets that estimate rainfall accumulation at 15-minute time intervals.
Base URL:
http://datafed.org/
NodeIdentifier:
urn:node:DFC
MN Tier:
Tier 1
Software stack:
iRODS
MN_Date_Online:
Name:
Logo URL:
Date Upcoming:
Date Deprecated:
Information URL:
Version:
Sprint:

Description

Member node implementation to connect with Datanet Federation Consortium (DFC) datanet project. DFC Implementation is iRODS so iRODS <--> DataONE Service Programming interface is needed

Subtasks

Task #4044: (Waiting for) Development plan for DFC clarificationsClosedBruce Wilson

Task #6079: DFC: Initial PreparationClosed

Task #6080: DFC: Establish contact with potential MN organizationClosed

Task #6081: DFC: Determine feasibilityClosed

Task #6082: DFC: PlanningClosed

Task #6083: DFC: Join DataONEClosedLaura Moyers

Task #6084: DFC: Integrate MN representatives with communityClosed

Task #6085: DFC: Create DataONE identitiesClosed

Task #6086: DFC: Create MN description documentClosedLaura Moyers

Task #6087: DFC: Scope the implementationClosed

Task #6088: DFC: Plan the implementationClosed

Task #6089: DFC: DevelopingClosedLaura Moyers

Task #6090: DFC: (monitor) Design, code and component test a new MN implementationClosedBruce Wilson

Task #6091: DFC: Local TestingClosed

Task #6092: DFC: Verify that MN passes the Web TesterClosedMark Servilla

Task #6772: Look at sample files from LisaClosedChris Jones

Task #6094: DFC: TestingClosedLaura Moyers

Task #6095: DFC: Registration in environmentClosed

Task #6096: DFC: Register new Science Metadata formatsClosedMark Servilla

Task #6097: DFC: SSL CertificatesClosed

Task #6098: DFC: Generate client certificate.ClosedChris Jones

Task #6099: DFC: Verify successful installation of client side certificateClosedMark Servilla

Task #6100: DFC: Verify successful installation of server side certificateClosedMark Servilla

Task #6104: DFC: SynchronizationClosed

Task #6105: DFC: Set up synchronization of the MNClosedMark Servilla

Task #6106: DFC: Verify MN Content and Services in Testing EnvironmentClosedMark Servilla

Task #6118: DFC: Check Authentication and Authorization in Testing EnvironmentClosedMark Servilla

Task #6119: DFC: Science Data accessClosedMark Servilla

Task #6120: DFC: Science Metadata accessClosedMark Servilla

Task #6121: DFC: Log record accessClosedMark Servilla

Task #6123: DFC: Registration in PRODUCTION environmentClosed

Task #6124: DFC: Register new Science Metadata formatsClosedLaura Moyers

Task #6125: DFC: SSL CertificatesClosed

Task #6126: DFC: Generate client certificate.ClosedMark Servilla

Task #6127: DFC: Verify successful installation of client side certificateClosedMark Servilla

Task #6129: DFC: Register MNClosed

Task #6130: DFC: Set up Node documentClosedMark Servilla

Task #6131: DFC: Set the node status to approved (start synchronization)ClosedMark Servilla

Task #6132: DFC: SynchronizationClosed

Task #6133: DFC: Set up synchronization of the MNClosedMark Servilla

Task #6134: DFC: Content ReviewClosedLaura Moyers

Task #6151: DFC: Transition to productionClosed

Task #6152: DFC: Mutual acceptanceRejected

Task #6153: DFC: Verify content available for Current MNs web pageClosedLaura Moyers

Task #6154: DFC: Create legal documentsClosed

Task #6155: DFC: Create news itemClosedLaura Moyers

Task #6156: DFC: Formal announcementRejected

Task #7683: Show DFC as "upcoming" on the MN dashboardClosedAmber Budden

Task #7704: DFC: refresh sandbox and retestClosedMark Servilla

Related issues

Related to Infrastructure - Story #4073: iRODS MN Stack development Closed

History

#1 Updated by John Cobb almost 12 years ago

  • translation missing: en.field_remaining_hours set to 0.0
  • Tracker changed from Task to MNDeployment
  • Start date deleted (2013-01-30)

#2 Updated by John Cobb almost 12 years ago

  • Due date set to 2013-07-31
  • Target version set to Deploy by end of Y4Q4
  • Start date set to 2013-01-30

#3 Updated by Matthew Jones almost 12 years ago

  • Due date changed from 2013-07-31 to 2014-01-31
  • Target version changed from Deploy by end of Y4Q4 to Deploy by end of Y5Q2

#4 Updated by Laura Moyers over 11 years ago

  • Longitude set to -79.04
  • Latitude set to 35.91

#5 Updated by Matthew Jones about 11 years ago

Lisa Stillwell from RENCI contacted me about implementing DataONE API support for iRODS. She has been given this task on their end, and wanted an overview. We met via telephone for about 90 minutes on 8/23/2013 to discuss the process. I gave her a brief overview of the DataONE MN API and discussed the process of developing a software stack. We also reviewed the issues surrounding PIDs, SIDs, immutability, logging, and other potential issues. I sent her an email with information on how to get started on development, including where to get documentation on libclient, how to reach us on IRC and the developers list, etc. I offered that we are more than happy to help with any issues that arise.

#6 Updated by Laura Moyers about 11 years ago

  • Software stack set to iRODS

#7 Updated by Bruce Wilson about 11 years ago

  • Status changed from New to Ready
  • MN Tier set to Tier 1

#8 Updated by Bruce Wilson about 11 years ago

  • Due date changed from 2014-01-31 to 2014-04-30
  • Target version changed from Deploy by end of Y5Q2 to Deploy by end of Y5Q3

Based on current progress, I'm moving the target for this out to Q3. Based on current progress, anticipating implementation after January seems most likely.

#9 Updated by Bruce Wilson almost 11 years ago

  • Due date changed from 2014-04-30 to 2014-07-31
  • Target version changed from Deploy by end of Y5Q3 to Deploy by end of Y5Q4

#10 Updated by Bruce Wilson over 10 years ago

Corresponded with Lisa Stillwell. Making progress. She's assembling questions for next steps.

#11 Updated by Laura Moyers over 10 years ago

  • Target version changed from Deploy by end of Y5Q4 to Deploy by end of Y1Q1
  • Due date changed from 2014-07-31 to 2014-10-31

#12 Updated by Laura Moyers almost 10 years ago

  • Target version changed from Deploy by end of Y1Q1 to Deploy by end of Y1Q3

#13 Updated by Laura Moyers over 9 years ago

DFC POC is Chris Lenhardt (clenhardt@renci.org).

#14 Updated by Laura Moyers over 9 years ago

  • Target version changed from Deploy by end of Y1Q3 to Deploy by end of Y1Q4

#15 Updated by Laura Moyers over 9 years ago

  • NodeIdentifier set to urn:node:DFC

#16 Updated by Laura Moyers about 9 years ago

  • Target version changed from Deploy by end of Y1Q4 to Deploy by end of Y2Q1

#17 Updated by Laura Moyers almost 9 years ago

  • Target version changed from Deploy by end of Y2Q1 to Deploy by end of Y2Q2

#18 Updated by Laura Moyers over 8 years ago

  • Base URL set to http://datafed.org/
  • MN Description set to The DataNet Federation Consortium (DFC) Hydro-NEXRAD rainfall accumulation data for the Carolinas, Maryland, and Virginia uses Hydro-NEXRAD algorithms and NEXRAD data from the NOAA National Centers for Environmental Information (NCEI) to provide spatial datasets that estimate rainfall accumulation at 15-minute time intervals.

Added short MN description and MN URL.

#19 Updated by Laura Moyers over 8 years ago

  • Status changed from Ready to Testing
  • % Done changed from 55 to 50

#20 Updated by Laura Moyers over 8 years ago

  • Target version changed from Deploy by end of Y2Q2 to Deploy by end of Y2Q3

#21 Updated by Laura Moyers over 8 years ago

  • Target version changed from Deploy by end of Y2Q3 to Deploy by end of Y2Q4

#22 Updated by Laura Moyers about 8 years ago

  • Target version changed from Deploy by end of Y2Q4 to Deploy by end of Y3Q1

#23 Updated by Laura Moyers over 7 years ago

  • % Done changed from 50 to 100
  • Target version deleted (Deploy by end of Y3Q1)
  • Status changed from Testing to Closed

Development activities suspended. Word from Lisa Stillwell 7 Feb 2017, there will not be a DFC Member Node. The work that Lisa has done so far on the iRODS MN will be leveraged at CyVerse for their iRODS MN implementation.

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)