search

ufal / perl-pmltq-web

Simple web build on the top of the PML Tree Query server
https://lindat.mff.cuni.cz/services/pmltq/
0 stars 0 forks source link

PDiT2.0: how to access m-layer attributes - suggested query leads to empty output, #130

Open Ansa211 opened 6 years ago

Ansa211 commented 6 years ago

According to the Node Types menu, the corpus should contain nodes of type m-node. However, the query m-node [] has an empty output.

Another way how to access the information from the m-layer in PDT-corpora is usually as an m/something attribute on the a-layer. However, although the menu Attributes > of a-node contains the value m/form, the query a-node [m/form ~ '.*'] has an empty output. (The same query works in PDT 3.0!)

The Suggest function does not help either: Go to PDiT 2.0 and enter a simple query for an a-node a-node []. Select the first node and use the Suggest function to create the following queries; both queries lead to empty output od PDiT2.0 but have some output on PDT 3.0: a-node $a := [ member m [ form = 'unie', ], ] vs. the same in PDT 3.0 a-node $a := [ member m [ member w/[1] [ token = 'unie', ], ], ] vs. the same in PDT 3.0

matyaskopp commented 6 years ago

suggest is based on files in pml format but the query is evaluated on database. m-node table in postgres database is empty thus query result is empty too.

file /net/work/projects/pmltq/data/pdit20/sql_dump/adata__type_m-node.dump is not empty so I guess that it was incorrectly imported to database.

matyaskopp commented 6 years ago

Fixed treebanks: pdit20, pdit20_full

Treebanks were converted with wrong mdata_30_schema.xml schema.

matyaskopp commented 6 years ago

Not fixed. I guess that m-node type is not converted as we usually convert trees on analytical and tectogrammatical layers. Should be all pdt like treebanks reconverted?