Which software to use for creating a controlled vocabulary?
I need easy data input and the option to represent the hierarchy visually (Broad terms, Narrow terms, Related terms, Preferred terms). Ideally the software should be able to export data in XML-format.
Answers (3)
Costin-Sorin I.
Once QA, Always QA
Best Answers in: Using LinkedIn (6), Education and Schools (1), Government Policy (1), Compensation and Benefits (1), Personnel Policies (1), Internationalization and Localization (1), Viral Marketing (1), Quality Management and Standards (1), Professional Networking (1), Biotech (1), Enterprise Software (1), Computers and Software (1), Computer Networking (1), Information Storage (1)
Try this link. On the first page there are some interesting options
Links:
Stowe S.
Author/Writer, Principal PHP/MySQL developer on LAMP stack at Action Navigation LLC
Best Answers in: Web Development (2), Education and Schools (1), Change Management (1), Enterprise Software (1)
Drupal is built from the ground up to use taxonomy and vocabularies. I highly recommend it. It does have a steep learning curve but worth it.
Links:
Scott G.
VP, Product Management at Citypath.com
Best Answers in: Web Development (5), Public Relations (1), Professional Networking (1), Business Plans (1), Starting Up (1)
There's a bunch of options out there these days. I've personally used these two products:
Free
http://protege.stanford.edu/
Pro
http://www.synaptica.com/djcs/synaptica/
It's been about six months since I've needed to do that kind of work, and at the time Synaptica wasn't thrilling me. However, looking at their web site, it looks like they've enhanced their UI in ways that solve the issues I'd had with some of the clunky entry.
Just about anything is going to export into XML. Do you really mean XML? Or do you need OWL, etc. BT/NT/RT, etc. can be handled by a lot of tools. I'd think - as with most things - from an input - process - output perspective you often have to start with the output. If you're building a hierarchy, that's one thing. If you're building a fully multi-faceted meta data type structure, that's another. Does the production tool need to integrate with other back end tools? (That is, to handle things like user, editor or otherwise sourced taxonomy changes?)
As difficult as building a controlled vocabulary can be, planning for maintainable can be even harder.
I'd just suggest that you consider these issues as well as you look down the feature sets of tools you're evaluating.
Scott
