Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
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":



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others imbibing at the Monastery: (2)
As of 2024-04-25 20:31 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found