Skip to content
#

search-interface

Here are 172 public repositories matching this topic...

JasonStoltz
JasonStoltz commented Oct 31, 2019

The Results component should accept a prop called 'displayFields` which would allow users to specify which fields from their result object to display. The parameter should be able to express:

  1. Order
  2. field
  3. field label

Example:

result:

{
  title: {title value},
  date: {date value},
  cats: {cats value }
  isbn: {isbn value}
}

Component using new field

Open Source research tool to search, browse, analyze and explore large document collections by Semantic Search Engine and Open Source Text Mining & Text Analytics platform (Integrates ETL for document processing, OCR for images & PDF, named entity recognition for persons, organizations & locations, metadata management by thesaurus & ontologies, search user interface & search apps for fulltext search, faceted search & knowledge graph)

  • Updated Dec 8, 2021
  • Dockerfile
RecoverPy
PabloLec
PabloLec commented Jun 21, 2021

Currently, RecoverPy only works with Linux systems.
This is due to the different tools it uses under the hood but theoretically it could be adapted to work on macOS.

grep, dd and even progress are compatible with macOS, so no change needed here.
But lsblk is not so here is the first difference.

Additions needed I can think of right now are:

  • Detect if OS is Linux or macOS (done).

Python/Django based webapps and web user interfaces for search, structure (meta data management like thesaurus, ontologies, annotations and named entities) and data import (ETL like text extraction, OCR and crawling filesystems or websites)

  • Updated Oct 31, 2020
  • CSS

Improve this page

Add a description, image, and links to the search-interface topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the search-interface topic, visit your repo's landing page and select "manage topics."

Learn more