Difference between revisions of "Search"
Jump to navigation
Jump to search
(fix image) |
(Adds link to Flickr) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 7: | Line 7: | ||
=== Semantic Web Search === | === Semantic Web Search === | ||
| − | [[Image: | + | [[Image:Logo.png|thumb]] |
# http://swoogle.umbc.edu Semantic Web Search | # http://swoogle.umbc.edu Semantic Web Search | ||
=== Searching for Multimedia === | === Searching for Multimedia === | ||
| − | + | When searching for unrestricted graphics content, it is hard to beat the huge commons of Wiki commons. Use the search engine on toolserver.org to find the images or other media you're looking for. http://toolserver.org/~tangotango/mayflower/ Any image found there can be used under the terms of the (creative commons) license listed -- meaning it can be used here or on your website. | |
| − | |||
| − | When searching for unrestricted graphics content, it is hard to beat the huge commons of | ||
Flickr also has millions of images licensed under creative commons licenses: https://www.flickr.com/creativecommons/ | Flickr also has millions of images licensed under creative commons licenses: https://www.flickr.com/creativecommons/ | ||
| Line 19: | Line 17: | ||
=== Native (Application) Search === | === Native (Application) Search === | ||
Applications such as this wiki (runs on MediaWiki), and CMS systems (e.g. Drupal) obviously know their own content. So, usually it would suffice to make use of the search facilities built in to the application. However, this doesn't always ring true -- especially when you consider that search as a service in it's own right is probably more powerful than search as a "feature" that is independently tacked on to each application in your stack. | Applications such as this wiki (runs on MediaWiki), and CMS systems (e.g. Drupal) obviously know their own content. So, usually it would suffice to make use of the search facilities built in to the application. However, this doesn't always ring true -- especially when you consider that search as a service in it's own right is probably more powerful than search as a "feature" that is independently tacked on to each application in your stack. | ||
| − | |||
| − | |||
Users and Implementors of MediaWiki, see [[MediaWiki/Search]]. | Users and Implementors of MediaWiki, see [[MediaWiki/Search]]. | ||
| Line 46: | Line 42: | ||
=== Search your code. Can you 'grok' it? === | === Search your code. Can you 'grok' it? === | ||
[[File:Opengrok-analysis.png|right]] | [[File:Opengrok-analysis.png|right]] | ||
| − | LXR The [http://lxr.linux.no/ Linux Cross Reference] is probably the first widely used web-based code cross-reference tool. Along came [http://opengrok.github.io/OpenGrok/ OpenGrok] which started out as a project at Sun (which was bought by Oracle) and now the project lives on its own in the open. OpenGrok is '''lightening fast''' and is actively maintained as an open source project on GitHub. By the way, the underlying search is powered by SOLR. Meanwhile, [http://kohsuke.org/ Kohsuke Kawaguchi] the magic man behind Jenkins ( | + | LXR The [http://lxr.linux.no/ Linux Cross Reference] is probably the first widely used web-based code cross-reference tool. Along came [http://opengrok.github.io/OpenGrok/ OpenGrok] which started out as a project at Sun (which was bought by Oracle) and now the project lives on its own in the open. OpenGrok is '''lightening fast''' and is actively maintained as an open source project on GitHub. By the way, the underlying search is powered by SOLR. Meanwhile, [http://kohsuke.org/ Kohsuke Kawaguchi] the magic man behind Jenkins (Hudson), also wrote [http://sorcerer.jenkins-ci.org/ Sorceror] which understands semantics in Java. Sadly, Sorceror code hasn't been touched in 4 years and doesn't seem to be an active project - but for Java codebases, it's probably still a good option. |
=== Browser extensions / Web Apps === | === Browser extensions / Web Apps === | ||
