Project

General

Profile

MNDeployment #3708

Minnesota Population Center

Added by Rebecca Koskela over 11 years ago. Updated over 6 years ago.

Status:
Operational
Priority:
Normal
Assignee:
Laura Moyers
Target version:
Operational
Start date:
2013-10-15
Due date:
2013-11-04
% Done:

89%

Latitude:
44.97
Longitude:
-93.23
MN Description:
The Minnesota Population Center disseminates integrated census and survey data from the U.S. and around the world; spatial boundary data for U.S. and international administrative units; and global environmental data on topics including land use, land cover, and climate.
Base URL:
https://www.pop.umn.edu/index.php
NodeIdentifier:
urn:node:US_MPC
MN Tier:
Tier 4
Software stack:
Slender Node
MN_Date_Online:
2014-12-22
Name:
Logo URL:
Date Upcoming:
Date Deprecated:
Information URL:
Version:
Sprint:
Ongoing Operational

Description

The Minnesota Population Center would like to become a Member Node. The project director is also PI on the Terra Populus:A Global Population/Environment Data Network (TerraPop) DataNet.
The MN description form has been completed and is attached to this ticket.

Member_Node_Description_Form_MPC.docx (299 KB) Rebecca Koskela, 2013-04-04 18:56

Subtasks

Task #4089: Schedule follow-up meeting with MPC for NovemberClosedLaura Moyers

Task #4090: Establish technical contacts between CCIT and MPC folks; determine coredev primary POCClosedLaura Moyers

Task #4139: Touch base with MPC to see who to have in follow-up telecon in mid- to late-NovemberClosedBruce Wilson

Task #5530: MPC PROD: Generate client certificate for urn:node:MPCClosedChris Jones

Task #5909: MPC: PlanningClosed

Task #5910: MPC: Join DataONEClosed

Task #5911: MPC: Integrate MN representatives with communityClosed

Task #5912: MPC: Create DataONE identitiesClosed

Task #5913: MPC: Create MN description documentClosed

Task #5914: MPC: Scope the implementationClosed

Task #5915: MPC: Plan the implementationClosed

Task #5916: MPC: DevelopingClosed

Task #5917: MPC: Design, code and component test a new MN implementationClosed

Task #5918: MPC: Local TestingClosed

Task #5919: MPC: Verify that MN passes the Web TesterClosed

Task #5920: MPC: Verify that MN passes the Replication TesterClosed

Task #5921: MPC: TestingClosed

Task #5922: MPC: Registration in environmentClosed

Task #5923: MPC: Register new Science Metadata formatsClosed

Task #5924: MPC: SSL CertificatesClosed

Task #5925: MPC: Generate client certificate.ClosedChris Jones

Task #5926: MPC: Verify successful installation of client side certificateClosedChris Jones

Task #5927: MPC: Verify successful installation of server side certificateClosedChris Jones

Task #5928: MPC: Register MNClosed

Task #5929: MPC: Set up Node documentClosedChris Jones

Task #5930: MPC: Set the node status to approved (start synchronization)Closed

Task #5931: MPC: SynchronizationRejected

Task #5932: MPC: Set up synchronization of the MNRejected

Task #5933: MPC: Content ReviewClosedChris Jones

Task #5934: MPC: Verify Science DataClosedChris Jones

Task #5935: MPC: Verify Science Data contentClosedChris Jones

Task #5936: MPC: Verify that the Science Data is returned with the correct HTTP Content-TypeClosedChris Jones

Task #5937: MPC: Verify Science MetadataClosedChris Jones

Task #5938: MPC: Verify Science Metadata contentClosedChris Jones

Task #5939: MPC: Verify Science Metadata is returned with the correct HTTP Content-TypeClosedChris Jones

Task #5940: MPC: Verify that the Science Metadata is correctly processed by CNsClosedChris Jones

Task #5941: MPC: Verify Resource MapsClosedChris Jones

Task #5942: MPC: Verify Resource Map contentClosedChris Jones

Task #5943: MPC: Verify Resource Map is returned with the correct HTTP Content-TypeClosedChris Jones

Task #5944: MPC: Verify that Resource Maps are correctly processed by CNs.ClosedChris Jones

Task #5949: MPC: Replication testing (if Tier 4)Closed

Task #5978: MPC: Transition to productionClosed

Task #5979: MPC: Mutual acceptanceClosed

Task #5980: MPC: Verify content available for Current MNs web pageClosed

Task #5981: MPC: Create legal documentsClosed

Task #5982: MPC: Create news itemClosed

Task #5983: MPC: Formal announcementClosed

Task #8258: (MPC) unable to connect to MNClosedAmy Forrester

Task #8668: MPC- upgrade GMN version 1.2.10 to 3.0.4NewRoger Dahl

Related issues

Related to Infrastructure - Story #4172: Support for Data Documentation Initiative (DDI) Metadata Rejected
Blocked by Infrastructure - Story #4088: Design and schedule Slender Node based on OAI-PMH harvest Closed

History

#1 Updated by Laura Moyers over 11 years ago

7/26/13 MN Wranglers meeting: Rebecca spoke to Steve Ruggles @ Minnesota Population Center. They WILL need logins (user authentication before download of data). Looking at later in PY5. Rebecca to find out what kind of authentication they are using now; answer technical questions with Cathy Fitch/Wendy Thomas

#2 Updated by Laura Moyers about 11 years ago

  • Status changed from New to Planning

In a meeting with MPC on 9/30/13, we made plans to put MPC technical folks in contact with D1 CCIT folks. Follow-up meeting early November.

#3 Updated by John Cobb about 11 years ago

  • Assignee changed from John Cobb to Bruce Wilson

#4 Updated by Bruce Wilson about 11 years ago

Notes from 9/30/13 telecon are at http://epad.dataone.org/MPC-and-DataONE. They have their own internal software (includes using ESRI tools). They're interested in initially publishing metadata to DataONE. A clean way of harvesting metadata is useful. SlenderNode (OAI-PMH harvester) could be a very relevant option for MPC, as this would let them stand up OAI-PMH and make the data available to multiple projects, not just DataONE.

#5 Updated by Bruce Wilson about 11 years ago

  • Target version set to Deploy by end of Y5Q4
  • Start date set to 2013-10-29
  • Due date set to 2014-07-31

epad at http://epad.dataone.org/MPC-and-DataONE updated with notes from today's discussion. Key issue will be how to get first the metadata from MPC to DataONE. MPC also needs to address how they want to handle identifiers for data and metadata. Tentatively scheduling for end of year 5 based on the current level of effort anticipated and technical questions that need to be resolved.

#6 Updated by Bruce Wilson about 11 years ago

  • OAI-PMH Stack set to TBD
  • Latitude set to 44.97
  • Longitude set to -93.23
  • Base URL set to https://www.pop.umn.edu/index.php
  • MN Tier set to Tier 1
  • Software stack set to Slender Node

Good discussion this week via email; follow-up telecon planned. The OAI-PMH approach with the (planned) slender node is the most desirable option for MPC at this point. That would make them a primarily metadata member node. They do understand and are interested in making data more directly available. A key issue is that they do data set assembly on the fly, using a mixture of some data in databases and some in files. They are also looking at an overall restructure of several of their services. For metadata, key challenges are agreeing on a metadata format (which DataONE may need to add) and working how how they want to serve their metadata, which is all in a database at this point.

#7 Updated by Bruce Wilson about 11 years ago

Met with MPC staff 2013-11-11; notes on epad at http://epad.dataone.org/MPC-and-DataONE.

MPC to work on determining which stack to use for OAI-PMH; DataONE needs to work on the Slender Node implementation to consume OAI-PMH (Dublin Core). We do need to advise MPC of any limitations we place on Dublin Core and it would be useful to note what extensions we support. Note that their metadata will link to a landing page. Data is not available on-demand, by and large.

#8 Updated by Laura Moyers over 10 years ago

  • Status changed from Planning to Testing

#9 Updated by Laura Moyers over 10 years ago

  • NodeIdentifier set to urn:node:MPC

#10 Updated by Laura Moyers over 10 years ago

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

#11 Updated by Laura Moyers about 10 years ago

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

#12 Updated by Laura Moyers about 10 years ago

  • NodeIdentifier changed from urn:node:MPC to urn:node:US_MPC

In their nodeID, MPC wants to mirror us.mpc, the identifier registered with the DDI Alliance. Use of "." in nodeIDs is problematic, hence the use of "_" to retain a country_node format.

Also, see the updated Member Node Description Document on ticket https://redmine.dataone.org/issues/5913; the MNDD attached here is the original and is obsolete.

#13 Updated by Laura Moyers almost 10 years ago

  • Due date changed from 2014-10-31 to 2013-10-15
  • Status changed from Testing to Operational
  • Target version changed from Deploy by end of NCTE to Operational
  • MN_Date_Online set to 2014-12-22

#14 Updated by Laura Moyers over 9 years ago

  • Assignee changed from Bruce Wilson to Laura Moyers

#15 Updated by Laura Moyers over 9 years ago

  • MN Description set to The Minnesota Population Center disseminates integrated census and survey data from the U.S. and around the world; spatial boundary data for U.S. and international administrative units; and global environmental data on topics including land use, land cover, and climate.

#16 Updated by Laura Moyers over 8 years ago

  • MN Tier changed from Tier 1 to Tier 4

MPC is a GMN (needs to be updated).

#17 Updated by Dave Vieglais almost 7 years ago

  • Sprint set to Ongoing Operational

#18 Updated by Monica Ihli almost 7 years ago

  • Subject changed from Minnesota Population Center to Minnesota Population Center

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 14.8 MB)