...
- Option 1 - Use LD-R semi-automatic annotating feature (API?) (Ali Khalili
- Pros:
- Cons:
- Option 2 - Implement our own function/service?
- Pros:
- Cons: Possibly takes more time? Reuse existing libraries?
- Option 3 - Use NLP mechanisms to find topics/keywords and add these as tags use tf-idf as a general measure to get important terms for deck/slides (Antje Schlaf)
- Pros:
- get important terms independent on recognizing DBPedia (or other) Entities, should be used in combination (get important terms, link to known entities when possible)
- terms are defined as special / important based on that they are frequent in current deck but not commonly frequent in other docs (e.g. "RDF" was often used in this deck but is not a term often used in decks in general)
- Cons:
- possibly a bit general, but for the bigger languages we can use POS-Taggers etc. to restrict to nouns if wanted
- document frequency of terms needs to be recalculated / updated and made stored / accessible for calculation
- Pros:
- Option 4 - use machine learning (Antje Schlaf)
- Pros: classification is fast when model is once trained, more time consuming model training just once necessary
- Cons:
- needs representative amount of training data for each category, which we don't have. We could use this method if enough manual labeled tags are inside system
- re-training necessary / recommended because new topics / labels are added to the growing system
- Option 5 - use topic modeling (Antje Schlaf)
- Pros:
- no manual training data needed
- calculate topics based on given collection, result: word probabilities per topic and topic probabilities per document
- Cons:
- topics have no labels (but can be manually labeled based on the resulting topic words or just present a word clowd per topic for the user which might be ok as well)
- not sure how to deal with growing collection. recalculation from time to time recommended, recalculation can lead to different topics also for older data
- Pros:
- Other options?(Ali Khalili , Roy Meissner , Mariano Rico , Antje Schlaf , Luis Daniel Fernandes Rotger )
- also important: language info probably required for all options, thus: automatic language recognition required to not rely on users setting correct language per deck (Antje Schlaf)
- Option 1 - Use LD-R semi-automatic annotating feature (API?) (Ali Khalili