Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
project:graph_queries [2018/10/26 17:33] – [New Frontiers in Graph Queries] semper_writes | project:graph_queries [2018/10/27 22:26] (current) – [Putting the spark back into SPARQL] semper_writes | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== SPARQLfish ===== | ===== SPARQLfish ===== | ||
- | ==== New Frontiers in Graph Queries ==== | + | {{sparqlfish_logo.png}} |
We begin with the observation that a typical SPARQL endpoint is not friendly in the eyes of an average user. Typical users of cultural databases include researchers in the humanities, museum professionals and the general public. Few of these people have any coding experience and few would feel comfortable translating their questions into a SPARQL query. | We begin with the observation that a typical SPARQL endpoint is not friendly in the eyes of an average user. Typical users of cultural databases include researchers in the humanities, museum professionals and the general public. Few of these people have any coding experience and few would feel comfortable translating their questions into a SPARQL query. | ||
Line 6: | Line 6: | ||
Moreover, the majority of the users expect searches of online collections to take something like the form of a regular Google search (names, a few words, or at the top end Boolean operators). This approach to search does not make use of the full potential of the graph-type databases that typically make SPARQL endpoints available. It simply does not occur to an average user to ask the database a query of the type "show me all book authors whose children or grandchildren were artists." | Moreover, the majority of the users expect searches of online collections to take something like the form of a regular Google search (names, a few words, or at the top end Boolean operators). This approach to search does not make use of the full potential of the graph-type databases that typically make SPARQL endpoints available. It simply does not occur to an average user to ask the database a query of the type "show me all book authors whose children or grandchildren were artists." | ||
- | The extensive possibilities that are offered by graph databases to researchers in the humanities go unexplored because of a lack of awareness of the possibilities they offer and a shortage of information about how they can be used. Even those academics who understand the potential of these resources and have some experience in using them, it is often difficult to get an overview of the semantics of complex datasets. | + | The extensive possibilities that are offered by graph databases to researchers in the humanities go unexplored because of a lack of awareness of their capabilities |
We therefore set out to develop a tool that: | We therefore set out to develop a tool that: | ||
* simplifies the entry point of a SPARQL query into a form that is accessible to any user | * simplifies the entry point of a SPARQL query into a form that is accessible to any user | ||
- | * makes it possible for users to explore | + | * opens ways to increase |
- | * * | + | * moves away from purely text-based searches to interfaces that are more visual |
+ | * gives an overview to a user of what kinds of nodes and relations are available in a database | ||
+ | * makes it possible to explore the data in a graphical way | ||
+ | * makes it possible to formulate fundamentally new questions | ||
+ | | ||
+ | * can eventually be applied to any SPARQL endpoint | ||
+ | [[https:// | ||
===== Data ===== | ===== Data ===== | ||
- | * List and link your actual and ideal data sources. | + | Wikidata |
===== Team ===== | ===== Team ===== | ||
* Loïc Jaouen loic.jaouen@unil.ch | * Loïc Jaouen loic.jaouen@unil.ch | ||
- | * ... | + | * (Elena Chestnova elena.chestnova@usi.ch) |
| | ||
{{tag> | {{tag> | ||