Candidates for Plugins / Extensions / Services #280
Replies: 6 comments 4 replies
|
name: QCA-AID |
|
name: lang extract |
|
name: Gabriel |
|
So far, these are all complex tools with a lot of different workflows and possible use cases. Therefore we probably need to have a multi-layer approach. At the ground level layer there is a tool like GABRIEL. On a second layer there should be a template based setup of typical workflows fitting into QDA. Therefore we would implement the integration of GABRIEL on a ground layer and then provide a GABRIEL-analysis "platform", just like we have a wordcloud analysis platform which does different types of wordclouds. |
|
name: presidio |
|
The people choosing the name definitely had a kind of special humor: QualiAnon is also a tool for anonymization https://www.qualiservice.org/de/helpdesk/webinar/tools.html - it has a doi https://doi.org/10.26092/elib/2525 and a github repo https://github.com/pangaea-data-publisher/qualianon - it is a java app, so it should be rather straightforward to isolate the relevant logic and provide it as a service - imho a PERFECT student group or MA project! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Until we have a full features plugin architecture, we should consider some viable candidates, that we should consider when analyzing requirements and designing the plugin architecture + protocols.
How to add candidates?
Manage candidates
All reactions