<commit_before>======================
What is this document?
======================
This document frames the goals and scope for the current Cosmos release. Documentation for each feature should be placed in a README file on that feature's folder.

===============
Curry release (internal alpha) goals
===============
**Due Date**: 30/03/2012

**One line goal**: Create a web front-end to let users launch Hadoop jobs on the cluster and view the results of the job.

*Note*: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.


Web front-end
-------------

Goals
~~~~~
- Main Page:
   - The front-end MUST support user login.
   - The main page of the front-end (once the user is logged in) MUST provide a list of previous and active Hadoop tasks, and their state: Running, Completed, Error.
   - The rows that describe Completed tasks MUST provide a link to view the results of the job.
   - The rows that describe Error tasks MUST provide a link to view extended error information about the failure.
   - The main page MUST provide a button to create new Hadoop jobs
- Job creation page (unless otherwise specified, users are assumed to be authenticated):
   - Non authenticated users MUST NOT be able to create Hadoop jobs in the cluster.
   - Users MUST be able to upload the input data through an HTTP POST (i.e. a Web form).<commit_msg>Very small fix<commit_after>======================
What is this document?
======================
This document frames the goals and scope for the current Cosmos release. Documentation for each feature should be placed in a README file on that feature's folder.

====================================
Curry release (internal alpha) goals
====================================
**Due Date**: 30/03/2012

**One line goal**: Create a web front-end to let users launch Hadoop jobs on the cluster and view the results of the job.

*Note*: The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.


Web front-end
-------------

Goals
~~~~~
- Main Page:
   - The front-end MUST support user login.
   - The main page of the front-end (once the user is logged in) MUST provide a list of previous and active Hadoop tasks, and their state: Running, Completed, Error.
   - The rows that describe Completed tasks MUST provide a link to view the results of the job.
   - The rows that describe Error tasks MUST provide a link to view extended error information about the failure.
   - The main page MUST provide a button to create new Hadoop jobs
- Job creation page (unless otherwise specified, users are assumed to be authenticated):
   - Non authenticated users MUST NOT be able to create Hadoop jobs in the cluster.
   - Users MUST be able to upload the input data through an HTTP POST (i.e. a Web form).
{'fraction_non_alphanumeric': 0.13399668325041458, 'fraction_numerical': 0.007960199004975124, 'mean_word_length': 3.9523809523809526, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2080928', 'n_tokens_mistral': 825, 'n_tokens_neox': 752, 'n_words': 445}