Task #4034: (Waiting for) Resolve policy and MN description questions - Member Nodes - DataONE Tasks

Task #4034

MNDeployment #3531: Gulf of Alaska Data Portal

(Waiting for) Resolve policy and MN description questions

Added by Laura Moyers over 10 years ago. Updated about 10 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Matthew Jones

Target version:

Operational

Start date:

2013-10-03

Due date:

2013-10-16

% Done:

100%

Estimated time:

0.00 h

Story Points:

Sprint:

Description

Collect information for MN Description document for Laura, to be included on DataONE MN webpage when Gulfwatch is in production

History

#1 Updated by Bruce Wilson over 10 years ago

Start date changed from 2013-10-03 to 2013-10-16
% Done changed from 0 to 20
Subject changed from (Waiting for) Create MN Description document to (Waiting for) Resolve policy and MN description questions

face to face meeting planned for 10/15. Expect to be able to address some remaining questions at that meeting or shortly thereafter.

#2 Updated by Bruce Wilson over 10 years ago

Due date set to 2013-10-16
Start date changed from 2013-10-16 to 2013-10-03

#3 Updated by Bruce Wilson over 10 years ago

Status changed from New to In Progress

#4 Updated by Matthew Jones over 10 years ago

Matt met on Oct 15 with the Gulf Watch Alaska team to discuss repository branding and replication with DataONE. The result is the decision to broaden the repository scope to the whole Gulf of Alaska, and include data from both Gulf Watch Alaska and other AOOS-supported projects. Consequently, the node name is being revised the 'Gulf of Alaska Data Portal'.

Matt developed the MN description document, which is currently in review by PIs, and should be ready early next week.

#5 Updated by Matthew Jones over 10 years ago

Target version changed from 315 to Deploy by end of Y5Q2

#6 Updated by Matthew Jones over 10 years ago

translation missing: en.field_remaining_hours set to 0.0
Status changed from In Progress to Closed

The MN description document has been reviewed and revised and is ready for submission to DataONE. Closing this ticket as the policy issues are resolved.