• Fix the items mentioned in issues.

frontend ideas

  • datasources functionality:
    • Implement async wikidata-enriching (partly done)
    • ? datasource-activation switches for only autocomplete (not searching)
  • Add claim-support to the Wikidata-data fetching (and support for claim-data in the field-definitions).
  • Bookmarking:
    • Cross-tab bookmark state-syncing
    • Bookmark edit mode → then click on bookmark → display bookmark edit modal → save button
    • Better generic data support, based on the “item data object”
    • Add more input-formats:
    • Research better drag-and-drop support
  • structured search (beyond Wikidata)
    • ontology classes
    • ontology properties
    • autocompletion
    • multi-lingual labels
    • handle CORS issues
  • search modalities:
    • support date-range search modality
    • support geo / date-range searching in the active datasources (when possible through their API).
      • add to each datasource definition which search-modalities are supported: string, geo, date, …

admin-dev workflows

  • Clean up any issues with field definitions:
    • Turn the the inline-API field-structure into an object (instead of a string)?
  • Field-translation support: Create a structure to store field-label translations (title and icon-title), both for Wikidata and non-Wikidata fields.
    • Allow the json2fields script to fetch and store property translations too.

general ideas

  • Conzept development vision:
    • data-defined software. Often this first requires several code implementations/examples to explore the domain.
    • Improve and maintain conceptual integrity, as vague and abstract as that term is.
  • Research educational-support enhancements:
    • Collaborative & social learning features (eg. p2p audio-chat and text-chat rooms for each topic)
    • User-created and auto-generated presentations around a topic
    • Auto-generated topic quizzes
    • Auto-generated, spaced-repetition-based facts learning (for a certain topic / set of topics / topic-domain)
    • ? Note-taking integration (eg.: Bangle, …)
    • Better ways to indicate personal and professional interests (similar to the persona-tags setting)
    • Experiences: play Chess positions (done), …
  • ? Offline(-first) support with content-caching (especially useful when traveling and/or without reliable internet-connectivity).
  • ? Research creating some kind of a simple web-application interface standard for input/output/event-handling:
    • URL parameter IO (iso2 language, search-string, ID, …)
    • Event-handling (other view triggers, key-bindings, fullscreening, …)


  • How to detect if the field URL could be embedded (instead of opening a a new tab)? (run a headless browser loading an iframe with the URL, checking for CORS-errors?)
  • JSON-LD enhancement: “Add schema:about properties that include #Wikidata (/entity/{id}) and #DBpedia (/resource/{id}) identifiers as property values.” * (this is useful when there are multiple subjects, beyond the main subject)
  • Find and integrate a more lightweight MIDI-webcomponent, if available (html-midi-player is more than 0.5MB by itself!)