Project Conclusion Report

verglichen mit
Diese Zeile wurde entfernt.
Dieses Wort wurde entfernt. Dieses Wort wurde hinzugefügt.
Diese Zeile wurde hinzugefügt.

Änderungen (2)

Seitenhistorie anzeigen
In order to load the RDF data provided by our API and GeoNames into Drupal, the built-in RDF capabilities of Drupal were extended to not only [output|], but also read data in RDF. The mappings of RDF-properties and classes to Drupal fields and bundles are parsed from the application profile.

As mentioned above, we link to geonames GeoNames for countries and cities to demonstrate the approach of adding additional context to our data. These links contain data such as the population which could be used for further visualizations. Furthermore, although we do not use Drupal's database for our actual data, all other capabilities of the CMS can be used, e.g. to define users and roles in an editing workflow.

h2. JavaScript Map (-)

The JavaScript map is a separate read-only front-end based on [Leaflet|]. Although it is currently embedded in the Drupal site, it communicates directly with the API to fetch its data. Most filtering (i.e. by type and country) is done within the map's JavaScript at this point of the prototype. As the dataset grows, this filtering can be moved to the API to increase performance. As a pragmatic approach, the map's popups reuse the views provided by Drupal. These views can be replaced by custom renderings in the future. To demontrate the advantages of linking to external datasets, country labels from the GeoNames data are provided in the language corresponding to the browser's settings. These multi-lingual labels are not part of the OER world map dataset, but retrieved from GeoNames using the Linked Open Data approach. Any updates to the GeoNames data will thus be reflected in the UI automatically. {color:#ff0000}(Hier könnte noch besser herausgearbeitet werden, dass das ein Vorteil von LOD ist){color}