We are having a similar metadata problem at work. We are hoping to solve it by requiring users to categorize their content. We are providing them with a controlled vocabulary list and asking them to enter up to three subject codes. The goal is to have these categories drive a search engine and a browse by topic feature.

Of course, there is the problem of not being sure if they picked the correct subject codes. There doesn't seem to be any way to guarantee this without human intervention. Also developing a controlled vocabulary list that meets every person's needs is hard as hell.

One solution is to have global metadata, data that should be collected about every file(node) and local metadata, info that is specific to a section or content type. This allows us to fine tune our metadata without putting a huge burden on the user. Having global and local metadata also cuts down on the size of any controlled vocabulary list.

The sections of the Q&A section could be a good start for subject codes(global metadata). The goal of browsing by topic is a good one and it would compliment the Super Search nicely.

The work of the Dublin Core and the W3C (RDF) could provide some good ideas and blueprints for this topic.

Get Strong Together!!

In reply to Re: topic-linking for nodes by aardvark
in thread topic-linking for nodes by princepawn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.