Differences

This shows you the differences between two versions of the page.

--- project:discoverabilitythroughstructure [2015/06/05 14:26] – [Concept: Metadata Extraction] toiletpee
+++ project:discoverabilitythroughstructure [2019/02/03 21:17] (current) – old revision restored (2015/06/06 13:39) loleg
@@ Line 24: / Line 24: @@
 A simple implementation of this would be a site that allows querying multiple CKAN instances. From this point, additional major open data portal types could be targeted. One possible backend for this might be pazpar2.
+**Use case**
+**Goal:** A user wants to find data that combine election results with demographic characteristics (age, nationality etc., areas).
+**User workflow without the meta portal:** The user searches different portals with different interfaces in order to find the information he wants. Hence he has to enter the same query several times. After having found the necessary data, the user has to combine/visualize the data himself using a separate applicatio
+Disadvantages: Searching takes a lot of time or the necessary data cannot be found although the data would actually be available.
+**User workflow using the meta portal:** The user only searches in one portal with one interface. The system helps the user to find the data by providing filters, suggestions, culstering, maps. He might find data from repositories that he otherwise wouldn't have searched.
+**Specific user workflow:**
+  - The user enters the keywords //zurich elections//
+  - The system suggests search terms/displays boxes using disambiguation (e.g.: zurich in switzerland city, zurich in switzerland canton).
+  - User selects "his" Zurich and the list of results is adjusted according to his choice.
+  - User selects relevant datasets and saves them to "download list"
+  - He starts a new search //zurich demografics//.
+  - The system provides facets/filters (age, nationality, sex, education) in order to refine the list of results.
+  - see 4)
+  - The user has the possibility to directly combine and visualize the actual data within the portal itself.
+**Datasets to experiment with:**
+  - http://data.stadt-zuerich.ch/ogd.FUf4u5s.link
+  - http://data.stadt-zuerich.ch/ogd.qIvPeoN.link
 ===== Concept: Metadata Extraction =====
@@ Line 30: / Line 55: @@
 This could be for example implemented as a CKAN extension and/or a standalone executable. CKAN already has the [[http://docs.ckan.org/en/ckan-2.2/datastore.html|DataStore extension]], which allows full-text search of files uploaded to a CKAN instance. Metadata extraction would improve this further.
 ===== Concept: Ontologies =====
@@ Line 36: / Line 62: @@
 This could be implemented as part of the search portal, or also as a CKAN extension.
+GeoNames may be a good source of geographical ontology data.
+===== Mockups: Global open data search portal =====
+{{:project:search_elections.png?200|}}
+{{:project:search_demographics.png?200|}}
+{{:project:analytics.png?200|}}
+Mockups created using [[balsamiq | https://balsamiq.com/]]
+===== Prototype: Global open data search portal =====
+[[https://sleepy-sea-1327.herokuapp.com|demo]], [[https://github.com/bellisk/opendata-multisearch|source code]]
+Future Work:
+   * Sorting by title, pub date, relevant date
+   * Searching by relevant date (date/date range the information is about)
+   * Example of a facet widget that is enabled for certain searches, eg Volksinitiativen have data sets by different areas like Canton, Municipality, etc.
 ===== Team =====
@@ Line 41: / Line 86: @@
   * [[user:toiletpee|Rae Knowler]] [[https://twitter.com/raeknowler]]
   * [[user:eth-bibliothek|Claudia Lienhard]]
-  *
+  * [[user:wolfram|Wolfram Willuhn]]
 ===== Links =====
@@ Line 49: / Line 94: @@
   * [[http://www.library.ethz.ch/en/]]
   * [[http://www.geonames.org/]]
+  * [[http://www.geonames.org/export/place-hierarchy.html]]
+  * [[http://ckan.org/instances/]]
+  * [[http://docs.ckan.org/en/latest/api/index.html]]
-{{tag>status:concept needs:design}}
+{{tag>status:concept needs:design research}}