Minnesota Population Center
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.
#1 Updated by Laura Moyers about 9 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
#4 Updated by Bruce Wilson almost 9 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 almost 9 years ago
- Due date set to 2014-07-31
- Target version set to Deploy by end of Y5Q4
- Start date set to 2013-10-29
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 almost 9 years ago
- Software stack set to Slender Node
- Latitude set to 44.97
- Longitude set to -93.23
- MN Tier set to Tier 1
- OAI-PMH Stack set to TBD
- Base URL set to https://www.pop.umn.edu/index.php
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 almost 9 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.
#12 Updated by Laura Moyers almost 8 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.
#15 Updated by Laura Moyers over 7 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.