Difference between revisions of "Developer Space/Components"

From wiki.gpii
Jump to: navigation, search
m (Executive Summary)
m (Curators)
Line 19: Line 19:
  
 
=== Curators ===
 
=== Curators ===
e whole Developer Space site is build on Drupal 7 technologies (for the underlying architecture please refer to D201.5 of the Prosperity4AllProject). The component repository specifically relies on the Search and Facets API, that provides the necessary interfaces for efficient browsing via an Apache SOLR server. The curation scheme above is implemented using the Workbench module. Those parts are shared with the otding Components to the GPII Developer Space
+
The overall Developer Space site is build on [https://www.drupal.org/drupal-7.0 Drupal 7] technology (for the underlying architecture please refer to D201.5 of the Prosperity4AllProject). The component repository specifically relies on the [https://www.drupal.org/project/search_api Search] and [https://www.drupal.org/project/facetapi Facets API], that provides the necessary interfaces for efficient browsing via an [https://www.drupal.org/project/search_api_solr Apache SOLR] server. The curation scheme above is implemented using the Workbench module. Those parts are shared with the other content of the Website.
  
 
=== Suggesting New Components ===
 
=== Suggesting New Components ===

Revision as of 11:28, 3 January 2018

Open component repository

Executive Summary

This document contains a accompanying user guide and developer documentation for the GPII Developer Space Component Repository, which is online as part of the GPII Developer Space at. If you are interested in contributing visit the site directly at http://ds.gpii.net/components. and refer directly to the relevant section in this document.

The repository is constantly extended and allows structured search in a compehensive list of building blocks for Assistive Technology development and implementation. The repository is as inclusive as possible, addressing different needs and solutions by a diverse set of software and hardware. The components listed on this page fulfil some minimal requirements for documentation and categorisation, that we define in this document. If you want to add a component to the list please go to https://github.com/dspace-projects/additions/issues, drop a mail on http://lists.gpii.net/cgi-bin/mailman/listinfo/dspace or post to our twitter account at https://twitter.com/GPII_DevSpace.

The goal of this public deliverable of the Prosperity4All Project is to provide particularly technical documentation about the background of the site and the curation process, which aims to be transparent, sustainable and scalable. The document is the last one in a range of documents (D202.1 and D202.2) where we have described, how we created and designed this repository and looked at technical convergence of components through standards and APIs. If you want more detailed information about the underlying architecture of the whole Developer Space refer to D201.5 as this document documents particularly the component listing. Additionally you should visit and browse the actual main deliverable of the project, which is online at http://ds.gpii.net/.

Background and Related Efforts

The component repository is not a unique effort in the sense that it collects accessibility related components. However, it differs from existing efforts in multiple ways. Even before the efforts started in this project the Spotlight / featured tools and components on the RaisingTheFloor web site provided a listing of developer targeted tools and components. This listing has been incorporated into the GPII Developer Space along with other developer targeted content. RaisingTheFloor is committed to curate this content beyond the project via the GPII Developer Space. The original listing also contains project specific listings like the AEGIS: Overview of demonstrators . It is the goal of the GPII Developer Space to provide a platform for such listings in the future and interlink open project results from commercial or academic endeavours in more sustainable way. Today many AEGIS demonstrators live on github such as http://hanshillen.github.io/jqtest/ where there can be easily forked and used by developers. We want to encourage projects to bring content to places where the developers actually are, without creating a new place that diverts traffic. This is why we also provide an interface that just provides an alternative interface to existing sites. The same goes for technology specific efforts like the W3C WAI Component Gallery. We were easily able to incorporate most content as it was hosted here as well as we also depend on external activities like Project A11y to identify open source content. The biggest difference of the component repository is that we have identified over 1000 accessibility related open source components, that we started to categorize on https://ds.gpii.net/develop/components .

The Interface for Searching, Browsing and Bookmarking Components

The Repository for Users

Editors

Curators

The overall Developer Space site is build on Drupal 7 technology (for the underlying architecture please refer to D201.5 of the Prosperity4AllProject). The component repository specifically relies on the Search and Facets API, that provides the necessary interfaces for efficient browsing via an Apache SOLR server. The curation scheme above is implemented using the Workbench module. Those parts are shared with the other content of the Website.

Suggesting New Components

Using Github

Strategies for finding new componets

Understanding the Importing and Updating Pipeline

Drupal Feeds Plugin

The Mapping of Github information to DSpace

Editing and Categorizing Components

Type

Needs

Solutions

Procurement Requirements

Curating and Publishing Components

Minimal Requirements

Scheduling for Publication

Summary and Future Work