A customer had an existing Drupal powered Intranet site. They were excited to tell us about a project they were building for a collaborative workspace for a group of researchers that was customized to manage Karyotyping images. The collaborative workspace would tie together a number of collaboration tools they already had in use - Drupal, Jumper 2.0, and DSpace.
A researcher would create an image that needed to be stored in Dspace. The image would be uploaded to the DSpace repository. The workflow they were building would manage this process via scripts. The Drupal search module was customized to let users search for specific image thumbnails on the Intranet site. Drupal is chiefly focused on handling HTML content, so Gallery2 was installed to generate thumbnails on a preview page and extract embedded metadata.
Drupal would push the image to the DSpace repository and store the metadata and thumbnails in the Gallery. When images are recorded, Drupal offers users the option to include additional related tag objects created in Jumper 2.0. When users record a new image they have an option to tag the document or image using the Jumper 2.0 tag engine. The image is then assigned a unique identifier in the repository and published in a news feed.
The new image is picked up via the published feed and stored in the Gallery module of the research project's Drupal site. Included in the feed are the image, metadata (including the unique identifier), tag profile with pointers to any related objects. Another researcher learns that the new image is available to examine. A module was written to provide a workflow for the feeds so that the new items showed up in a block in "my workspace," and an was email generated by the notify module. Other researchers could click on a reference link to view the full res image, compare the image in the Gallery module to other images, they could click on reference links to related papers published in Connotea, they could read and edit the tag profile with new annotations, comments, or notes to build more knowledge around the image.
Using Jumper 2.0 tagging there is now a rich set of metadata associated with the image. The new metadata was published as feeds and picked up for inclusion in the DSpace repository housing the original archived image. This publishing cycle was ongoing for the life of a specific research project. The rich metadata that Jumper delivers provided the context, meaning and value to the image that was missing in traditional metadata. Critical provenance information was provided as well as links to related images or published papers. All of this made the search results more relevant.
Tuesday, July 27, 2010
Friday, July 23, 2010
Proposing an Open Index Initiative
Many of the customers who download Jumper are using it for personal search. They are using it themselves, or in a small company, or between a few colleagues. Jumper has many benefits that make it an ideal personal search engine, however, if you are using Jumper in this way you are missing one of its big benefits – collaborative sharing of resources. In a larger community of uses with a shared interest or profession the number of searchable resources grows rapidly and the inherent value of Jumper search increases accordingly.
In an effort to facilitate resource sharing among the many customers who use Jumper for personal search we are proposing an Open Index initiative.
Jumper will make a shared index database available for download on Sourceforge under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported license. This Open Index will be built by users like you, who share your tag profiles with other users, who in turn share their tag profiles with you. This collaborative initiative will be aggregated by Jumper in a central Open Index that will be available for download on Sourceforge.
This means that you can share and change the index database as you choose.
• to Share — to copy, distribute and transmit the work
• to Remix — to adapt the work
Under the following conditions:
• Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
• Noncommercial — You may not use this data directly for commercial purposes. You cannot resell or repackage this data for commercial benefit. You cannot commercially benefit by providing access to this data. The intent for use is that any benefit will only be derived indirectly by using this data to search for resources that may provide a commercial benefit as a result.
• Share Alike — If you alter, transform, or build upon this work, you may distribute the resulting work only under the same license to this one.
It is important to understand that when you contribute your resources to the common index for the general good of all that it can only be used under these license guidelines.
There are two ways you can easily contribute.
You can export your Jumper index database and send the flat file to us via Email at Open Index
Or you can add individual resources to the open index via the Open Index form.
In an effort to facilitate resource sharing among the many customers who use Jumper for personal search we are proposing an Open Index initiative.
Jumper will make a shared index database available for download on Sourceforge under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported license. This Open Index will be built by users like you, who share your tag profiles with other users, who in turn share their tag profiles with you. This collaborative initiative will be aggregated by Jumper in a central Open Index that will be available for download on Sourceforge.
This means that you can share and change the index database as you choose.
• to Share — to copy, distribute and transmit the work
• to Remix — to adapt the work
Under the following conditions:
• Attribution — You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).
• Noncommercial — You may not use this data directly for commercial purposes. You cannot resell or repackage this data for commercial benefit. You cannot commercially benefit by providing access to this data. The intent for use is that any benefit will only be derived indirectly by using this data to search for resources that may provide a commercial benefit as a result.
• Share Alike — If you alter, transform, or build upon this work, you may distribute the resulting work only under the same license to this one.
It is important to understand that when you contribute your resources to the common index for the general good of all that it can only be used under these license guidelines.
There are two ways you can easily contribute.
You can export your Jumper index database and send the flat file to us via Email at Open Index
Or you can add individual resources to the open index via the Open Index form.
Saturday, April 17, 2010
Jumper and Sphinx - integrating the best of both worlds
We had a customer who requested some direction on integrating the Jumper 2.0 tagging feature into a number of very large distributed databases. The customer had just implemented the Sphinx search engine on each of these databases.
Many of these SQL databases contained very large numbers of tables. The primary challenge was that many of these tables contained cryptic table and column names that made it very difficult to interpret exactly what the data was in the tables.
They wanted to integrate the Jumper 2.0 bookmarking engine into the Sphinx search engines so that users could apply knowledge tags to the legacy database tables. In this way users could search locally for data and then tag the data they had searched with relevant knowledge tags. In the initial design meeting it was determined that integrating the Jumper tagging fields directly into the Sphinx search interface would be the best approach and storing the tags to a central Jumper mySQL index. Provided below is a quick example of this integration.
The first thing created was a simple form in HTML.
<-html->
<-head->
<-title->Jumper Tagging Fields<-/title->
<-/head>
<-body->
<-form method="post" action="jumper_update.php">
User Name:<-br />
<-input type="text" name="creator_id" size="10" /><-br />
Table Name:<-br />
<-input type="text" name="title" size="40" /><-br />
Description:<-br />
<-input type="text" name="body" size="300" /><-br />
Database Hostname:<-br />
<-input type="text" name="url_title" size="255" /><-br />
Keywords:<-br />
<-input type="text" name="meta_keywords" size="200" /><-br />
Database Location & Access:<-br />
<-input type="text" name="meta_location" size="200" /><-br />
Realted Data:<-br />
<-input type="text" name="meta_link" size="200" /><-br />
Type of Data:<-br />
<-input type="text" name="data_type" size="30" /><-br />
Date:<-br />
<-input type="text" name="date_posted" size="30" /><-br />
// Next we need to add the submit button to the web page. //
<-input type="submit" value="Update Database"
<-/form>
<-/body>
<-/html>
The next step is to create jumper_update.php file. This will update the database with the new knowledge tags that have been applied to the database tables. Create a new file called jumper_update.php
$creator_id = $_POST['creator_id'];
$title = $POST['title];
$body = $POST['body'];
$url_title = $POST['url_title'];
$meta_keywords $POST['meta_keywords'];
$meta_location $POST['meta_location'];
$meta_link $POST['meta_link'];
$meta_datatype $POST['meta_datatype'];
$date_posted $POST['date_posted'];
mysql_connect("localhost", "username", "password") or die ('Error: ' . mysql_error());
mysql_select_db("s_jmp_entry");
$query="INSERT INTO Table (id, creator_id, title, body, url_title, meta_keywords, meta_location, meta_link, meta_datatype, date_posted)VALUES ('NOT NULL','"$creator_id."','"$title."','"$body."','"$url_title."','"$meta_keywords."','"$meta_location."','"$meta_link."','"$meta_datatype."','"$date_posted."')";
mysql_query($query) or die ('Error updating database');
echo "Database Updated With: " .$creator_id. " ".$title." "$body." "$url_title." "$meta_keywords." "$meta_location." "$meta_link." "$meta_datatype." "$date_posted ;
?>
We are working on inserting the knowledge tags directly into the Sphinx index so that users can search data by both full-text and knowledge tags to improve discoverability of the legacy data. We will keep you posted.
-apology for the all the hyphens it was the only way to get the blog to accept the HTML.
Many of these SQL databases contained very large numbers of tables. The primary challenge was that many of these tables contained cryptic table and column names that made it very difficult to interpret exactly what the data was in the tables.
They wanted to integrate the Jumper 2.0 bookmarking engine into the Sphinx search engines so that users could apply knowledge tags to the legacy database tables. In this way users could search locally for data and then tag the data they had searched with relevant knowledge tags. In the initial design meeting it was determined that integrating the Jumper tagging fields directly into the Sphinx search interface would be the best approach and storing the tags to a central Jumper mySQL index. Provided below is a quick example of this integration.
The first thing created was a simple form in HTML.
<-html->
<-head->
<-title->Jumper Tagging Fields<-/title->
<-/head>
<-body->
<-form method="post" action="jumper_update.php">
User Name:<-br />
<-input type="text" name="creator_id" size="10" /><-br />
Table Name:<-br />
<-input type="text" name="title" size="40" /><-br />
Description:<-br />
<-input type="text" name="body" size="300" /><-br />
Database Hostname:<-br />
<-input type="text" name="url_title" size="255" /><-br />
Keywords:<-br />
<-input type="text" name="meta_keywords" size="200" /><-br />
Database Location & Access:<-br />
<-input type="text" name="meta_location" size="200" /><-br />
Realted Data:<-br />
<-input type="text" name="meta_link" size="200" /><-br />
Type of Data:<-br />
<-input type="text" name="data_type" size="30" /><-br />
Date:<-br />
<-input type="text" name="date_posted" size="30" /><-br />
// Next we need to add the submit button to the web page. //
<-input type="submit" value="Update Database"
<-/form>
<-/body>
<-/html>
The next step is to create jumper_update.php file. This will update the database with the new knowledge tags that have been applied to the database tables. Create a new file called jumper_update.php
$creator_id = $_POST['creator_id'];
$title = $POST['title];
$body = $POST['body'];
$url_title = $POST['url_title'];
$meta_keywords $POST['meta_keywords'];
$meta_location $POST['meta_location'];
$meta_link $POST['meta_link'];
$meta_datatype $POST['meta_datatype'];
$date_posted $POST['date_posted'];
mysql_connect("localhost", "username", "password") or die ('Error: ' . mysql_error());
mysql_select_db("s_jmp_entry");
$query="INSERT INTO Table (id, creator_id, title, body, url_title, meta_keywords, meta_location, meta_link, meta_datatype, date_posted)VALUES ('NOT NULL','"$creator_id."','"$title."','"$body."','"$url_title."','"$meta_keywords."','"$meta_location."','"$meta_link."','"$meta_datatype."','"$date_posted."')";
mysql_query($query) or die ('Error updating database');
echo "Database Updated With: " .$creator_id. " ".$title." "$body." "$url_title." "$meta_keywords." "$meta_location." "$meta_link." "$meta_datatype." "$date_posted ;
?>
We are working on inserting the knowledge tags directly into the Sphinx index so that users can search data by both full-text and knowledge tags to improve discoverability of the legacy data. We will keep you posted.
-apology for the all the hyphens it was the only way to get the blog to accept the HTML.
Wednesday, March 31, 2010
A new model of a Trusted Web and Decentralized Search
Ask most users and they will tell you in no uncertain terms that enterprise search sucks. Why is it generally so frustrating? Why does it fail to meet most user needs? Why can’t it find the information you are looking for?
Because it is a general search tool when what you are often looking for is something highly specialized. The result of a general tool and a specialized need is an extremely frustrating user experience. Finding the right information is exactly like a finding a needle in a haystack. You need to get lucky.
But good search should not be about getting lucky. Although we could all use a little luck. It should be about delivering on your unique needs. When you have a specialized need you reach for a specialized tool. One that is perfectly adapted to the job at hand. That is exactly what a personalized search engine delivers.
A Personalized Search Revolution
Jumper is a revolution in Enterprise Search precisely because it is a personalized, specialized, and trusted engine. It contains an index of searchable information that has been provided by trusted colleagues, who share a common interest, and are working toward a common goal.
At Jumper we believe that each person’s ability to drive trust into every search is the animating force that moves us from centralized search paradigms to a new, decentralized one. In this new model, we will be able to search better because trusted communities are doing search for you. They collectively share this highly specialized information and knowledge to build a better personalized search engine.
We can better trust search results because people we know had good experiences with specific information resources and then share that experience with others. We get better search results because the community of users that built the search index is like us; they share our interests, our passions, and speak our language.
Personalized search is discipline specific, much like vertical web search engines, it is focused on your specific industry or research. However, it delivers universal search across all information sources allowing you to learn about new things and ideas based on personal recommendations from a community of people who are similar to you.
The New Model of Trusted Search
Traditional monolithic enterprise search is limited by its very generality, its one-size-fits-all indexing approach, its rigid global taxonomies, its ambiguous metadata. The biggest problem is changing semantics and antiquated metadata. The differences between one word or acronym, and the other, can vary widely by user, profession, location, or industry. The word web, for instance, can have entirely different meanings in different contexts. Even if, across all different forms, locations and languages, you are looking for the word web, what is the context you want to place it in? By personalizing search the context is always relevant and decided by the community of users.
This new proactive model of creating trust is not some future, far off concept. It is happening right now with Jumper 2.0. It delivers personalized, specialized, and trusted search precisely because it is easily deployed to smaller groups of users. It is light-weight, portable, web-based, and license-free. It is easily customized and adaptable to meet the unique needs of departments and divisions, research groups and project teams. It is a point solution search approach that is highly flexible and very dynamic.
Jumper leverages social knowledge tagging that makes it easy and intuitive for users to apply tags, descriptions, definitions, classifications, almost anything you want to apply to make information easier to find and more usable. This reputation system is based on user input and expertise that allows us to better trust verified content, media, or data and to rely on the knowledge attached to that information resource. We use trust based rating systems to determine what information is considered the best and what is not worth your time.
The explosive growth of Jumper community search demonstrates how people are frustrated with traditional enterprise search. All they really want is an effective search tool. One that works for them. They are proactively creating trusted search through shared interests.
Because it is a general search tool when what you are often looking for is something highly specialized. The result of a general tool and a specialized need is an extremely frustrating user experience. Finding the right information is exactly like a finding a needle in a haystack. You need to get lucky.
But good search should not be about getting lucky. Although we could all use a little luck. It should be about delivering on your unique needs. When you have a specialized need you reach for a specialized tool. One that is perfectly adapted to the job at hand. That is exactly what a personalized search engine delivers.
A Personalized Search Revolution
Jumper is a revolution in Enterprise Search precisely because it is a personalized, specialized, and trusted engine. It contains an index of searchable information that has been provided by trusted colleagues, who share a common interest, and are working toward a common goal.
At Jumper we believe that each person’s ability to drive trust into every search is the animating force that moves us from centralized search paradigms to a new, decentralized one. In this new model, we will be able to search better because trusted communities are doing search for you. They collectively share this highly specialized information and knowledge to build a better personalized search engine.
We can better trust search results because people we know had good experiences with specific information resources and then share that experience with others. We get better search results because the community of users that built the search index is like us; they share our interests, our passions, and speak our language.
Personalized search is discipline specific, much like vertical web search engines, it is focused on your specific industry or research. However, it delivers universal search across all information sources allowing you to learn about new things and ideas based on personal recommendations from a community of people who are similar to you.
The New Model of Trusted Search
Traditional monolithic enterprise search is limited by its very generality, its one-size-fits-all indexing approach, its rigid global taxonomies, its ambiguous metadata. The biggest problem is changing semantics and antiquated metadata. The differences between one word or acronym, and the other, can vary widely by user, profession, location, or industry. The word web, for instance, can have entirely different meanings in different contexts. Even if, across all different forms, locations and languages, you are looking for the word web, what is the context you want to place it in? By personalizing search the context is always relevant and decided by the community of users.
This new proactive model of creating trust is not some future, far off concept. It is happening right now with Jumper 2.0. It delivers personalized, specialized, and trusted search precisely because it is easily deployed to smaller groups of users. It is light-weight, portable, web-based, and license-free. It is easily customized and adaptable to meet the unique needs of departments and divisions, research groups and project teams. It is a point solution search approach that is highly flexible and very dynamic.
Jumper leverages social knowledge tagging that makes it easy and intuitive for users to apply tags, descriptions, definitions, classifications, almost anything you want to apply to make information easier to find and more usable. This reputation system is based on user input and expertise that allows us to better trust verified content, media, or data and to rely on the knowledge attached to that information resource. We use trust based rating systems to determine what information is considered the best and what is not worth your time.
The explosive growth of Jumper community search demonstrates how people are frustrated with traditional enterprise search. All they really want is an effective search tool. One that works for them. They are proactively creating trusted search through shared interests.
Monday, March 29, 2010
Happy Birthday Jumper 2.0
Today marks the one year anniversary of Jumper’s first production release. We are celebrating the open source release of Jumper 2.0 on Sourceforge (March 29th) and look forward to another exciting year.
We have achieved unexpected growth in this short span and the credit goes to all of our dedicated community members. Lots of smart people, from smart companies, are driving Jumper 2.0 forward. Since our initial launch one year ago we have over 5000 enterprise downloads. Our software is installed in some of the largest Life Sciences and Pharmaceutical organizations, Automobile and Construction equipment manufacturers, Food Product and Beverage companies, leading Universities around the globe, and several US Government agencies. Our open source software has been downloaded in over 76 countries with more downloads to China than any other country. We get more hits, downloads, and requests from China than any other country outside the US.
Jumper 2.0 is just beginning to gain recognition as a game changing software platform. Jumper has grown rapidly from department and project level deployments by rogue groups of employees frustrated with existing corporate IT solutions, to development level beta and sandbox platforms that opened peoples eyes to the power of social knowledge tagging, to full blown enterprise platforms that supplement existing Search and KM tools. Jumper wikis are popping up to provide users with support and advice and corporate IT, instead of trying to police or squash this self-help behavior, has begun to embrace it.
We look forward to becoming a significant driver of innovation in the enterprise, empowering users everywhere behind the firewall, and planning new developments to the Jumper platform in the coming year. Our community of users, supporters, and developers grows stronger every day and we anticipate the suggestions and contributions of each new member. It is your feedback that will result in new features and tools that benefit the broader community.
From all of us at Jumper thank you to the community of users who support us. Your comments, suggestions, complaints, bug fixes, and continued deployments help make for better software.
We have achieved unexpected growth in this short span and the credit goes to all of our dedicated community members. Lots of smart people, from smart companies, are driving Jumper 2.0 forward. Since our initial launch one year ago we have over 5000 enterprise downloads. Our software is installed in some of the largest Life Sciences and Pharmaceutical organizations, Automobile and Construction equipment manufacturers, Food Product and Beverage companies, leading Universities around the globe, and several US Government agencies. Our open source software has been downloaded in over 76 countries with more downloads to China than any other country. We get more hits, downloads, and requests from China than any other country outside the US.
Jumper 2.0 is just beginning to gain recognition as a game changing software platform. Jumper has grown rapidly from department and project level deployments by rogue groups of employees frustrated with existing corporate IT solutions, to development level beta and sandbox platforms that opened peoples eyes to the power of social knowledge tagging, to full blown enterprise platforms that supplement existing Search and KM tools. Jumper wikis are popping up to provide users with support and advice and corporate IT, instead of trying to police or squash this self-help behavior, has begun to embrace it.
We look forward to becoming a significant driver of innovation in the enterprise, empowering users everywhere behind the firewall, and planning new developments to the Jumper platform in the coming year. Our community of users, supporters, and developers grows stronger every day and we anticipate the suggestions and contributions of each new member. It is your feedback that will result in new features and tools that benefit the broader community.
From all of us at Jumper thank you to the community of users who support us. Your comments, suggestions, complaints, bug fixes, and continued deployments help make for better software.
Thursday, February 25, 2010
How Jumper survives early E2.0 market and uncertain economic times – the secret sauce is open source
A customer recently asked me how Jumper was going to survive as a start-up in tough economic times. A very good question considering…
Cogenz has folded, Connectbeam has an uncertain future (the rumor is they are out of money), and Jive recently layed off 1/3 of their staff and “reassigned” the CEO and co-founder. How will Jumper survive?
The power of Jumper is in open source. Unlike the closed enterprise platforms of our struggling competitors the Jumper 2.0 software and source code will continue on with or without Jumper Networks. The ideas and creativity of Jumper 2.0 will live on in the community even if Jumper Networks is not the community leader. A new community will emerge to drive development of the software, continue improvements, and bring new ideas and insights into the development process. Our software isn’t proprietary, it belongs to everyone.
The opportunity of open source is that you can try some truly new ideas and see if they work. Jumper has pioneered a number of ideas that are growing rapidly. Knowledge tagging (see Wikipedia definition) was a Jumper idea that has taken on a life of its own and is being openly debated in the KM community. Rating mechanisms for search results was a Jumper idea first and is now being experimented with by the biggest of search companies. Although giving power to the people when you have customers paying for search placement will be an interesting balancing act for them to pull off.
The last great benefit of open source is that we have not had to take VC money and sell our soul to the bottom line. We can still experiment, still innovate, still create new ways of doing things and let you the users decide what you like and what you don’t. At Jumper there is no bottom line, at least not yet. There is no time table to profitability, and given the current economic environment that is a good thing. It takes time for new ideas, for revolutionary software platforms to take hold. It takes time for people to begin to grasp the benefits, opportunities, and real power of groundbreaking software. In that sense Jumper has only just begun.
Cogenz has folded, Connectbeam has an uncertain future (the rumor is they are out of money), and Jive recently layed off 1/3 of their staff and “reassigned” the CEO and co-founder. How will Jumper survive?
The power of Jumper is in open source. Unlike the closed enterprise platforms of our struggling competitors the Jumper 2.0 software and source code will continue on with or without Jumper Networks. The ideas and creativity of Jumper 2.0 will live on in the community even if Jumper Networks is not the community leader. A new community will emerge to drive development of the software, continue improvements, and bring new ideas and insights into the development process. Our software isn’t proprietary, it belongs to everyone.
The opportunity of open source is that you can try some truly new ideas and see if they work. Jumper has pioneered a number of ideas that are growing rapidly. Knowledge tagging (see Wikipedia definition) was a Jumper idea that has taken on a life of its own and is being openly debated in the KM community. Rating mechanisms for search results was a Jumper idea first and is now being experimented with by the biggest of search companies. Although giving power to the people when you have customers paying for search placement will be an interesting balancing act for them to pull off.
The last great benefit of open source is that we have not had to take VC money and sell our soul to the bottom line. We can still experiment, still innovate, still create new ways of doing things and let you the users decide what you like and what you don’t. At Jumper there is no bottom line, at least not yet. There is no time table to profitability, and given the current economic environment that is a good thing. It takes time for new ideas, for revolutionary software platforms to take hold. It takes time for people to begin to grasp the benefits, opportunities, and real power of groundbreaking software. In that sense Jumper has only just begun.
Thursday, February 11, 2010
Jumper versus Enterprise Search
A customer recently asked us at a show what the difference was between cluster search with Vivisimo and Jumper search? We hear this and similar questions quite often. Our response is always the same...
They are different tools to solve different problems.
Universal Search
Whether cluster search, keyword search, full-text search, page rank search, or federated search they all represent specific point solutions. Jumper provides a more global or universal view of all your information assets.
Federated search for structured data, page rank search for web pages, cluster search and keyword search for content and media, they each search across a specific silo. Each can be very effective at finding information within the silo. But they do not search across silos (either different formats, schemas, locations or vendors). Jumper provides search across all your silos and it connects disparate information together across these silos.
20% Rule
Traditional enterprise search only allows you to search storage that you already know about. The assets in centralized storage represent on average only 20% of all your information assets. The other 80% of information assets are hidden from traditional enterprise search, but are visible with Jumper.
In a large organization there can be thousands of databases, hundreds of file servers, dozens of content systems that are often distributed by division, department, geography, project, etc. Searching across all of these is, to be polite, extremely difficult with traditional search. Jumper gives you high-level visibility of all these assets regardless of format or location. It allows users who know, use, or create the information to share it with the organization.
Smarter than People?
All of the search solutions we have discussed are coded algorithms. Automated software programs that represent a one-size fits all approach to search. They lack the dexterity and the intelligence that Jumper delivers to search results.
A cluster or keyword search algorithm pulls out and indexes words that appear to be significant. However, it cannot provide the context, meaning, and value that we crave in search results. Even the best algorithm is not as good as a human being at interpreting the content or data. You have to click through each search result and analyze it for relevance. Jumper delivers the who, what, when, where, how, and why details with the search results so you can quickly determine relevance and value without inquiring each source.
Final Analysis
Your organization most likely uses both cluster search as well as federated search because they each provide value in their own way. Jumper can be included in this equation.
We always tell our customers that its not one solution or the other.
Organizations should use Jumper along side these other tools for the value it provides delivering true enterprise wide (even global) visibility as well as for its next-gen knowledge management capabilities.
They are different tools to solve different problems.
Universal Search
Whether cluster search, keyword search, full-text search, page rank search, or federated search they all represent specific point solutions. Jumper provides a more global or universal view of all your information assets.
Federated search for structured data, page rank search for web pages, cluster search and keyword search for content and media, they each search across a specific silo. Each can be very effective at finding information within the silo. But they do not search across silos (either different formats, schemas, locations or vendors). Jumper provides search across all your silos and it connects disparate information together across these silos.
20% Rule
Traditional enterprise search only allows you to search storage that you already know about. The assets in centralized storage represent on average only 20% of all your information assets. The other 80% of information assets are hidden from traditional enterprise search, but are visible with Jumper.
In a large organization there can be thousands of databases, hundreds of file servers, dozens of content systems that are often distributed by division, department, geography, project, etc. Searching across all of these is, to be polite, extremely difficult with traditional search. Jumper gives you high-level visibility of all these assets regardless of format or location. It allows users who know, use, or create the information to share it with the organization.
Smarter than People?
All of the search solutions we have discussed are coded algorithms. Automated software programs that represent a one-size fits all approach to search. They lack the dexterity and the intelligence that Jumper delivers to search results.
A cluster or keyword search algorithm pulls out and indexes words that appear to be significant. However, it cannot provide the context, meaning, and value that we crave in search results. Even the best algorithm is not as good as a human being at interpreting the content or data. You have to click through each search result and analyze it for relevance. Jumper delivers the who, what, when, where, how, and why details with the search results so you can quickly determine relevance and value without inquiring each source.
Final Analysis
Your organization most likely uses both cluster search as well as federated search because they each provide value in their own way. Jumper can be included in this equation.
We always tell our customers that its not one solution or the other.
Organizations should use Jumper along side these other tools for the value it provides delivering true enterprise wide (even global) visibility as well as for its next-gen knowledge management capabilities.
Subscribe to:
Posts (Atom)