General

Profile

Issues

Filters

Apply Clear

# Project Tracker Status Priority Subject Assignee Updated Category
433RequirementsRequirementNewLow(Requirement) Data and metadata is replicated to at least one other member node2010-03-25 03:11
412RequirementsRequirementNewLow(Requirement) Identifiers always refer to the same object2010-03-25 15:41
431RequirementsRequirementNewLow(Requirement) Software developed for infrastructure should be implemented according to specifications2010-03-25 14:44
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
371RequirementsRequirementNewLow(Requirement) Provide a suite of collaboration tools and instruction on how to use them2010-03-16 20:06
389RequirementsRequirementNewLow(Requirement) Implement a Member Node based on the ORNL DAAC2010-03-25 14:46
388RequirementsRequirementNewLow(Requirement) Implement a Member Node based on Dryad2010-03-24 13:36
383RequirementsRequirementNewLow(Requirement) System supports data storage2010-03-16 21:35
387RequirementsRequirementNewLow(Requirement) Implement a Member Node based on Metacat2010-10-06 22:00
385RequirementsRequirementNewLow(Requirement) Support arbitrary unique identifiers2010-03-16 22:09
386RequirementsRequirementNewLow(Requirement) Deploy at least three Member Nodes2010-03-17 13:39
592RequirementsRequirementNewHighDataONE needs to synchronize metadata between MNs and CNsRobert Waltz2010-09-06 02:28d1_cn_service
770RequirementsRequirementNewHigh(Requirement) Authorization system should be able to express the pseudo-principal concepts like 'public'Dave Vieglais2010-08-11 00:41Requirement
393RequirementsRequirementNewHigh(Requirement) Access control rule evaluation must be highly scalable and responsive.Dave Vieglais2010-09-06 20:27Requirement
771RequirementsRequirementNewHigh(Requirement) User identities should have simple string serializations that express both the user identity and namespace from which it is drawnDave Vieglais2010-09-06 03:12Requirement
392RequirementsRequirementNewHigh(Requirement) Identity and access control should be interoperable across datanetsDave Vieglais2010-09-06 20:31Requirement
772RequirementsRequirementNewHigh(Requirement) Authentication services should be compatible with existing infrastructure and applicationsDave Vieglais2010-08-11 07:54Requirement
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
761RequirementsRequirementNewHigh(Requirement) Users can specify authorization rules for data objects, science metadata objects, and process artifacts separatelyDave Vieglais2010-09-06 03:06Requirement
765RequirementsRequirementNewHigh(Requirement) Tools can access an API for authn and authzDave Vieglais2010-09-06 20:30Requirement
318RequirementsRequirementNewHigh(Requirement) Sponsor required Y1 functionalityDave Vieglais2010-09-06 03:24d1_common_java
762RequirementsRequirementNewHigh(Requirement) User identities can be derived from existing institutional directory servicesDave Vieglais2010-09-06 03:01Requirement
(1076-1100/1153) Per page: 25, 50, 100, 500

Also available in: Atom CSV PDF

Add picture from clipboard (Maximum size: 14.8 MB)