Project

General

Profile

CCI-0.3 Deployed

2010-05-03

100%

151 issues   (151 closed — 0 open)

The first version of the DataONE infrastructure components. Basic CN implementation with CN-CN synchronization and MN metadata transfer to CN.

Includes milestones:

  • Initial coding on low level functionality and schemas
  • Functional use cases addressed: 1, 36
  • Prototype specifications documented
  • Initial core software components identified
  • System Metadata schema defiend
  • CN Application library incompatibilities evaluated
  • Base inter-process communications enabled (Mercury - Metacat)
  • CN, MN API wrappers generated
  • Implement reference implementation of MN and CN
  • Low level logging incorporated into API wrappers
Issues by
Story

14/14
Task

132/132
Bug

3/3
Feature

1/1
Decision

1/1
Related issues
Story #259: As a CN, I need to be able to call any of the valid 0.3 MN APIs at any time.
Story #278: (Story) As the system, I want Mercury to return results conforming to the DataONE Collection Object Response
Story #284: (Story) As a developer, I want to have a test development machine of my own
Story #293: (Story) Fix issues found during code review.
Story #305: (Story) Misc to wrap up for 0.3
Story #319: As a developer, I want to build a CN Service with Mercury fully installed such that I can complete integration testing.
Story #325: Design phase with Ryan
Story #347: Implement get() method for Metacat
Story #354: Complete refining CN and MN logging specification
Story #355: Document CN VM configuration and installation
Story #359: Determine if system metadata should or should not be stored on Member Nodes
Story #476: Create a VM to host the Python MN software
Story #523: As the GMN manager, I need to deploy GMN as a DataONE adapter for Dryad
Story #525: As a CN, I need to be able to obtain a skeleton system metadata object from Dryad for any of its objects at any time
Task #78: Specify hardware requirements for Coordinating Nodes
Task #80: Trigger mercury to update index on document addition / change
Task #81: Determine incompatibilities between Metacat and Mercury
Task #88: Create development KVM instance for CN prototyping
Task #141: Generate KVM virtual machine for initial CN development testbed
Task #142: Develop agenda for February CCIT meeting
Task #144: Define the prototype MN Service
Task #145: Define and implement the CN Service
Task #146: Define configuration for Metacat replication
Task #147: Procure and install hardware at ORNL
Task #152: Stub out CN servlet
Task #156: Generate system metadata for content in mn_service
Task #159: Evaluate Maven as a build tool
Task #161: Agenda for Dev Call 20100114
Task #163: Document test server deployment
Task #166: Create a metapackage for installing Mercury dependencies
Task #167: Deploy metacat on the CN dev server
Task #168: Common tools and APIs in CN proto server
Task #173: Document mechanisms for interaction with Mercury system
Task #176: Enable access to cn-dev for Jim Green
Task #177: Agenda for Dev Call 20100121
Task #185: Review the CN buildout
Task #187: Create folder structure for cn_service
Task #188: Design cn_service packages
Task #190: update sysmeta schema enumerated values with real values
Task #191: Pilot catalog style sheet issue
Task #209: add tests to verify unicode handling for MN_service
Task #211: Document the process for command-line building of CN environment under development
Task #219: Document Eclipse Usage for CnService Development
Task #224: Can we setup e-mail generation of a Ticket
Task #228: Working Group page needs review/edit
Task #229: DIUG page needs edit/publication
Task #260: (for story #259) Identify test data and metadata from a Metacat instance
Task #261: Implement MN_crud.getSystemMetadata() (token, GUID) -> objectMetadata
Task #266: (for story #262) Define response from resolve()
Task #279: (for story #278) Review and confirm metadata to be returned by search
Task #280: (for story #278) Research Mercury to determine best manner to return DataONE compliant result sets
Task #281: (for story #278) Create Configuration to use ContentNegotiatingViewResolver
Task #282: (for story #278) Create 3 Xslt to transform model object into Object Collection Response
Task #283: (for story #278) Determine and implement Unit test for Mercury
Task #285: (for story #284) Create Virtual Ubuntu 9.10 Server
Task #286: (for story #284) Apply DataOne Package Install Script
Task #287: (for story #284) Research and resolve certificate issue
Task #292: Building out CN development VM resulted in errors from tomcat
Task #294: (for story #293) Remove all untyped, "unexpected error", exceptions
Task #295: (for story #293) Add checks for HTTP verb and return "405 Method Not Allowed" for unexpected verbs
Task #296: (for story #293) Check for negative count / start
Task #297: (for story #293) Change 404 to the correct return codes
Task #298: (for story #293) Limit max return count of /object/ and /log/ to 1000
Task #299: (for story #293) Add note in REST doc on filtering options that were not required by the API spec
Task #300: (for story #293) Support for Unicode and use Unicode in tests
Task #301: (for story #293) Add detailed error messages to 404 returns
Task #302: (for story #293) Implement serialization abstraction to support different return formats
Task #303: (for story #293) Don't create body for HEAD requests. Return unknown size or disk file size
Task #304: (for story #293) Stream object bytes out instead of buffering in memory
Task #306: (for story #305) Set up a unique index for the from_object / to_object combination
Task #307: (for story #305) Set up test of update_db admin command
Task #313: (for story #278) Create two build scripts for Mercury, review Jim's Maven pom for the common library
Task #314: (for story #305) Add content negotiation
Task #315: (for story #305) Set up a unique index for the from_object / to_object combination
Task #316: (for story #305) Set up test of update_db admin command
Task #320: update developer CN with new packages
Task #321: run build script with only Mercury package installed
Task #322: configure mercury to run correctly
Task #323: verify mercury is responding to query calls
Task #344: Ensure consistent representation of synchronization and replication
Task #345: (for story #259)
Task #361: create a table for the mapping between GUID and Localid in Metacat
Task #362: create LocalID when a request comes in using a GUID
Task #363: refactor handleReadAction() to support GUIDs
Task #398: edit fields in LoggingSchema specification document
Task #399: create schema and instance document for logging
Task #401: specify MN APIs as Java Interfaces
Task #402: specify CN APIs as Java Interfaces
Task #404: create classes for all Exceptions in Java
Task #407: Login accounts
Task #418: modify service_api java BaseException class to produce exception format
Task #419: Adapt Metacat get() to match DataONE API and exceptions
Task #430: Document the decision regarding MN and system metadata
Task #440: Resolve discrepancy between Types.ErrorMessage and serialized forms
Task #442: meet to determine the appropriate approach for utilizing the shared code
Task #460: Document the python module dependencies
Task #462: Document the GMN testing process
Task #463: Create a distribution of the software that all the necessary components
Task #464: Document the GMN install process
Task #469: Define detail error codes in documentation
Task #470: Document network connectivity requirements
Task #471: Provide a document to a MN SA so that he can set up an appropriate Linux target environment for GMN
Task #472: Document OS requirements
Task #474: Update unit tests to match changes in System metadata
Task #475: Refactor code to match the changes in the System Architecture specifications in Member Node APIs
Task #478: Ensure necessary individuals have access to machine
Task #479: Document configuration of hardware
Task #485: write unit test for get REST service
Task #490: Refactor code to match the changes in the System Architecture specifications in System metadata
Task #492: Using Mercury Indexer, confirm that the merged metadata records can be parsed
Task #493: Modify Configuration file and Solr schema
Task #498: Update unit tests to match changes in Member Node APIs
Task #499: Refactor code to match the changes in the System Architecture specifications in Data Types in CICore
Task #500: Update unit tests to match changes in Data Types in CICore
Task #501: Refactor code to match the changes in the System Architecture specifications in REST Interface
Task #502: Update unit tests to match changes in REST Interface
Task #503: Refactor code to match the changes in the System Architecture specifications in Exceptions Raised by MN and CN APIs
Task #504: Update unit tests to match changes in Exceptions Raised by MN and CN APIs
Task #505: Test MN_crud.getSystemMetadata() (token, GUID) -> objectMetadata
Task #506: Implement MN_crud.get() (token, GUID) -> object
Task #507: Test MN_crud.get() (token, GUID) -> object
Task #508: Implement MN_crud.getLogRecords() (token, fromDate, toDate)
Task #509: Test MN_crud.getLogRecords() (token, fromDate, toDate)
Task #510: Implement MN_crud.log() (typeOfOperation, targetGUID, requestorIdentity, dateOfRequest)
Task #511: Test MN_crud.log() (typeOfOperation, targetGUID, requestorIdentity, dateOfRequest)
Task #512: Implement MN_replication.listObjects() (token, query) -> list of GUIDs
Task #513: Test MN_replication.listObjects() (token, query) -> list of GUIDs
Task #517: Test MN_replication.synchronizationFailed() (token, GUID, problemDescription)
Task #518: Implement MN_health.heartbeat() () -> response
Task #519: Test MN_health.heartbeat() () -> response
Task #520: Document hardware or virtual hardware requirements
Task #527: Implement REST call that Dryad calls to register a new science metadata object
Task #528: Implement mets.xml parser to retrieve values for system metadata for the science metadata(mets.xml)
Task #530: Implement proxy mechanism to obtain appropriate Dryad URL given the identifier
Task #531: Create complete list of publicly available data files in Dryad
Task #539: Download science metadata (METS) file from Dryad
Task #540: Parse science metadata (METS) file
Task #541: Get URL of science data object
Task #542: Download science data object
Task #543: Combine data from science metadata, science data and data provided in registration call and create skeleton system metadata
Task #545: Document GMN Dryad REST interface
Task #546: Test that the REST interface conforms to the documentation
Task #547: Provide the documentation to the Dryad developer and have them independently test that the REST interface conforms to the documentation
Task #549: Provide documentation to Dryad SA on how to install the standardized Linux OS distribution
Task #550: Verify ssh connectivity to GMN host
Task #551: Use ssh connection to install standardized software environment
Bug #157: mn_service getObjects reponse is dictionary rather than list
Bug #178: login issue cn-dev.dataone.org
Bug #207: PDF version of architecture docs not being generated
Feature #220: Add object class to system metadata
Decision #212: What level of logging information should be available to whom
Add picture from clipboard (Maximum size: 14.8 MB)