During the course of development several issues have been resolved in the current implementation of the frontend. Here is the changeLog for the new version available under “http://korap.ids-mannheim.de/app“.
- bug fixes:
- save user query resulted in connection error
- query language was not persisted to query object upon saving
- constant request polling
- headline with query and total number of results in match view was hidden
- show total number of page results in match view
- bootstrap communication with backend service was executed per request
- annotation links in match did not line break upon page resize
- display of morphological information in a table per foundry and match
- quick search is disabled by default now (but can be enabled in KorAPPreferences)
- save current query is directly persisted to database
- predefined collections are no longer statically loaded, but integrated with the policy service. Thus, if a user does not match the available policies for the collection, the collection is not returned. The result: only accessible collections are displayed in the frontend.
In lieu of help files, which are still on the to-do list (they will be created after the final features of the system are in place), we have started a Frequently-Asked-Questions document.
The test version of KorAP is now open for IDS-internal access (through the “demo” profile, linked right below the “Login” button) at http://korap.ids-mannheim.de/app
Please note that, for the time being, we can only serve a limited portion of DeReKo data, available to non-authenticated users. The preferred browser to use is Firefox. The frontend has also been tested with Safari. Old versions of Internet Explorer will surely not work well with it.
As you can image, at the moment we are aware of the most critical bugs, but we welcome all feedback, big and small. Bug report forms are available from inside the test version, by clicking the “Kontakt” link.
the KorAP Team
We are now in the process of establishing the internal address and the way to serve KorAP within the IDS. We should be done with the relevant details in the
The slides will also be published here, after we have addressed some of the issues that have appeared in the question period.
Piotr Banski (for the Team)
A demonstration video presented at the LTC conference in Poznań (Poland) from 7 -9 December 2013:
KorAP web interface demonstration
We’re happy to share the extended abstract that we have submitted for LTC-2013. We would also like to gratefully acknowledge the Organisers’ invitation to submit a related paper to a special peer-reviewed proceedings volume.
The presentation was given on the 8th of December, 2013, and the full reference is as follows:
Bański, P.; Bingel, J.; Diewald, N.; Frick, E.; Hanl, M.; Kupietz, M.; Pęzik, P.; Schnober, C. and A. Witt. 2013. KorAP: the new corpus analysis platform at IDS Mannheim. In Vetulani, Z. and H. Uszkoreit (eds). Human Language Technologies as a Challenge for Computer Science and Linguistics. Proceedings of the 6th Language and Technology Conference. Poznań: Fundacja Uniwersytetu im. A. Mickiewicza. ISBN 978-83-932640-3-2
We would like to announce that the next issue of the workshop on the Challenges in the Management of Large Corpora (CMLC) has been approved by the LREC Organization Committee.
More information is to be found here: http://corpora.ids-mannheim.de/cmlc-2014.html
Today we reached a preliminary feature freeze of the the Lucene based backend of KorAP. We now provide a good portion of the functionality of Cosmas II, are close to fully support the Poliqarp Query Language, and introduced some quite nice novel features for corpus querying.
Although most of the missing features are already provided by the second backend (using a Neo4j graph database), implementing these features is scheduled for early next year, marking the final milestone before starting the alpha testing phase of the KorAP project.
In the next weeks we will prepare the frontend to support all new backend functionalities and start working on the distribution capabilities of the index.
As part of the monitoring functionalities of KorAP, I have implemented a framework to allow logging and tracing of user and service activities. Whereas that alone represents a fulfilment of a design requirement imposed by licence agreements of the containing data (text and annotations alike), the framework also includes the possibility of recording users’ query activity. Thus, KorAP’s Auditing framework allows the retrieval of query information such as the most frequently formulated queries or the data/level of annotations that are queried most frequently. Not only does this allow KorAP to create usage statistics concerning the underlying data set, but it also enables the developers to improve KorAP’s usability for feature releases according to the data retrieved.
For example, in the case of null query (queries with no result) tracking, the data can be used to extend and improve documentation or even find new traps in users’ understanding and application of query language constructs. All recorded information is subject to legal data protection and in case it is published, the user data will be anonymized. When in production mode, KorAP will inform the users about the extent of record keeping and the usage of the data.
The API was designed with the following design concepts in mind:
- to be easily extendible for future developer convenience
- separation of duties (Auditing takes place outside of the system logic via Spring proxy calls)
We’re scheduled for two appearances in December:
We’re currently busy loading the trunk/ with as much baggage as we can put together before the showdown…