-
Notifications
You must be signed in to change notification settings - Fork 2
Extension: EntityFCS
Erik Körner edited this page Sep 18, 2024
·
3 revisions
- Demo:
- @text+: https://tppssi-demo.saw-leipzig.de/
- Enable Entity Search in settings
- Switch to Advanced Search (Only supported there)
- Switch to Results View, enable annotation layer view
- Tokens or Spans may be underlined where Entities can be annotated, by hovering an info box will pop up that uses the GND to fetch meta information about an entity by using its ID
- @text+: https://tppssi-demo.saw-leipzig.de/
Searching using an entity ID
- cover alternative forms (spelling mistakes, historical forms)
- synonyms, synsets
- co-references/mentions: "he"/"she"/"they", "the person", ...
- disambiguation (homonyms; same spelling but different person or different word usage based on context)
- Which IDs to support
- Entity ID resolution (due to different vocabularies)
- on endpoint or client (FCS Aggregator, search support) side
- Idea: FCS client (FCS Aggregator) with keyword expansion using entity ID to generate list of word forms for native search
-
Advanced Search with new Layer Type Identifier of
entitythat should annotate tokens/spans using entity IDs (prefixed or full URIs) - in Vuetify FCS Frontend (demo) with custom search input support (ID suggestions) and visualization (see section Resource and Materials)
- Entity search "mode" in FCS Aggregator to generate search queries (using IDs) for both Advanced Search and Lexical Search (see LexFCS - FCS for Lexical Resources) for aggregated results over multiple search query types
- ⚙️ AAI
- ⚙️ LexFCS - FCS for Lexical Resources
- 🧪 EntityFCS - Search with entity IDs
- 💭 Syntactic Search
- 💭 Metadata for Result
- 💭 Custom Fonts for Results
⚙️ wip, testing 🧪 experimental 💭 ideation