It's definitely true that dropdowns won't work for LCSH, Getty, or other large, standard vocabularies. But I think a lot of projects would be happy with a "lite" version of a controlled vocabulary plugin just to speed up the data entry process and maintain some internal consistency in their homegrown metadata conventions. So, maybe this is two plugins rather than one.
On Apr 21, 2010 9:56 PM, "Ethan Gruber" <ewg4...@gmail.com> wrote:
Something that I think is really important to note is that controlled vocabulary indices may have tens or hundreds of thousands of entries, even millions. A solution for populating a drop down menu from LCSH, for example, won't work. It's not scalable enough. There are close to 400,000 LCSH terms, and the Library of Congress doesn't maintain a service by which you can access terms on the fly. LCSH terms are publicly available in an rdf file that is 400-500 megabytes, though if you parse out only the term, id, and creation/modified dates, you can whittle the size down to less than 75. Even still, you need to develop a process by which the vocabulary list is queried for terms that match your inputted keystrokes, which is why I recommend autosuggest for controlled vocabulary terms if you are dealing with LCSH, Getty geographical place names, or other large collections of terms.
On Wed, Apr 21, 2010 at 8:45 PM, Patrick Murray-John <pgos...@umw.edu> wrote:
Thanks, Shirley. That's exactly the kind of input we need.
On Apr 23, 2010 10:31 AM, "Jim Safley" <jims...@gmail.com> wrote:
> Am I right in thinking that the filterItemSave method could yield odd
> results if someone hits t...
You should try the code I provided. Just make a directory in plugins/
called ControlledVocab, place the code in plugin.php, and install it.
When adding an input, you'll find a strange warning error (something
we have to straighten out), but I think you'll find the results to be
typical and expected.
> I'm a little concerned about the user not having a signal about which value
> is saved if they cr...
I agree that ambiguity can be problematic in the current setup, and I
will never underestimate the ability of users to create oddities.
Though I wonder how far we should go to hold their hand. Data input is
a learned task, requiring trial and error. But I digress...
> So, what do you think of this tack on it. Using the itemFilterForm method,
> insert a <select> th...
That's a good tack, one that will certainly reduce ambiguity. I think
we'll request a simple controlled vocabulary plugin from the
developers during the May playdate. It would be a good problem to hack
You received this message because you are subscribed to the Google Groups "Omeka Dev" grou...