Activity
From 2014-03-23 to 2014-04-21
2014-04-16
- 02:27 Task #5116 (Rejected): KUBI PROD: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:27 Task #5115 (Rejected): KUBI PROD: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:27 Task #5114 (Rejected): KUBI PROD: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:27 Task #5113 (Rejected): KUBI PROD: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:26 Task #5112 (Rejected): KUBI PROD: Mutual acceptance
- Change to "approved" in production.
- 02:26 Task #5111 (Rejected): KUBI PROD: Transition to production
- Tasks related to moving the new MN into production.
- 02:26 Task #5110 (Rejected): KUBI PROD: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:26 Task #5109 (Rejected): KUBI PROD: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:26 Task #5108 (Rejected): KUBI PROD: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:26 Task #5107 (Rejected): KUBI PROD: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:26 Task #5106 (Rejected): KUBI PROD: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:26 Task #5105 (Rejected): KUBI PROD: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:26 Task #5104 (Rejected): KUBI PROD: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:26 Task #5103 (Rejected): KUBI PROD: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:26 Task #5102 (Rejected): KUBI PROD: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:26 Task #5101 (Closed): KUBI PROD: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:26 Task #5100 (Closed): KUBI PROD: Verify Science Metadata is returned with the correct HTTP Content...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:26 Task #5099 (Closed): KUBI PROD: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:26 Task #5098 (Closed): KUBI PROD: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:26 Task #5097 (Closed): KUBI PROD: Verify that the Science Data is returned with the correct HTTP Co...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:26 Task #5096 (Closed): KUBI PROD: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:26 Task #5095 (Closed): KUBI PROD: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:26 Task #5094 (Closed): KUBI PROD: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:26 Task #5093 (Closed): KUBI PROD: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:26 Task #5092 (Closed): KUBI PROD: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:26 Task #5091 (Closed): KUBI PROD: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:26 Task #5090 (Closed): KUBI PROD: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:26 Task #5089 (Closed): KUBI PROD: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:26 Task #5088 (Closed): KUBI PROD: 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.
- 02:26 Task #5087 (Closed): KUBI PROD: 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.
- 02:26 Task #5086 (Closed): KUBI PROD: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:26 Task #5085 (Closed): KUBI PROD: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:26 Task #5084 (Closed): KUBI PROD: 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.
- 02:26 Task #5083 (Closed): KUBI PROD: Registration in environment
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:26 Task #5082 (Closed): KUBI STAGE: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:26 Task #5081 (Closed): KUBI STAGE: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:26 Task #5080 (Closed): KUBI STAGE: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:26 Task #5079 (Closed): KUBI STAGE: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:26 Task #5078 (Closed): KUBI STAGE: Mutual acceptance
- Change to "approved" in production.
- 02:26 Task #5077 (Closed): KUBI STAGE: Transition to production
- Tasks related to moving the new MN into production.
- 02:26 Task #5076 (Closed): KUBI STAGE: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:25 Task #5075 (Closed): KUBI STAGE: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:25 Task #5074 (Closed): KUBI STAGE: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:25 Task #5073 (Closed): KUBI STAGE: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:25 Task #5072 (Closed): KUBI STAGE: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:25 Task #5071 (Closed): KUBI STAGE: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:25 Task #5070 (Closed): KUBI STAGE: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:25 Task #5069 (Closed): KUBI STAGE: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:25 Task #5068 (Closed): KUBI STAGE: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:25 Task #5067 (Closed): KUBI STAGE: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:25 Task #5066 (Closed): KUBI STAGE: Verify Science Metadata is returned with the correct HTTP Conten...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:25 Task #5065 (Closed): KUBI STAGE: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:25 Task #5064 (Closed): KUBI STAGE: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:25 Task #5063 (Closed): KUBI STAGE: Verify that the Science Data is returned with the correct HTTP C...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:25 Task #5062 (Closed): KUBI STAGE: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:25 Task #5061 (Closed): KUBI STAGE: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:25 Task #5060 (Closed): KUBI STAGE: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:25 Task #5059 (Closed): KUBI STAGE: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:25 Task #5058 (Closed): KUBI STAGE: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:25 Task #5057 (Closed): KUBI STAGE: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:25 Task #5056 (Closed): KUBI STAGE: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:25 Task #5055 (Closed): KUBI STAGE: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:25 Task #5054 (Closed): KUBI STAGE: 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.
- 02:25 Task #5053 (Closed): KUBI STAGE: 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.
- 02:25 Task #5052 (Closed): KUBI STAGE: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:25 Task #5051 (Closed): KUBI STAGE: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:25 Task #5050 (Closed): KUBI STAGE: 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.
- 02:25 Task #5049 (Closed): KUBI STAGE: Registration in environment
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:25 Task #5048 (Closed): KUBI DEV: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:25 Task #5047 (Closed): KUBI DEV: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:25 Task #5046 (Closed): KUBI DEV: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:25 Task #5045 (Closed): KUBI DEV: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:25 Task #5044 (Closed): KUBI DEV: Mutual acceptance
- Change to "approved" in production.
- 02:25 Task #5043 (Closed): KUBI DEV: Transition to production
- Tasks related to moving the new MN into production.
- 02:25 Task #5042 (Closed): KUBI DEV: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:25 Task #5041 (Closed): KUBI DEV: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:25 Task #5040 (Closed): KUBI DEV: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:25 Task #5039 (Closed): KUBI DEV: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:24 Task #5038 (Closed): KUBI DEV: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:24 Task #5037 (Closed): KUBI DEV: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:24 Task #5036 (Closed): KUBI DEV: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:24 Task #5035 (Closed): KUBI DEV: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:24 Task #5034 (Closed): KUBI DEV: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:24 Task #5033 (Closed): KUBI DEV: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:24 Task #5032 (Closed): KUBI DEV: Verify Science Metadata is returned with the correct HTTP Content-...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:24 Task #5031 (Closed): KUBI DEV: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:24 Task #5030 (Closed): KUBI DEV: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:24 Task #5029 (Closed): KUBI DEV: Verify that the Science Data is returned with the correct HTTP Con...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:24 Task #5028 (Closed): KUBI DEV: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:24 Task #5027 (Closed): KUBI DEV: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:24 Task #5026 (Closed): KUBI DEV: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:24 Task #5025 (Closed): KUBI DEV: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:24 Task #5024 (Closed): KUBI DEV: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:24 Task #5023 (Closed): KUBI DEV: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:24 Task #5022 (Closed): KUBI DEV: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:24 Task #5021 (Closed): KUBI DEV: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:24 Task #5020 (Closed): KUBI DEV: 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.
- 02:24 Task #5019 (Closed): KUBI DEV: 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.
- 02:24 Task #5018 (Closed): KUBI DEV: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:24 Task #5017 (Closed): KUBI DEV: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:24 Task #5016 (Closed): KUBI DEV: 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.
- 02:24 Task #5015 (Closed): KUBI DEV: Registration in environment
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5014 (Closed): KUBI: Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5013 (Closed): KUBI: Verify that MN passes the Replication Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5012 (Closed): KUBI: Verify that MN passes the Web Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5011 (Closed): KUBI: Local Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5010 (Closed): KUBI: Design, code and component test a new MN implementation
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:24 Task #5009 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 02:24 Task #5008 (Closed): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 02:24 Task #5007 (Closed): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 02:24 Task #5006 (Closed): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 02:24 Task #5005 (Closed): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 02:24 Task #5004 (Closed): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 02:24 Task #5003 (Closed): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:24 Task #5002 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:24 Task #5001 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:24 Task #5000 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 02:24 Task #4999 (Closed): KUBI: Initial Preparation
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:24 MNDeployment #4998 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_20:24:02
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:24 Task #4997 (Closed): KUBI PROD: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:23 Task #4996 (Closed): KUBI PROD: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:23 Task #4995 (Closed): KUBI PROD: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:23 Task #4994 (Closed): KUBI PROD: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:23 Task #4993 (Closed): KUBI PROD: Mutual acceptance
- Change to "approved" in production.
- 02:23 Task #4992 (Closed): KUBI PROD: Transition to production
- Tasks related to moving the new MN into production.
- 02:23 Task #4991 (Closed): KUBI PROD: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:23 Task #4990 (Closed): KUBI PROD: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:23 Task #4989 (Closed): KUBI PROD: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:23 Task #4988 (Closed): KUBI PROD: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:23 Task #4987 (Closed): KUBI PROD: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:23 Task #4986 (Closed): KUBI PROD: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:23 Task #4985 (Closed): KUBI PROD: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:23 Task #4984 (Closed): KUBI PROD: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:23 Task #4983 (Closed): KUBI PROD: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:23 Task #4982 (Closed): KUBI PROD: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:23 Task #4981 (Closed): KUBI PROD: Verify Science Metadata is returned with the correct HTTP Content...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:23 Task #4980 (Closed): KUBI PROD: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:23 Task #4979 (Closed): KUBI PROD: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:23 Task #4978 (Closed): KUBI PROD: Verify that the Science Data is returned with the correct HTTP Co...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:23 Task #4977 (Closed): KUBI PROD: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:23 Task #4976 (Closed): KUBI PROD: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:23 Task #4975 (Closed): KUBI PROD: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:23 Task #4974 (Closed): KUBI PROD: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:23 Task #4973 (Closed): KUBI PROD: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:23 Task #4972 (Closed): KUBI PROD: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:23 Task #4971 (Closed): KUBI PROD: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:23 Task #4970 (Closed): KUBI PROD: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:23 Task #4969 (Closed): KUBI PROD: 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.
- 02:23 Task #4968 (Closed): KUBI PROD: 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.
- 02:23 Task #4967 (Closed): KUBI PROD: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:23 Task #4966 (Closed): KUBI PROD: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:23 Task #4965 (Closed): KUBI PROD: 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.
- 02:23 Task #4964 (Closed): KUBI PROD: Registration in environment
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:23 Task #4963 (Closed): KUBI STAGE: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:23 Task #4962 (Closed): KUBI STAGE: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:22 Task #4961 (Closed): KUBI STAGE: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:22 Task #4960 (Closed): KUBI STAGE: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:22 Task #4959 (Closed): KUBI STAGE: Mutual acceptance
- Change to "approved" in production.
- 02:22 Task #4958 (Closed): KUBI STAGE: Transition to production
- Tasks related to moving the new MN into production.
- 02:22 Task #4957 (Closed): KUBI STAGE: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:22 Task #4956 (Closed): KUBI STAGE: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:22 Task #4955 (Closed): KUBI STAGE: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:22 Task #4954 (Closed): KUBI STAGE: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:22 Task #4953 (Closed): KUBI STAGE: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:22 Task #4952 (Closed): KUBI STAGE: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:22 Task #4951 (Closed): KUBI STAGE: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:22 Task #4950 (Closed): KUBI STAGE: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:22 Task #4949 (Closed): KUBI STAGE: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:22 Task #4948 (Closed): KUBI STAGE: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:22 Task #4947 (Closed): KUBI STAGE: Verify Science Metadata is returned with the correct HTTP Conten...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:22 Task #4946 (Closed): KUBI STAGE: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:22 Task #4945 (Closed): KUBI STAGE: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:22 Task #4944 (Closed): KUBI STAGE: Verify that the Science Data is returned with the correct HTTP C...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:22 Task #4943 (Closed): KUBI STAGE: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:22 Task #4942 (Closed): KUBI STAGE: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:22 Task #4941 (Closed): KUBI STAGE: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:22 Task #4940 (Closed): KUBI STAGE: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:22 Task #4939 (Closed): KUBI STAGE: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:22 Task #4938 (Closed): KUBI STAGE: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:22 Task #4937 (Closed): KUBI STAGE: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:22 Task #4936 (Closed): KUBI STAGE: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:22 Task #4935 (Closed): KUBI STAGE: 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.
- 02:22 Task #4934 (Closed): KUBI STAGE: 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.
- 02:22 Task #4933 (Closed): KUBI STAGE: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:22 Task #4932 (Closed): KUBI STAGE: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:22 Task #4931 (Closed): KUBI STAGE: 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.
- 02:22 Task #4930 (Closed): KUBI STAGE: Registration in environment
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:22 Task #4929 (Closed): KUBI DEV: Formal announcement
- Announce the new MN on DataONE website, press release, ListServ, Twitter, etc.
- 02:22 Task #4928 (Closed): KUBI DEV: Create news item
- Draft news item for public release and coordinate with MN for any announcements they wish to do from their perspective
- 02:22 Task #4927 (Closed): KUBI DEV: Create legal documents
- Legal language (any partnership agreements, MOUs, etc.)
- 02:21 Task #4926 (Closed): KUBI DEV: Verify content available for Current MNs web page
- Update the Current MNs webpage with information about the new MN.
- 02:21 Task #4925 (Closed): KUBI DEV: Mutual acceptance
- Change to "approved" in production.
- 02:21 Task #4924 (Closed): KUBI DEV: Transition to production
- Tasks related to moving the new MN into production.
- 02:21 Task #4923 (Closed): KUBI DEV: Replication testing (if Tier 4)
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:21 Task #4922 (Closed): KUBI DEV: Log record access
- Verify that Log Records can be accessed only as allowed by the MN policy.
- 02:21 Task #4921 (Closed): KUBI DEV: Science Metadata access
- Verify that Science Metadata has the correct read, write and updatePermissions permissions.
Verify that Science Meta... - 02:21 Task #4920 (Closed): KUBI DEV: Science Data access
- Verify that Science Data has the correct read, write and updatePermissions permissions.
Verify that Science Data can... - 02:21 Task #4919 (Closed): KUBI DEV: Authentication and Authorization
- Tasks related to ensuring that permissions are correct on Science Data, Science Metadata and log records and that the...
- 02:21 Task #4918 (Closed): KUBI DEV: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:21 Task #4917 (Closed): KUBI DEV: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:21 Task #4916 (Closed): KUBI DEV: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:21 Task #4915 (Closed): KUBI DEV: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:21 Task #4914 (Closed): KUBI DEV: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:21 Task #4913 (Closed): KUBI DEV: Verify Science Metadata is returned with the correct HTTP Content-...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:21 Task #4912 (Closed): KUBI DEV: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:21 Task #4911 (Closed): KUBI DEV: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:21 Task #4910 (Closed): KUBI DEV: Verify that the Science Data is returned with the correct HTTP Con...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:21 Task #4909 (Closed): KUBI DEV: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:21 Task #4908 (Closed): KUBI DEV: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:21 Task #4907 (Closed): KUBI DEV: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:21 Task #4906 (Closed): KUBI DEV: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:21 Task #4905 (Closed): KUBI DEV: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:21 Task #4904 (Closed): KUBI DEV: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:21 Task #4903 (Closed): KUBI DEV: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:21 Task #4902 (Closed): KUBI DEV: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:21 Task #4901 (Closed): KUBI DEV: 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.
- 02:21 Task #4900 (Closed): KUBI DEV: 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.
- 02:21 Task #4899 (Closed): KUBI DEV: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:21 Task #4898 (Closed): KUBI DEV: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:21 Task #4897 (Closed): KUBI DEV: 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.
- 02:21 Task #4896 (Closed): KUBI DEV: Registration in environment
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4895 (Closed): KUBI: Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4894 (Closed): KUBI: Verify that MN passes the Replication Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4893 (Closed): KUBI: Verify that MN passes the Web Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4892 (Closed): KUBI: Local Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4891 (Closed): KUBI: Design, code and component test a new MN implementation
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:21 Task #4890 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 02:20 Task #4889 (Closed): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 02:20 Task #4888 (Closed): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 02:20 Task #4887 (Closed): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 02:20 Task #4886 (Closed): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 02:20 Task #4885 (Closed): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 02:20 Task #4884 (Closed): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:20 Task #4883 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:20 Task #4882 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:20 Task #4881 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 02:20 Task #4880 (Closed): KUBI: Initial Preparation
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:20 MNDeployment #4879 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_20:20:47
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:19 Task #4878 (Closed): KUBI DEV: Verify that Resource Maps are correctly processed by CNs.
- Verify that CNs are able to process the Resource Maps.
Successfully processed Resource Maps will cause objects to be... - 02:19 Task #4877 (Closed): KUBI DEV: Verify Resource Map is returned with the correct HTTP Content-Type
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:19 Task #4876 (Closed): KUBI DEV: Verify Resource Map content
- Verify that Resource Maps are complete, correctly formatted and represent the intended associations.
- 02:19 Task #4875 (Closed): KUBI DEV: Verify Resource Maps
- DataONE uses Resource Maps to create associations between objects.
- 02:19 Task #4874 (Closed): KUBI DEV: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:19 Task #4873 (Closed): KUBI DEV: Verify Science Metadata is returned with the correct HTTP Content-...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:19 Task #4872 (Closed): KUBI DEV: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:19 Task #4871 (Closed): KUBI DEV: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:19 Task #4870 (Closed): KUBI DEV: Verify that the Science Data is returned with the correct HTTP Con...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:19 Task #4869 (Closed): KUBI DEV: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:19 Task #4868 (Closed): KUBI DEV: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:19 Task #4867 (Closed): KUBI DEV: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:19 Task #4866 (Closed): KUBI DEV: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:19 Task #4865 (Closed): KUBI DEV: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:19 Task #4864 (Closed): KUBI DEV: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:19 Task #4863 (Closed): KUBI DEV: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:19 Task #4862 (Closed): KUBI DEV: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:19 Task #4861 (Closed): KUBI DEV: 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.
- 02:19 Task #4860 (Closed): KUBI DEV: 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.
- 02:19 Task #4859 (Closed): KUBI DEV: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:19 Task #4858 (Closed): KUBI DEV: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:19 Task #4857 (Closed): KUBI DEV: 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.
- 02:19 Task #4856 (Closed): KUBI DEV: Registration in environment
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4855 (Closed): KUBI: Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4854 (Closed): KUBI: Verify that MN passes the Replication Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4853 (Closed): KUBI: Verify that MN passes the Web Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4852 (Closed): KUBI: Local Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4851 (Closed): KUBI: Design, code and component test a new MN implementation
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:19 Task #4850 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 02:18 Task #4849 (Closed): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 02:18 Task #4848 (Closed): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 02:18 Task #4847 (Closed): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 02:18 Task #4846 (Closed): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 02:18 Task #4845 (Closed): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 02:18 Task #4844 (Closed): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:18 Task #4843 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:18 Task #4842 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:18 Task #4841 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 02:18 Task #4840 (Closed): KUBI: Initial Preparation
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:18 MNDeployment #4839 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_20:18:46
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:11 Task #4838 (Closed): KUBI DEV: Verify Resource Maps
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:11 Task #4837 (Closed): KUBI DEV: Verify that the Science Metadata is correctly processed by CNs
- Verify that CNs are able to index any supported Science Metadata objects.
Successfully indexed objects appear in the... - 02:11 Task #4836 (Closed): KUBI DEV: Verify Science Metadata is returned with the correct HTTP Content-...
- The HTTP Content-Type header should correctly represent the Science Metadata when downloaded.
For instance, EML , TI... - 02:11 Task #4835 (Closed): KUBI DEV: Verify Science Metadata content
- Verify that the Science Metadata is present, complete and correctly formatted.
I.e., can be opened in the applicatio... - 02:11 Task #4834 (Closed): KUBI DEV: Verify Science Metadata
- Tasks related to ensuring that the Science Metadata is correctly represented on the MN.
- 02:11 Task #4833 (Closed): KUBI DEV: Verify that the Science Data is returned with the correct HTTP Con...
- The HTTP Content-Type header should correctly represent the Science Data when downloaded. For instance, EML , TIFF, a...
- 02:11 Task #4832 (Closed): KUBI DEV: Verify Science Data content
- Verify that the Science Data is present, complete and correctly formatted. I.e., can be opened in the applications th...
- 02:11 Task #4831 (Closed): KUBI DEV: Verify Science Data
- Tasks related to ensuring that the Science Data is correctly represented on the MN.
- 02:11 Task #4830 (Closed): KUBI DEV: Content Review
- Verify that all content on the MN appears correctly and is successfully processed by CNs.
- 02:11 Task #4829 (Closed): KUBI DEV: Set up synchronization of the MN
- Enable synchronization for the MN.
- 02:11 Task #4828 (Closed): KUBI DEV: Synchronization
- Setting the MN up for synchronization and verifying that it works correctly.
- 02:11 Task #4827 (Closed): KUBI DEV: Set the node status to approved (start synchronization)
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:11 Task #4826 (Closed): KUBI DEV: Set up Node document
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:11 Task #4825 (Closed): KUBI DEV: Register MN
- After notification from the MN that the server side certificate has been installed, verify that it is working correctly.
- 02:11 Task #4824 (Closed): KUBI DEV: 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.
- 02:11 Task #4823 (Closed): KUBI DEV: 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.
- 02:11 Task #4822 (Closed): KUBI DEV: Generate client certificate for urn:node:KUBI
- Create the client certificate and send it to CJ Grady, Aimee Stewart. When the certificate has been installed on the ...
- 02:11 Task #4821 (Closed): KUBI DEV: SSL Certificates
- Set up and verify correct operation of SSL client and server side certificates
- 02:11 Task #4820 (Closed): KUBI DEV: 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.
- 02:11 Task #4819 (Closed): KUBI DEV: Registration in environment
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:11 Task #4818 (Closed): KUBI: Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:11 Task #4817 (Closed): KUBI: Verify that MN passes the Replication Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:11 Task #4816 (Closed): KUBI: Verify that MN passes the Web Tester
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:10 Task #4815 (Closed): KUBI: Local Testing
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:10 Task #4814 (Closed): KUBI: Design, code and component test a new MN implementation
- If a new MN is being developed from scratch, tickets in this section will track progress.
- 02:10 Task #4813 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 02:10 Task #4812 (Closed): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 02:10 Task #4811 (Closed): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 02:10 Task #4810 (Closed): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 02:10 Task #4809 (Closed): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 02:10 Task #4808 (Closed): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 02:10 Task #4807 (Closed): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:10 Task #4806 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:10 Task #4805 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 02:10 Task #4804 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 02:10 MNDeployment #4802 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_20:10:42
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:10 Task #4803 (Closed): KUBI: Initial Preparation
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone... - 02:10 MNDeployment #4801 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_20:10:18
- This story is to track deployment of a new Member Node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone...
2014-04-15
- 19:11 MNDeployment #4798 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_13:11:43
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 19:10 MNDeployment #4797 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_13:10:42
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 19:09 MNDeployment #4796 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_13:09:50
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 19:06 MNDeployment #4795 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_13:06:48
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:50 MNDeployment #4794 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_12:50:45
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:47 MNDeployment #4793 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_12:47:31
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:47 MNDeployment #4792 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_12:47:05
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:45 MNDeployment #4791 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_12:45:22
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 18:42 MNDeployment #4790 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-15_12:42:20
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:11 MNDeployment #4787 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:11:17
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:11 MNDeployment #4786 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:11:06
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:11 MNDeployment #4785 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:11:02
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:09 MNDeployment #4784 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:09:45
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:06 MNDeployment #4783 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:06:08
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:04 MNDeployment #4782 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:04:46
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:04 Task #4780 (Closed): KUBI: Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:04 Task #4781 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 05:04 MNDeployment #4779 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:04:34
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:03 Task #4778 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 05:03 Task #4777 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 05:03 Task #4776 (Closed): KUBI: Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 05:03 MNDeployment #4775 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_23:03:41
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 04:32 MNDeployment #4774 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:32:51
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 04:30 MNDeployment #4773 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:30:51
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.k... - 04:25 MNDeployment #4772 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:25:16
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm.ku.... - 04:16 MNDeployment #4771 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:16:25
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI **BaseURL**: https://bidataone.nhm.ku.... - 04:10 Task #4770 (Closed): KUBI PROD: t2
- Design, code and component test a new MN implementation
- 04:10 Task #4769 (Closed): KUBI PROD: t1
- Design, code and component test a new MN implementation
- 04:10 Task #4768 (Closed): KUBI PROD: Registration in environment
- Design, code and component test a new MN implementation
- 04:10 Task #4767 (Closed): KUBI STAGE: t2
- Design, code and component test a new MN implementation
- 04:10 Task #4766 (Closed): KUBI STAGE: t1
- Design, code and component test a new MN implementation
- 04:10 Task #4765 (Closed): KUBI STAGE: Registration in environment
- Design, code and component test a new MN implementation
- 04:10 Task #4764 (Closed): KUBI DEV: t2
- Design, code and component test a new MN implementation
- 04:10 Task #4763 (Closed): KUBI DEV: t1
- Design, code and component test a new MN implementation
- 04:10 Task #4762 (Closed): KUBI DEV: Registration in environment
- Design, code and component test a new MN implementation
- 04:10 Task #4761 (Closed): KUBI: Testing
- Design, code and component test a new MN implementation
- 04:10 Task #4760 (Closed): KUBI: Verify that MN passes the Replication Tester
- Design, code and component test a new MN implementation
- 04:10 Task #4759 (Closed): KUBI: Verify that MN passes the Web Tester
- Design, code and component test a new MN implementation
- 04:10 Task #4758 (Closed): KUBI: Local Testing
- Design, code and component test a new MN implementation
- 04:09 Task #4757 (Closed): KUBI: Develop Member Node software
- Design, code and component test a new MN implementation
- 04:09 Task #4756 (Closed): KUBI: Developing
- Determine which software stack to use, etc.
- 04:09 Task #4755 (Closed): KUBI: Plan the implementation
- Determine which software stack to use, etc.
- 04:09 Task #4754 (Closed): KUBI: Scope the implementation
- Select the MN Tier, etc.
- 04:09 Task #4753 (Closed): KUBI: Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 04:09 Task #4752 (Closed): KUBI: Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 04:09 Task #4751 (Closed): KUBI: Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 04:09 Task #4750 (Closed): KUBI: Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 04:09 Task #4749 (Closed): KUBI: Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 04:09 Task #4748 (Closed): KUBI: Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 04:09 Task #4747 (Closed): KUBI: Establish contact with potential MN organization
- Establish contact with the developers and/or administrators who will be responsible for developing and/or deploying t...
- 04:09 Task #4746 (Closed): KUBI: Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 04:09 MNDeployment #4745 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:09:44
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 04:08 Task #4744 (Closed): KUBI: Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 04:08 MNDeployment #4743 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:08:36
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 04:07 Task #4742 (Closed): KUBI: Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 04:07 MNDeployment #4741 (Closed): KUBI: MNDeployment: urn:node:KUBI 2014-04-14_22:07:22
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 03:49 Task #4740 (Closed): Scope the implementation
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 03:49 Task #4739 (Closed): Create MN description document
- Work with MN POC to create MN description document, logo, etc. Attach here when complete; store PDF in docs.dataone.org.
- 03:49 Task #4738 (Closed): Create DataONE identities
- Create DataONE identities for one or more of the MN contacts, to enable access to docs.dataone.org, Redmine, etc.
- 03:49 Task #4737 (Closed): Integrate MN representatives with community
- Add MN representatives to MNF/developers/community, other lists as needed.
- 03:48 Task #4736 (Closed): Join DataONE
- Determine if the potential MN organization has the required resources for becoming a MN.
- 03:48 Task #4735 (Closed): Planning
- Determine if the potential MN organization has the required resources for becoming a MN.
- 03:48 Task #4734 (Closed): Determine feasibility
- Determine if the potential MN organization has the required resources for becoming a MN.
- 03:48 Task #4733 (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...
- 03:48 Task #4732 (Closed): Initial Preparation
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm... - 03:48 MNDeployment #4731 (Closed): MNDeployment: urn:node:KUBI 2014-04-14_21:48:49
- This issue is to track deployment of member node:
**Node ID**: urn:node:KUBI
**BaseURL**: https://bidataone.nhm...
Also available in: Atom
