A community member needs to update the public record of specific system information so others can find and use the information. Several specific examples of this general need follow. (a) An community member needs to revise/update the known use cases. (b) A community member needs to update the implementation status of one or more use cases. (c) A community member needs to publish a plan to change an implementation of one or more use cases. (d) A software provider needs to add/update information about their software. (e) A service provider needs to add/update availability of a service.
User Importance Summary:
The public research computing environment should be open and extensible: a "community infrastructure." In order to use and participate in this environment, community members (researchers, application developers, service providers, campus IT administrators) must be able to access and update details about the system’s design, implementation status, and the driving user needs.
Target Communities and Sizes:
Application developers - 100 < N < 1,000
Campus IT administrators - 100 < N < 1,000
Software providers 10 < N < 100
Service providers - 10 < N < 100
Staff members - 10 < N < 100