User Tools

Site Tools


g2:choosing

Back to G2 main

Choosing a glossary-type module

None of the glossary modules is intended as a plug-in replacement for the original glossary module already available with drupal since its humble beginnings. Each of the alternatives was designed for slightly different needs, and this page is here to help you choose which module you should probably be using, or if you should really write your own. Lexicon evolved from glossary to accomodate yet another set of requirements, and glossify started with needs similar to glossary, but evolved to a much more diverse set of features; only those relevant to glossaries should be listed here.

Left-to-right order by date of creation. Empty cells means info not yet available. Please contribute !

TODO: import “features discussion” from the 2008 glossary comparison table, which updated the very obsolete http://drupal.org/node/266511, currently unavailable for edit except to members of the Drupal doc team due to the Full HTML format, but has now become partly obsolete itself. The 2008 chart is now imported.

TODO: document the new Atrium Glossary.

Feature Glossary G2 Glossify Lexicon G2 Refactoring Atrium Glossary
Drupal-related
Drupal 7.x No Yes No(t yet) Yes Yes No
Drupal 6.x Yes Yes Yes Yes No Yes
Drupal 5.x Yes Yes Yes No No No
Drupal 4.7.x Yes Yes No No No No
Drupal 4.6.x Yes No No No No No
Earlier Drupal versions Yes No No No No No
AJAX No Some autocompletion
Storage terms nodes, 1 content type nodes (types ?) any entity
Revision support No core core
Simpletest No A few Yes
Services provided
multiple glossaries on one site Yes No No Yes
RSS feeds on entries core No core (?)
RSS feeds on additional vocabularies No core core core
classify entries No core taxonomy core taxonomy core fields
commenting on entries No core core core, only on node storage
private editorial information No Builtin Use CCK core fields
alphabar maintenance automatic manual defaults + override
remote glossaries No Yes, limited Yes
steganographic content protection No Yes
RDF information No Yes
i18n
Translation template supplied Yes Yes
Multilingual blocks No
Translatable content Use i18nterms Use i18ncontent Use i18ncontent
Feature blocks
Alphabar No Yes Use Views Default View
Daily Yes Yes Use Views Default View
Latest No Yes Use Views Default View
Random Yes Yes Use Views Default View
Search glossary Yes No No Yes
Content filtering
Input, automatic Yes No No Yes
Input, automatic, stop list Single language No No i18n support
Input, explicit No Yes, dfn element No Yes, custom element
Output, automatic No No Yes
auto “title” on links No No Teaser / Disambiguation
Disambiguation pages n.a. Yes, limited default + override
Disambiguation targeting in links n.a. No Yes, on explicit
3rd party integration
Quality Agent No No Yes
Views: basic core core + specific core + specific
Views: default views No No Yes
Wikipedia No No Yes, with i18n
Zeitgeist No No Yes
Performance
memory needs/number of entries O(n) O(1) O(n) (?)
speed on small glossaries faster slower slower
speed on large glossaries slower with size remains constant slower with size
Themeing
- home page core
- search form Yes core core
- node overview Yes core core
- definition fields n.a. Yes Use CCK core fields
- each feature block n.a. Yes Use Views
Specific class on glossary links Yes Yes
Implementation Templates Theme functions Templates
Developer features
XML-RPC API No alphabar
latest
top
random
word of the day
No
Web services security n.a. IP-based access control
throttling
n.a.
UI module separate from Data API No No Yes

Obviously, in all cases, a “No” actually means: “roll your own”, as in all Open Source software.

Documentation

g2/choosing.txt · Last modified: 2011/02/22 08:25 by fgm