General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
766RequirementsRequirementNewHigh(Requirement) Users should be able to easily assign proxy privileges to other users and to systems acting on their behalf for limited time durationsDave Vieglais2010-08-11 00:11Requirement
765RequirementsRequirementNewHigh(Requirement) Tools can access an API for authn and authzDave Vieglais2010-09-06 20:30Requirement
764RequirementsRequirementNewHigh(Requirement) Authentication and access control should be consistently availableDave Vieglais2010-09-06 20:32Requirement
763RequirementsRequirementNewHigh(Requirement) Authentication and authorization services are geographically replicatedDave Vieglais2010-09-06 20:52Requirement
762RequirementsRequirementNewHigh(Requirement) User identities can be derived from existing institutional directory servicesDave Vieglais2010-09-06 03:01Requirement
761RequirementsRequirementNewHigh(Requirement) Users can specify authorization rules for data objects, science metadata objects, and process artifacts separatelyDave Vieglais2010-09-06 03:06Requirement
632RequirementsRequirementNewLow(Requirement) Monitor the DataONE infrastructure2010-05-28 20:10
592RequirementsRequirementNewHighDataONE needs to synchronize metadata between MNs and CNsRobert Waltz2010-09-06 02:28d1_cn_service
581RequirementsRequirementNewLow(Requirement) System supports multiple types of science metadata2010-04-20 20:45
580RequirementsRequirementNewLow(Requirement) All software developed on the project should be open sourceDave Vieglais2010-04-15 22:57
468RequirementsRequirementNewLow(Requirement) Design the cyberinfrastructure for the project.2010-03-25 16:51
455RequirementsRequirementNewLow(Requirement) Installation of critical software must be well documented and as automated as possible2010-03-25 13:52
439RequirementsRequirementNewLow(Requirement) Maintain original copies of all science metadata2010-03-25 03:27
433RequirementsRequirementNewLow(Requirement) Data and metadata is replicated to at least one other member node2010-03-25 03:11
431RequirementsRequirementNewLow(Requirement) Software developed for infrastructure should be implemented according to specifications2010-03-25 14:44
412RequirementsRequirementNewLow(Requirement) Identifiers always refer to the same object2010-03-25 15:41
411RequirementsRequirementNewHigh(Requirement) The infrastructure must survive destruction of one or more data storage nodesDave Vieglais2010-09-06 03:10d1_common_java
410RequirementsRequirementNewLow(Requirement) The infrastructure must support long term preservation of Data2010-03-25 15:41
409RequirementsRequirementNewLow(Requirement) Develop a reference implementation of the Member Node stack2010-03-25 13:57
408RequirementsRequirementNewLow(Requirement) Implement a Coordinating Node software stack2010-03-25 15:44
393RequirementsRequirementNewHigh(Requirement) Access control rule evaluation must be highly scalable and responsive.Dave Vieglais2010-09-06 20:27Requirement
392RequirementsRequirementNewHigh(Requirement) Identity and access control should be interoperable across datanetsDave Vieglais2010-09-06 20:31Requirement
391RequirementsRequirementNewHigh(Requirement) Enable different classes of users commensurate with their roles.Dave Vieglais2010-09-06 20:51Requirement
390RequirementsRequirementNewHigh(Requirement) Consistent mechanism for identifying usersDave Vieglais2010-09-06 20:50Requirement
389RequirementsRequirementNewLow(Requirement) Implement a Member Node based on the ORNL DAAC2010-03-25 14:46
(151-175/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)