12,347
edits
LexVoc: Difference between revisions
From LexBib
→Update Workflow
mNo edit summary |
|||
| Line 48: | Line 48: | ||
== Update Workflow == | == Update Workflow == | ||
As soon as a new term is linked to a member of the main SKOS graph using [[Property:P72|skos:broader]] or [[Property:P77|skos:closeMatch]], it is considered in subsequent iterations of article full text indexation. | On Elexis LexMeet, you can contribute to the discussion about LexVoc structure, i.e. the definition of main branches, and the inner organization of these: https://meet.elex.is/groups/lexicographic-concepts-vocabulary/ | ||
Regarding inclusion of new terms: As soon as a new term (i.e. a member of [[Item:Q7|Class "Term"]], and of at least one [[Item:Q33|skos:Collection]]) is linked to a member of the main SKOS graph using [[Property:P72|skos:broader]] or [[Property:P77|skos:closeMatch]], it is considered in subsequent iterations of article full text indexation. On the other hand, if a term has no [[Property:P72|skos:broader]] or [[Property:P77|skos:closeMatch]] relation to another term, it is not (any more) considered for article full text indexation. An article full text indexation iteration (performed locally by [[User:DavidL]]) thus reflects the state of LexVoc at that particular point of time. | |||
== Stop-labels == | |||
Some term lexicalizations are very ambiguous, and do not yield proper results (many false positives and/or too many distinct word senses relevant in the domain of Lexicography). At the time being, our workaround is a label stop-list, which is accessible [https://github.com/elexis-eu/elexifinder/blob/master/wikibase/stopterms.py here]. These term labels are not considered in article full text indexation (if a term has several labels, those are not affected). | |||
