I would really like to see two features in Gallery 3 that could probably be done easily with modules.
The first is tag aliases. So let's say someone searches for a tag called clothing but the tag used in the gallery is clothes. If the alias is setup, it will show the results for clothes.
I'd also like to see another feature that would be useful for people posting artwork instead of photos and that would be an artist field that could allow for multiple names and aliases on them too would be nice. While I do know there is a custom fields mod, I want the artist name to be clickable so it could show all the artwork done by that particular artist.
Hopefully these things are easy to implement.
Posts: 1857
I like the idea of tag aliases. Requires a little more thought though; I'm not sure that it can be done as a module, but maybe. (I'm thinking about what would happen if you set up an alias, but also later add a tag with the same name; maybe one of the two just gets ignored?)
For the artists names: If the custom fields module works for you, you can make it clickable. Easiest way would be to make the artist names tags and use the tag albums module, but maybe that's not what you're after? http://codex.galleryproject.org/Gallery3:Modules:tag_albums
Posts: 28
For tag aliases one of the aliases would be set as primary so if someone tags a picture clothing it will automatically change to clothes.
Tag albums would only work if all the artwork by that artist is in one album which wasn't what I was planning. Albums would be type of art... unless I'm misunderstanding this module.
Posts: 814
Just adding a couple of thoughts on the alias tag feature... again just some thoughts
If one were to have to iterate over a list of words, the search would take a long time
-so-
* When tagging an image, the tag module would need to 'scan' the aliases to determine if one exist, if so, it'd need to change to the 'master' tag and tag the image, if not, add it as a new master tag and tag the image - this would require substantial rework of the tagging module
* Search would need to look to see if the searched tag is a 'master' tag, or an alias, then if alias, only search for 'master' tag - I don't recall a search 'hook' that would allow us to intercept the search, thus requiring substantial core rework as well
* When adding aliases, the module would have to search if exists in alias list, or as a master, and then handle accordingly - relatively easy enough probably
Posts: 1857
Tag aliases: With the clarification of your last post, this will be more complicated than I originally thought. After reading the 1st post, I thought you just wanted to affect searches; changing what happens when you actually tag a photo, well, that's another matter (as @jnash has commented on).
Tag albums: Not sure I'm understanding. I though that the point of the module is that it is dynamic. You tag items with tag1, tag2, etc and it dynamically creates and updates an album for that tag. So, if you want tag albums based on types of art, you'd make a tag for each type of art and use them accordingly. Did I miss something?
Posts: 28
Basically, I'm trying to make an art site with something like the Booru script but I prefer the look and feel of Gallery (plus Booru lacks any bulk upload option, it looks gross, and doesn't even support albums.)
The problem with tag albums is it merges the artist tags with all the other tags which isn't what I want.
Would there be a way to duplicate the tags module to make multiple sets of tags. For instance, content tags, artist tags, etc? I don't know PHP but maybe it's time to learn..
Posts: 1857
Booru script: Never heard of it and I don't know what it does.
Almost (almost) anything is possible. The limitation is going to be that whole "I don't know PHP" part. Honestly, I'd probably advise against starting a new module until Gallery 3.1 is released anyway because there will be significant changes that may affect module operation in some cases.
That would only happen on the tags list/cloud. I don't know enough about what you're doing to know why that would be a big deal. If it is a huge deal (and you want to spend some time learning a bit of PHP), you could prefix all of the artist tags with something (e.g. "artist_") and edit most of Gallery to not include those tags in clouds/lists/etc. (That could actually be a solid start to working out a module.)
If it's super important to you, and you're looking to get it done right away, you could also post in the services forum (marketplace) to see if anyone is willing to do it for a fee: http://galleryproject.org/forum/65