Activity
From 2014-02-28 to 2014-03-29
2014-03-14
- 15:52 Task #4458 (Closed): Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 15:52 Task #4457 (Closed): Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 15:52 Task #4456 (Closed): Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 15:52 Task #4455 (Closed): Final steps to go live
- The final steps required to bring the new Member Node online in the production environment.
- 15:52 Task #4454 (Closed): Production verifications
- All the items that were verified when the MN was in development and/or staging should be verified again for production.
- 15:52 Task #4453 (Closed): Mutual acceptance
- Change to "approved" in production.
- 15:52 Task #4452 (Closed): Update "Current MNs" webpage
- Update the Current MNs webpage with information about the new MN.
- 15:52 Task #4451 (Closed): Transition to production.
- Tasks related to moving the new MN into production.
- 15:52 Task #4450 (Closed): Resolve any synchronization related issues
- Resolve any issues found when reviewing the synchronization results.
- 15:52 Task #4449 (Closed): Review synchronization results
- After initial synchronization, review the representation of the data in DataONE and make sure that it accurately refl...
- 15:52 Task #4448 (Closed): Set up synchronization of the MN
- Enable synchronization for the MN.
- 15:52 Task #4447 (Closed): Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 15:52 Task #4446 (Closed): Register new Science Metadata formats
- All Science Objects on the MN should be of types that are known to the CN. Any unknown types should be registered.
- 15:52 Task #4445 (Closed): Synchronization
- TODO
- 15:52 Task #4444 (Closed): Log Record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 15:52 Task #4443 (Closed): Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 15:52 Task #4442 (Closed): Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 15:52 Task #4441 (Closed): Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 15:52 Task #4440 (Closed): Create Resource Maps for the data and metadata
- DataONE uses Resource Maps to associate Science Data with Science Metadata. Generate the required Resource Maps. Ther...
- 15:52 Task #4439 (Closed): Verify Science Metadata
- Review the MNs Science Metadata. This is to make sure that the metadata is complete, correctly formatted and is proce...
- 15:52 Task #4438 (Closed): Science Metadata is available in Solr index
- Verify that Science Metadata appears correct in the Solr index after synchronization.
- 15:52 Task #4437 (Closed): Verify that the Science Metadata is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded. For instance, EML , TIF...
- 15:52 Task #4436 (Closed): Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 15:52 Task #4435 (Closed): Verify that the Science Data is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 15:52 Task #4434 (Closed): Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 15:52 Task #4433 (Closed): Content Review
- Verify that all content on the MN appears correctly.
- 15:52 Task #4432 (Closed): Set up Node document
- Check that the Node document used during testing looks the same as it will in production.
- 15:52 Task #4431 (Closed): Verify successful installation of server side certificate
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 15:52 Task #4430 (Closed): Verify successful installation of client side certificate
- After notification from the MN that the client side certificate has been installed, verify that it is working correctly.
- 15:51 Task #4429 (Closed): Generate urn:node:KUBI client certificate for development.
- Create the test client certificate, and send it to CJ Grady, Aimee Stewart. When the certificate has been installed o...
- 15:51 Task #4428 (Closed): SSL Certificates for Development
- TODO
- 15:51 Task #4427 (Closed): SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 15:51 Task #4426 (Closed): Design, code and test a new MN implementation.
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 15:51 Task #4425 (Closed): Scope and plan implementation
- Select the MN Tier, determine which software stack to use, etc.
- 15:51 Task #4424 (Closed): Create MN description document
- Work with MN POC to create MN description document. Attach here when complete; store PDF in docs.dataone.org.
- 15:51 Task #4423 (Closed): Create DataONE identity
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 15:51 Task #4422 (Closed): Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 15:51 Task #4421 (Closed): Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 15:51 Task #4420 (Closed): Initial preparation
- TODO
- 15:51 MNDeployment #4419 (Closed): MNDeployment: urn:node:KUBI 2014-03-14_09:51:47
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 15:50 MNDeployment #4418 (Closed): MNDeployment: urn:node:KUBI 2014-03-14_09:50:37
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 03:15 MNDeployment #4417 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_21:15:33
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 03:14 MNDeployment #4416 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_21:14:40
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 03:13 MNDeployment #4415 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_21:13:22
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 02:18 MNDeployment #4414 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_20:18:14
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 01:54 MNDeployment #4413 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_19:54:24
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 01:44 Task #4412 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_19:44:58
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 01:05 Task #4411 (Closed): Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 01:05 Task #4410 (Closed): Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 01:05 Task #4409 (Closed): Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 01:05 Task #4408 (Closed): Final steps to go live
- The final steps required to bring the new Member Node online in the production environment.
- 01:05 Task #4407 (Closed): Production verifications
- All the items that were verified when the MN was in development and/or staging should be verified again for production.
- 01:05 Task #4406 (Closed): Mutual acceptance
- Change to "approved" in production.
- 01:05 Task #4405 (Closed): Update "Current MNs" webpage
- Update the Current MNs webpage with information about the new MN.
- 01:05 Task #4404 (Closed): Transition to production.
- Tasks related to moving the new MN into production.
- 01:05 Task #4403 (Closed): Resolve any synchronization related issues
- Resolve any issues found when reviewing the synchronization results.
- 01:05 Task #4402 (Closed): Review synchronization results
- After initial synchronization, review the representation of the data in DataONE and make sure that it accurately refl...
- 01:05 Task #4401 (Closed): Set up synchronization of the MN
- Enable synchronization for the MN.
- 01:05 Task #4400 (Closed): Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 01:05 Task #4399 (Closed): Register new Science Metadata formats
- All Science Objects on the MN should be of types that are known to the CN. Any unknown types should be registered.
- 01:05 Task #4398 (Closed): Synchronization
- TODO
- 01:05 Task #4397 (Closed): Log Record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 01:05 Task #4396 (Closed): Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 01:05 Task #4395 (Closed): Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 01:05 Task #4394 (Closed): Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 01:05 Task #4393 (Closed): Create Resource Maps for the data and metadata
- DataONE uses Resource Maps to associate Science Data with Science Metadata. Generate the required Resource Maps. Ther...
- 01:05 Task #4392 (Closed): Verify Science Metadata
- Review the MNs Science Metadata. This is to make sure that the metadata is complete, correctly formatted and is proce...
- 01:05 Task #4391 (Closed): Science Metadata is available in Solr index
- Verify that Science Metadata appears correct in the Solr index after synchronization.
- 01:05 Task #4390 (Closed): Verify that the Science Metadata is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded. For instance, EML , TIF...
- 01:05 Task #4389 (Closed): Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 01:05 Task #4388 (Closed): Verify that the Science Data is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 01:05 Task #4387 (Closed): Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 01:05 Task #4386 (Closed): Content Review
- Verify that all content on the MN appears correctly.
- 01:05 Task #4385 (Closed): Set up Node document
- Check that the Node document used during testing looks the same as it will in production.
- 01:05 Task #4384 (Closed): Verify successful installation of server side certificate
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 01:05 Task #4383 (Closed): Verify successful installation of client side certificate
- After notification from the MN that the client side certificate has been installed, verify that it is working correctly.
- 01:05 Task #4382 (Closed): Generate urn:node:KUBI client certificate for development.
- Create the test client certificate, and send it to CJ Grady, Aimee Stewart. When the certificate has been installed o...
- 01:05 Task #4380 (Closed): SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 01:05 Task #4381 (Closed): SSL Certificates for Development
- TODO
- 01:05 Task #4379 (Closed): Design, code and test a new MN implementation.
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 01:05 Task #4378 (Closed): Scope and plan implementation
- Select the MN Tier, determine which software stack to use, etc.
- 01:05 Task #4377 (Closed): Create MN description document
- Work with MN POC to create MN description document. Attach here when complete; store PDF in docs.dataone.org.
- 01:05 Task #4376 (Closed): Create DataONE identity
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 01:04 Task #4374 (Closed): Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 01:04 Task #4375 (Closed): Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 01:04 Task #4372 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_19:04:55
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 01:04 Task #4373 (Closed): Initial preparation
- TODO
- 01:01 Task #4369 (Closed): Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 01:01 Task #4370 (Closed): Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 01:01 Task #4368 (Closed): Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 01:01 Task #4367 (Closed): Final steps to go live
- The final steps required to bring the new Member Node online in the production environment.
- 01:01 Task #4366 (Closed): Production verifications
- All the items that were verified when the MN was in development and/or staging should be verified again for production.
- 01:01 Task #4364 (Closed): Update "Current MNs" webpage
- Update the Current MNs webpage with information about the new MN.
- 01:01 Task #4365 (Closed): Mutual acceptance
- Change to "approved" in production.
- 01:01 Task #4363 (Closed): Transition to production.
- Tasks related to moving the new MN into production.
- 01:01 Task #4362 (Closed): Resolve any synchronization related issues
- Resolve any issues found when reviewing the synchronization results.
- 01:01 Task #4361 (Closed): Review synchronization results
- After initial synchronization, review the representation of the data in DataONE and make sure that it accurately refl...
- 01:01 Task #4359 (Closed): Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 01:01 Task #4360 (Closed): Set up synchronization of the MN
- Enable synchronization for the MN.
- 01:01 Task #4358 (Closed): Register new Science Metadata formats
- All Science Objects on the MN should be of types that are known to the CN. Any unknown types should be registered.
- 01:01 Task #4357 (Closed): Synchronization
- TODO
- 01:01 Task #4355 (Closed): Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 01:01 Task #4356 (Closed): Log Record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 01:01 Task #4354 (Closed): Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 01:01 Task #4353 (Closed): Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 01:01 Task #4351 (Closed): Verify Science Metadata
- Review the MNs Science Metadata. This is to make sure that the metadata is complete, correctly formatted and is proce...
- 01:01 Task #4352 (Closed): Create Resource Maps for the data and metadata
- DataONE uses Resource Maps to associate Science Data with Science Metadata. Generate the required Resource Maps. Ther...
- 01:01 Task #4350 (Closed): Science Metadata is available in Solr index
- Verify that Science Metadata appears correct in the Solr index after synchronization.
- 01:01 Task #4349 (Closed): Verify that the Science Metadata is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded. For instance, EML , TIF...
- 01:01 Task #4347 (Closed): Verify that the Science Data is returned with the correct HTTP Content-Type
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 01:01 Task #4348 (Closed): Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 01:01 Task #4346 (Closed): Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 01:01 Task #4345 (Closed): Content Review
- Verify that all content on the MN appears correctly.
- 01:01 Task #4344 (Closed): Set up Node document
- Check that the Node document used during testing looks the same as it will in production.
- 01:01 Task #4343 (Closed): Verify successful installation of server side certificate
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 01:01 Task #4342 (Closed): Verify successful installation of client side certificate
- After notification from the MN that the client side certificate has been installed, verify that it is working correctly.
- 01:01 Task #4341 (Closed): Generate urn:node:KUBI client certificate for development.
- Create the test client certificate, and send it to CJ Grady, Aimee Stewart. When the certificate has been installed o...
- 01:01 Task #4340 (Closed): SSL Certificates for Development
- TODO
- 01:01 Task #4338 (Closed): Design, code and test a new MN implementation.
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 01:01 Task #4339 (Closed): SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 01:01 Task #4337 (Closed): Scope and plan implementation
- Select the MN Tier, determine which software stack to use, etc.
- 01:01 Task #4335 (Closed): Create DataONE identity
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 01:01 Task #4336 (Closed): Create MN description document
- Work with MN POC to create MN description document. Attach here when complete; store PDF in docs.dataone.org.
- 01:01 Task #4334 (Closed): Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 01:01 Task #4333 (Closed): Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 01:01 Task #4331 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_19:01:25
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 01:01 Task #4332 (Closed): Initial preparation
- TODO
2014-03-13
- 18:25 Task #4329 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_12:25:37
- This issue is to track deployment of Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:23 Task #4328 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_12:23:53
- This issue is to track deployment of Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:03 Task #4327 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_12:01:54
- This issue is to track deployment of Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:02 Task #4326 (Closed): MNDeployment: urn:node:KUBI 2014-03-13_12:00:35
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.ku.... - 05:29 Task #4314 (Closed): MNDeployment: urn:node:KUBI 2014-03-12_23:29:01
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm...
Also available in: Atom
