zazuko / zack-search

A highly adaptable HTML5 only component that enables interactive access and search data from a SPARQL endpoint.

Zazuko Zack [zack-search]

A highly adaptable HTML5 only component which enables interactive access and to search data from a SPARQL endpoint.

Install

• Install dependencies and build project.

  yarn install

• Run locally with proxy to SPARQL endpoint. See for current endpoint in package.json

  npm start

Configure / Development

• Change the config inside

  public/index.js

• Find the relevant CSS definitions in

  lib/zack.css

zack-search's Issues

identical filter are only once allowed in the filter-container

From @l00mi on September 8, 2016 13:23

if the users does try to add the same filter again, please fire an event (ideally with the id or a uniquie way to select the already existing data-filter)

Copied from original issue: zazuko/www.alod.ch#32

improve timeticks (to show interval instead only point in time)

From @l00mi on September 6, 2016 10:54

Copied from original issue: zazuko/www.alod.ch#24

hierarchy filter uses property path isPartOf+ and is extremely slow.

From @l00mi on July 26, 2016 23:9

Seems to be solved with https://issues.apache.org/jira/browse/JENA-1195

Can we update to the latest version?

Copied from original issue: zazuko/www.alod.ch#12

Add "clear" button on text filter

So one can get rid of it easily

Problem with empty lines on https://test.lindas.admin.ch/datasets/

In the bottom there are empty lines, what is the reason for them? This gets reported as errors.

data-property-path-postfix gets lost from filterable to filter

<div class="filter-item" data-filter="=" data-predicate="http://purl.org/dc/terms/hasPart" data-property-path-prefix="^" data-property-path-postfix="undefined" data-value="http://data.staatsarchiv-bs.ch/id/archivalresource/CH-000027-1/pa-633" data-named-node="true" draggable="true">fond: Archiv der Familie Ochs genannt His</div>

On the start-up every Query is issued twice.

Restrict search if &q=<string> is present

Best if it is taken into account for the first query.

make the GRAPH ?g {} an option in the query builder

For know we need to disable this only for the Stardog implementation. Later on we should get rid of this all. So best an option which needs to be set explicitly "true" end else we do not add the GRAPH construct.

resolves https://github.com/zazuko/odine/issues/21

First release

• Switch the example to use query.wikidata.org
• Clean up the queries to be more generic.
• Documentation

implement spinner

From @l00mi on September 6, 2016 10:52

visualize that the client is still fetching data

Copied from original issue: zazuko/www.alod.ch#23

Upgrade dependencies

The module comes with several security issues.
Dependencies should be upgraded.

detach the "search by text" part of the sparql queries

From @l00mi on September 12, 2016 5:34

In preparation for Stardog and as optimization for the current queries:

filter for documents only

Adding the document identifierZack.resultType like following as standard in the filters:
?sub a <http://data.archiveshub.ac.uk/def/ArchivalResource> .

remove the text search instead adding "*" if not set

Instead of providing a * as searchString remove the complete part of the query handling the text match:

GRAPH <http://data.alod.ch/graph/inference-supertitle> {$
   (?sub ?score ?literal) text:query (skos:hiddenLabel "${searchString}") .$
}

I propose to create another text snippet to be composed to the other queries: zack.textmatch-part.sparql

Copied from original issue: zazuko/www.alod.ch#34

create query dictionary component

From @bergos on November 3, 2016 15:46

The logic to load and manage queries with different dialects should be implemented only in one place in the code. The query dictionary component should read the dialect from the configuration and handle module/file loading. The interface should be implemented with Promises.

Copied from original issue: zazuko/www.alod.ch#41

Inline documentation/help on filters

While the function of the filter-link on the top left ("Series", "Files", "Items") seems more or less self-evident. I think the two filter links on the individual result rows are not and need some explanation (tool-tip, help-link or similar).

Show the reason a search result is found

From @l00mi on November 25, 2016 10:15

Show skos:hiddenLabel in result with the search words highlighted.

Copied from original issue: zazuko/www.alod.ch#44

The intro plugin is dependend on jQuery

We like to use it anyway ...

but we should handle it somehow that jQuery gets only loaded if the intro plugin is actually loaded.

Lets discuss.

Datetime Filter not working because of missing parantheses.

If a handle on the histogram is used to constrain the time the histogram query fails because the date is set in the filter without " around.

Temporary disable filter

One should be able to temporary disable the filter so one can select other filter types that get added to it.

sync issues

If while the interace is still loading the first filter is selected we end up often in an undefined state:

• Reload and immediately click on e.g. "Fonds"
• The result shows 4 items, but we see lots of entries not being fonds.

Overview zack-histogram

Concept and Design related

• The more important point of the component is to show the context of time.

  • Important feature to show for the current selection the start point of the timeline and end point (interval where documents are situated in). Might need visual boost.
  • Documents will relate with arrows or intervals to it (to put them self into context on the timeline.)
  • [Low prio] Timeline is fixed in granularity of years, (ideally it would also scales down to months, days).

• The case that non of the documents provide a date, hence there are no buckets delivered to the visualisation needs to be gracefully handled.

• The black bars can be used to constrain the search query to a time interval. (Probably better user interface metaphor ? Drag over the constraining interval (click-start, drag, click-stop -> interval).

• [Low prio] An intuitive way to relax the constraint is searched after (minimal case, just remove the constraint completely).

• Lowest Target Browser IE11

Dev and Code related

• Fork the development branch to work in.
• Higher level options can be set like this: https://github.com/zazuko/zack-search/blob/develop/public/index.html#L113
• Filtering is provided by simply setting an attribute on the correct html element: https://github.com/zazuko/zack-search/blob/develop/lib/timeline.js#L43

show error message if there are issues with the endpoint

group the same filters (same predicate) in the filter-container

From @l00mi on September 12, 2016 5:44

Add the filters which are needed to groups (by adding them inside the same

<div class="filter-grouped" data-predicate=".."> ... </div>

which allows to show it visually.

Copied from original issue: zazuko/www.alod.ch#35

histogram not define

https://github.com/zazuko/zack-search/blob/develop/lib/timeline.js#L109

var histogram is always undefined ?

Top notch!

@bergos this is class work, was a breeze to setup and run, couldn't have been made any simpler, thanks!

If there is only one result it's hidden by the filters

From @ktk on September 10, 2016 9:7

See screenshot

Copied from original issue: zazuko/www.alod.ch#33

Check if events are flowing according d3 concept

Nothing found ...

If we jump to a query where nothing is found the standard label "loading" is still visible.

https://web-ld-trifid.dev.bgdi.ch/search/?q=Cousset

Can we have an event for "Nothing found." ?

Inspiration for UI in the archival context

From @ktk on September 17, 2016 9:55

Someone which was at #archiveCH contacted me and pointed me to her bachelor thesis:

Die Schwierigkeiten bei der Recherche im Archiv(-katalog). Ursachenforschung und Vorschläge zur Problemstellung

http://www.htwchur.ch/uploads/media/CSI_74_Mueller.pdf

Could be great input for us

Copied from original issue: zazuko/www.alod.ch#37

Refactor d3 visualization code

If necessary refactor where you like.

Timeline code: https://github.com/zazuko/zack-search/blob/develop/lib/timeline.js
Histogram code: https://github.com/zazuko/zack-search/blob/develop/lib/histogram.js

possibly reflect on a plug-in architecture

From @l00mi on October 23, 2016 12:6

Right now the timeline/histogram gets fairly deep integrated with the main application. In some future we might see also a map component and so on. Each which should be easy to enable/disable for different use cases.

Might it be useful to define a plug-in interface architecture?

Copied from original issue: zazuko/www.alod.ch#40

window - resize needs to re-render the results also (to update the timeticks)

From @l00mi on September 7, 2016 8:56

Copied from original issue: zazuko/www.alod.ch#27

Update of Histogram not working after changing with the handles.