Lead by Susan Brown
A square with the title Access. Inside are two smaller squares: the first is titled Consumption and includes interfaces and plugins to browse, search and use LINCS data, and APIs for external tools. The second is titled Conversion and includes interfaces and tools for contributing new data to LINCS.

LINCS infrastructure will establish a polished bilingual Consumption Interface for accessing data through an integrated suite of views and tools, and a Conversion Portal to a range of conversion interfaces and tools. LINCS will serve a wide spectrum of users, from those new to linked open data, to those with technical and administrative experience.

Consumption Interface

The interface for mainstream users is of paramount importance. The Library User Experience team at Guelph, together with High Quality Personnel, will work for the duration of the project to ensure LINCS builds in usability and accessibility from the outset. Its components are:

  • Browsing based on the ARC’s Big Diva collection visualization tool with faceting.
  • Searching by keyword, entity and/or predicate values (like the Linked Modernisms interface); and, for technical users, expert (SPARQL) queries. ARC and ScholarsPortal will help customize the Apache Solr search engine to enable searches on the full-text of source documents from partner collections to pull up associated linked data.
  • A Context Box for entities: a screen of organized information (images, map, context, relationships) modelled on the SNAC prototype and Google Knowledge Panel, with added features to support research. Built as a widget for use in partner interfaces and as a browser plugin to allow LINCS to contextualize entities for users as they read materials on the Web.
  • Results Views in the forms of a list view, thumbnail view, browse view, or graph view provided by HuViz, a spatial view adapted from or using Peripleo, a timeline view, and a citation export button.
  • LINCS Catalogue which will provide a bridge from LINCS results to exploration of associated source documents in the award-winning Voyant visualization suite (cf. the DREAM interface).
  • Feedback tool to allow researchers or citizen scholars to submit corrections or enhancements of existing LINCS data to be vetted by data providers.
An image of the Access layer of the LINCS system diagram. The LINCS Contexts browser plug-in will provide mainstream users with access to search, browse, feedback and context tools and include bridges to external interfaces such as Voyant and HuViz.

Conversion Portal

The conversion portal is for experienced and technical users. Given the number of existing tools used for LINCS data conversion, it is not feasible to integrate interfaces. Instead, the conversion portal will link to but not generally modify existing tools for data conversion. It will comprise:

  • Entry points. A bilingual overview, workflow roadmap, and full documentation of tools. Inspired in part by the DPLA’s Developer’s pages, the portal will draw on a common documentation system to introduce users to a range of conversion platforms through to APIs.
  • Conversion platforms. Well-designed on-ramps to creating LOD for experienced users: CWRC and its Github-based CWRC-Writer; the TEI to RDF interface; Pelagios for spatial data creation; the ARC DH Dashboard for natural text; Karma (with LINCS gazetteers) for relational data. LINCS addresses the requirement by many researchers for cultural data cleaned to a high level by incorporating validation interfaces that enable users to review and refine algorithmically generated LOD in relation to source materials. Trusted users will be able to push enhanced data to LINCS, either directly or through a mediator such as a library, research project manager, or data partner.
  • Programming notebooks. LINCS conversion workflows that use modular tools will be documented through Web-based Voyant Spyral Notebooks, which make programming accessible to less experienced users. Spyral supports a mix of media, code, tools, data, and results. Documentation slides seamlessly into demonstration–with live code snippets–of how to accomplish tasks.
  • Sandbox. Users will be able to create LOD, load it into some tools, and download results.