Executive Summary: A service provider wants to enable research communities to install software on a resource they administer so the software can be used by the community and so community information systems contain resource-specific instructions that researchers can find and follow.
The functionality described in this use case is 90% supported by the operational components listed here.
The effort required for the two currently proposed activities is estimated at 8 hours total, 4 hours per gap.
|Component||User facing?||Component’s role in the capability|
|Research Software Portal (RSP)||yes||The SP learns that RDR is used to maintain resource information, and that they need to choose whether to support the Community Software Area (CSA) feature on their resource(s).|
|Resource Description Repository (RDR)||yes||SP records that a resource offers the CSA feature, and records instructions for the researcher on requesting a CSA and how to advertise software the researcher is making available thru the CSA.|