Something like that would solve the problem that is listing the same tag twice: FUN vs fun.
On a site where you only have one author, I can see this as being extremly helpful. But on a site with many authors you could run into problems. B.Ball : Basketball or Baseball?
Yeah, it’s gonna have to go into v1.1, right now I can’t get it to work as intended across all functions.
Will sort that out later. v1.0 coming up later today, just have to make a few last minute adjustments.
Edit: here’s v1.0, some things might be missing but I’ve tried to make it useful for a first release.
Note: The docs are severely lacking. Really. Haven’t had time to write it, nor will I anytime soon.
I’ll support the module in this thread instead for the time being.
Things to come in v1.01: —————————————-
You will be able to use spaces in keywords (key-sentences?)
Exporting a backup of keywords into a textfile / Import keywords from a backup textfile
Adding multiple keywords separated by pipe
Proper manual that’s actually useful.
Things that are in dev for the future: —————————————————————
Suggested Keywords, AJAX magic in the add keywords form: to add keywords without duplicating for different spellings.
Recommended Keywords, an algorithm for extracting recommended keywords automagically. (got a working proof of concept!)
Related Entries, AJAX wizardry for hovering over a related entries link and getting an list of related entries.
Keyword Module configuration page, where you can choose to disable Recommended Keywords and such..
I’ve downloaded and installed this module - so far so good! I had a look around the CP interface for it as well - looks great! And, the import of my keywords from the old Keywords module worked perfectly. I was expecting some problems with keywords containing spaces, but it worked without a hitch. However, before I begin using it for real, I had a few small questions:
1. I’m a little bit unclear on the concept of Layers. Am I correct in thinking that these are basically “groups” of keywords? Like, I could have one group for my main weblog, and another group for my reviews weblog? Or one group for all keywords related to my friends and family, and say, another group with keywords related to online stuff? Are they sort of like categories for keywords?
2. Earlier in the thread it was mentioned that there would be several different ways of adding keywords to a post. At the moment, I can only see one, the CP interface. Any word on how to add this to the Stand Alone entry form or as a hack to the main Publish page?
3. When I go to Layers > View Layer, I get a long long list of all keywords and what posts they were assigned to. However, it lists each seperately, like, if I’ve used a keyword 20 times, it will be listed 20 times on that page. To make it easier to view and manage, would it be possible to only list each keyword once, and list all the entries that use that keyword as a comma-seperated list (ie, Entry1, Entry2, Entry3, etc)? Also, would it be possible to optionally sort the keywords alphabetically here? The order seems to be chronological, but it’d be awesome to have the option of viewing them alphabetically there as well.
4. It was mentioned that development on the other Keywords module stopped because it was too resource-intensive. How does this module manage to take up less keywords? Are you using less MySQL queries for the listing etc of the keywords? I am very curious to hear some of the technical details.
1. Yes, layers are like global categories for keywords.
They are not restricted to any x weblog(s).
Because the parameter “group” has already been used for defining member groups (and because I think “layers” describes the feature better) I decided to go with “layers”.
You can use layers like categories or whatever.
A quick example:
Instead of keywording an entry “holliday”, “bulgaria”, “2005”
..you could keyword it like so:
layer: “events”, keyword: “hollidays”
layer: “locations”, keyword: “bulgaria”
layer: “years”, keyword: “2005”
It also let’s you restrict keyword matchings to specific layers.
2. Phoebe has made an hack for the publish page, but since EE v1.4 is featuring Extensions,
I’m waiting to see if they might let me do the trick without hacks.
3. The reason it’s done that way now is because I just needed something quick. I’ll think about reworking it for future updates. Thanks for the FR!
4. The main difference is that the plugin used a single field with piped keywords, thus having to process that piped list of keywords on every hit.
Phoebe came up with the solution to use a separate indexed table for keywords and running a quick query for pulling out the keywords with minimal php processing.
I did some testing (20 keywords per entry in 5.000 entries, 6 chars per keyword) to find out the speed vs table size ratio.
I was hoping for the sake of organisation that we could use one table with the keywords and another table with all the relations between entries and keywords,
but the speed gain from using a single table with repeating keywords was to big to dismiss..
We also have a cool feature called “threshold” that the plugin didn’t have.
It works like this;
If entry_id 1 use the keywords “fish”, “chicken” and “dog”
and entry_id 5 is uses the keywords “fish” and “dog”
and entry_id 7 is uses the keywords “chicken”, “dog” and “cat”
Using threshold=“1” would make all three entries related, because the keyword “dog” is shared by all three entries.
Using threshold=“2” would make entry_id 1 related to both entry_id 5 and entry_id 7, because at least two keywords are shared between entries.
Using threshold=“3” would not make any entries related, because no two entries share three keywords.
Hm.. did that make any sense?
If not let me know and I’ll try to elaborate.
That’s great, thanks Andy! Your answers cleared everything up. :D If I have any other questions or feature requests that I might discover as I start using the module, I’ll be sure to let you know in this thread. Thanks again so much to you and Phoebe for all your work!!!
(I just came back from vacation in Austin TX, visiting a friend I hadn’t seen in 3+ years. Had excellent tex-mex, hung out with other snarky people, bought more books (because that’s always good), had a great time. Now, I get to play catch-up…)
It’s available!! Excellent!! I’ll play with it this evening and come worship at your feet some more :D
Just stumbled across this new module you’re creating and can’t wait to try it out on our site. This is going to make it tons easier for readers of our site to find relevant articles in categories they’re interested in, rather than categories we tell them to be interested in. It’s funny how photo galleries have already jumped on tags—would be amazing to have a way to integrate keywords on articles and photos seamlessly.
I’m adding one thing to the list of things coming in the (near or distant) future;
- Abillity to keyword anything in the DB.
If it’s available in the EE DB, it will be keywordable.
Ie: Forum module entries will be keywordable and so will Gallery module images, to name a few ideas.
The only snag is that it might not be possible to use the module in the forum module templates, haven’t looked into that yet.
Oh yeah almost forgot, I’ve changed my username and email too. No more OS_Andy.
This looks really cool! Must find time to download and play!
But no more ‘OS_Andy’?! Argh! I’ll be wandering around for days, wondering who is this ‘ExpressionEngineer’ person with all the good tech posts yet I have never heard of them.
But no more ‘OS_Andy’?! Argh! I’ll be wandering around for days, wondering who is this ‘ExpressionEngineer’ person with all the good tech posts yet I have never heard of them.
Andy, I have just run into a strange problem with the exp:keyword:entries tag.
I have a tag cloud on my site, when you click on a keyword in the tag cloud, it takes you to a page that lists all entries assigned to that keyword. I list those entries in an unordered list, with their titles linking to the individual archive pages.
Here is the coding I was using that did not work - it just returned empty <ul> tags:
The culprit here seems to be the backspace parameter. If I leave it out or change it to 0, I only get empty tags. If I insert a space after every item and change it to backspace=“1”, it works OK.
Lastly, a small feature request: would it be possible to make {entry_date} available inside this {exp:keyword:entries} tag? Whenever I list all entries assigned to a keyword, I like to display the date alongside the entry title, so people can see how old the entries are.
Another feature request that I am noticing more now that I am using the module daily:
Would it be possible to add more than one keyword at a time? Like, when I go into the Keyword Module, and click an entry title to add keywords, I can only type in one keyword at a time into the text box. I have to click the submit button, wait for the page to load, scroll down, and enter a second keyword. This gets a bit tedious if I want to add 5 or 6 keywords.
Would it be possible to add the ability to type a string of keywords into the box, and have them all added as seperate keywords (perhaps seperated by comma, semi-colon or pipe or something)?
Edited to add: I was wondering, would it be very difficult to make all fields available in the exp:keyword:entries tag? Right now, only {entry_id}, {title}, {url_title}, and {category_id} are available - but I’d love to have my custom fields in there as well. Doable? Or is this very difficult/time consuming to do?
Or, alternatively, would it be possible to enable the use of the {exp:query} tags inside the exp:keyword:entries tag? Then I can just pull all my custom fields out of the database myself.
