Globals Challenge #4 requires you to build a solution-application that solves a problem, meets a current market need, or creates a new market by innovative use of data (the solution-application can do one or more of these). The solution-application can be for any industry, commercial focused, or open source / free focused. There are 3 options in creating the solution-application:

• Use at least one the APIs provided by Globals which are Java, .NET, and Node.js.
• Leverage an existing Globals based application or framework that was submitted in a previous challenge. The previous entries can be found on the Globals Challenge site.
• Use at least one API and leverage an existing Globals based application or framework.

In your submission, you must state the problem being solved, the need being met, or the new market being created. You must then state how your solution-application solves the problem, meets the need, or creates a new market.

Your submission will be judged using the following criteria:

Non-technical criteria:

1. Uniqueness of solution-application
2. Impact of your solution-application to the end-user / market
3. Ease of use, if end-user focused

Technical criteria:

1. The GUI (Graphical User Interface) design and technology, if your solution-application is end-user focused
   • Your solution can be system to system oriented, but you must still meet all the stated criteria
2. Knowledge and use of the Globals API(s) chosen
3. Performance of data interaction (reading, writing, and presenting data)
4. Ease of deployment or access, for judging (The easier it is for people to access or setup your submission for judging, the better)

For this Globals Challenge, it is recommended that you use the Forum Topic entitled Challenge Questions, Clarifications & Discussions..., under the Forum Globals Challenge #4, to ask questions about how to do something in Globals, as you would in a database you are familiar with. This will enable you to exploit the APIs and Globals to the advantage of your solution-application. (The Globals team will be there to answer your questions.)

For those who want some place to start for ideas, you can look at:

• 35+ Use Cases For Choosing Your Next NoSQL Database
• What The Heck Are You Actually Using NoSQL For?
• Alex Popescu's - myNoSQL Guide
• The NoSQL Tapes - A Filmed Compilation of Interviews & Explanations & Case Studies

User Interface Notes:

• Your solution-application should be deployable in one of the following three ways:
  1. As a CLI (Command Line Interface) Application
  2. As a Web / RIA (Rich Internet Application) Application
  3. As a Desktop Application (Can use RIA Technology)
• If you create a web application, where the technology needs to be deployed on a server (AJAX, PHP, JSF, etc), you will be required to find a host for your solution-application, and make it available during the entire voting and judging period.
• Consideration should be given such that judging members have the ability to run your complete solution-application on a local machine, or on a VM (Virtual Machine), with instructions on how to call each interface that you make available. Please limit your selection of virtual machine technology to either VMWare or Virtual Box, if you select this route.

Important:
The source code for your solution-application must be uploaded/pushed to this GitHub Repository. You are encouraged to push your application source code to the GitHub Repository as often as possible to show your progress. All of your source code must be pushed to the GitHub Repository before the implementation stage of the challenge comes to an end, in order to be eligible for voting.

Globals Challenge #3 requires you to build a solution-application that solves a problem, meets a current market need, or creates a new market by innovative use of data (the solution-application can do one or more of these). The solution-application can be for any industry, commercial focused, or open source / free focused. Feel free to use any of the supported interfaces to Globals: Java, Node.js, or .NET. In your submission, you must state the problem being solved, the need being met, or the new market being created. You must then state how your solution-application solves the problem, meets the need, or creates a new market.

Your submission will be judged using the following criteria:

Non-technical criteria:

1. Uniqueness of solution-application
2. Impact of your solution-application to the end-user / market
3. Ease of use, if end-user focused

Technical criteria:

1. The GUI (Graphical User Interface) design and technology, if your solution-application is end-user focused
   • Your solution can be system to system oriented, but you must still meet all the stated criteria
2. Knowledge and use of the Globals API(s) chosen
3. Performance of data interaction (reading, writing, and presenting data)
4. Ease of deployment or access, for judging (The easier it is for people to access or setup your submission for judging, the better)

For this Globals Challenge, it is recommended that you use the Forum Topic entitled Challenge Questions, Clarifications & Discussions..., under the Forum Globals Challenge #3, to ask questions about how to do something in Globals, as you would in a database you are familiar with. This will enable you to exploit the APIs and Globals to the advantage of your solution-application.
The Globals team will be there to answer your questions.

For those who want some place to start for ideas, you can look at:

• 35+ Use Cases For Choosing Your Next NoSQL Database
• What The Heck Are You Actually Using NoSQL For?
• Alex Popescu's - myNoSQL Guide
• The NoSQL Tapes - A Filmed Compilation of Interviews & Explanations & Case Studies

User Interface Notes:

• Your solution-application should be deployable in one of the following three ways:
  1. As a CLI (Command Line Interface) Application
  2. As a Web / RIA (Rich Internet Application) Application
  3. As a Desktop Application (Can use RIA Technology)
• If you create a web application, where the technology needs to be deployed on a server (AJAX, PHP, JSF, etc), you will be required to find a host for your solution-application, and make it available during the entire voting and judging period.
• Consideration should be given such that judging members have the ability to run your complete solution-application on a local machine, or on a VM (Virtual Machine), with instructions on how to call each interface that you make available. Please limit your selection of virtual machine technology to either VMWare or Virtual Box, if you select this route.

Important:
The source code for your solution-application must be uploaded/pushed to this GitHub Repository. You are encouraged to push your application source code to the GitHub Repository as often as possible to show your progress. All of your source code must be pushed to the GitHub Repository before the implementation stage of the challenge comes to an end, in order to be eligible for voting.

Globals Challenge #2 revolves around the storage and usage of streaming or changing data. Examples of this type of data include the following: Apache HTTP logs, Application Server logs, database server logs, and clickstreams, etc. Clickstreams can be defined as recordings of user activity (e.g. clickable screen actions) on a webpage or software application. As users click on elements of a webpage or application, actions associated with each click are logged as part of the current session's clickstream. This data, while useful in a plethora of ways, is often used for activity analysis, application productivity, popularity profiling, and testing, to name a few.

This challenge requires the following:

1. Select at least one log or streaming data source
   (If you chose to use the Apache Access Log file, for example, the data is stored in a file named access_log[.n], and can often be found in the following location on a Linux system: /var/log/httpd/)
2. Use one or more of the GlobalsDB APIs to do the following:
   1. Store the data into GlobalsDB
   2. Build a solution-application that will enable any judging member of the Globals Community to search (query) on data elements being stored in GlobalsDB from the data source(s)
   3. Enable updating of the data as it changes
      (For this you may need to have more than one dataset, or write a small application that can generate changes to your dataset)
   4. Build a solution-application that will enable any judging member of the Globals Community to browse the data being stored in GlobalsDB (Optional)
3. Build a user interface that provides the following:
   1. Enables a user to import the data into GlobalsDB
   2. Enables a user to browse or search the data in GlobalsDB
   3. Enables the user to know when the data previously stored in GlobalsDB has been changed
   • User Interface Notes:
     • Your solution-application should be deployable in one of the following three ways:
       1. As a CLI (Command Line Interface) Application
       2. As a Web / RIA (Rich Internet Application) Application
       3. As a Desktop Application (Can use RIA Technology)
     • If you create a web application, where the technology needs to be deployed on a server (AJAX, PHP, JSF, etc), you will be required to find a host for your solution-application, and make it available during the entire voting and judging period.
     • Consideration should be given such that judging members have the ability to run your complete solution-application on a local machine, or on a VM (Virtual Machine), with instructions on how to call each interface that you make available. Please limit your selection of virtual machine technology to either VMWare or Virtual Box, if you select this route.
4. Add non-trivial features to your solution-application that would make someone want to use it. Examples include, but are not limited to, the following:
   1. Threaded views of related items (can a user pick the types of relations)
   2. Historical views versus real-time views
   3. Priorities (and possibly actions) associated with key words or patterns
   4. Ability to monitor activity, not just read multiple static logs

Important:
The source code for your solution-application must be uploaded/pushed to this GitHub Repository. You are encouraged to push your application source code to the GitHub Repository as often as possible to show your progress. All of your source code must be pushed to the GitHub Repository before the implementation stage of the challenge comes to an end, in order to be eligible for voting.

RSS

• URL:  http://www.flickr.com/services/feeds/docs/photos_public/
• APIs:  http://www.flickr.com/services/api/

1. Build a representative class to model the RSS feed.
2. Using one of the published Flickr APIs, populate a Globals database with the data from the feed using the class and the Globals API (Java or Node.js).
3. Build a search mechanism on top of Globals that allows any judging member of the Globals Community to query on the data elements of the class you created. For instance if one of the data elements of your class is "name", we want any judge to have the ability to search on all names in the Globals database beginning with "A".
4. Provide a simple user interface to:
   1. Start / Stop the RSS data feed gathering.
   2. Query the data in the Globals database.
   3. Show the query results.
   • User Interface Notes:
     • Your solution-application should be deployable in one of three ways:
       1. As a CLI (Command Line Interface) Application
       2. As a Web / RIA (Rich Internet Application) Application
       3. As a Desktop Application (Can use RIA Technology)
     • If you create a web application, where the technology needs to be deployed on a server (AJAX, PHP, JSF, etc), you will be required to find a host for your solution-application, and make it available during the entire voting and judging period.
     • Consideration should be given such that judging members have the ability to run your complete solution-application on a local machine, or on a VM (Virtual Machine), with instructions on how to call each interface that you make available. Please limit your selection of virtual machine technology to either VMWare or Virtual Box, if you select this route.

Important:
The source code for your solution-application must be uploaded/pushed to this GitHub Repository. You are encouraged to push your application source code to the GitHub Repository as often as possible to show your progress. All of your source code must be pushed to the GitHub Repository before the implementation stage of the challenge comes to an end, in order to be eligible for voting.