Community Acceptance & Adoption Plan
From DigiRepWiki
This document is a DRAFT.
Contents |
Geospatial Application Profile Community Acceptance and Adoption Plan
This is a plan for community take-up and acceptance of the Geospatial Application Profile. It outlines a deployment path for implementation and take-up, including requirements for developers, repositories and service providers. Recommendations for further community engagement and future maintenance of the Application Profile are also included.
Uptake and deployment of the Application Profile should be driven by the user community, i.e. the repositories wishing to expose metadata and services wishing to consume it, and by the wider stakeholder community, including JISC and other funding bodies as well as a wider international community.
Background and scope
The background rationale for the Application Profile can be found in the Geospatial Application Profile home page. The scope is detailed in the Functional Requirements document.
Stakeholders and designated community
Stakeholders and the designated community for this Application Profile are outlined in the Functional Requirements document.
Maintenance and responsibility
Community engagement plan
Deployment plan
Responses from developers
The following developers and service providers are considered to be key stakeholders for implementation. Repositories using other software or in-house development should be encouraged to adopt the Profile, using the community engagement mechanisms listed above. Successful uptake by the key stakeholders should encourage wider uptake.
Developers
- Eprints.org
- DSpace
- Fedora / VITAL
Service Providers
- Intute (and UKOLN)
- EDINA
DSpace
EPrints
Fedora
Intute
Edina
{to be added}
