[CWB] [ cwb-Feature Requests-2888435 ] CQPweb: customisable tertiary annotation mapping tables

[SourceForge.net]

Feature Requests item #2888435, was opened at 2009-10-29 00:51
Message generated for change (Comment added) made by andrewhardie
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722306&aid=2888435&group_id=131809

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: CQPweb
Group: None
Status: Open
Priority: 5
Private: No
Submitted By: Andrew Hardie (andrewhardie)
Assigned to: Andrew Hardie (andrewhardie)
Summary: CQPweb: customisable tertiary annotation mapping tables

Initial Comment:
Mapping tables for "simple" pos tags are currently hard coded. They shouldn't be - rather, load them from mySQL at runtime. 

(But, it is worth keeping the hard coded ones so that they can be loaded *into* the mySQL database so that it _starts_off_ with a bundle of frequently used mapping tables ready to use.)

There will need ot be some kind of admin interface to allow for creation, management and removal of mapping tables. This will actually be the bigger part of the job.

-------------------------
Note also: BUG in the combo annotation where there is no combo annotation. Se install file for further details.

----------------------------------------------------------------------

>Comment By: Andrew Hardie (andrewhardie)
Date: 2009-11-28 10:37

Message:
Summary of how these features should work when they are fully
configurable.

1) You can simply define the tertiary annotation to search a field, like
the pri and sec.
2) OR you can define it to use a mapping table.
2a) It can use a mapping table on a field that is not otherwise searchable
(like the "class" field in the BNC)
2b) OR it can use a mapping table on a field that is searchable by some
other bit of syntax (like the "pos" field in the BNC)

HOWEVER, documentation should explain the "norm" of having tertiary
annotation be  a "simple pos", and how this should use the same basic
labels as the Oxford Simplified Tagset.

Mappings:
--------------
1) There should be as many built-in mapping tables as possible.
2) These should exist in forms BOTH for the "class" equivalent (as at
present) and as regexes for "pos"
3) These should not be hardcoded in ceql.inc.php, but rather should be
loaded to mysql when there is a DB reset.
4)  There should be a user interface allowing additional mapping tables to
be specified.

The combo annotation
-------------------------------------
1) It can simply the specify the combination of any two arbitrary p-atts.
2) either or both of these may use a mapping table.
3) OR it can read a combination-field like lemma in the BNC
4) again, the first half or the second half or both may use a mapping
table.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=722306&aid=2888435&group_id=131809