Abstract: Automatically generating a glossary of terms for a given document or group of documents is provided. A single document or a group of documents associated with a given project or event are parsed for one or more unique terms (e.g., words, acronyms, phrases, etc.). Identified terms are passed to a local or external definition source, and definitions for the one or more identified terms are retrieved. Retrieved definitions are presented to a user of the documents, and approved definitions are stored in a project store for subsequent use in association with the documents.

Abstract: In various embodiments, methods and systems for language scaling a natural language processing system (NLPS) are provided. A database schema of a database is accessed. The database schema includes entities that are defined in a query natural language different from an NLPS natural language upon which NLPS components are built. The entities are communicated to a machine translation service and top translations. A translated database schema model is generated based on the entities and translations. When a query associated with the query natural language and the database schema is received, a query translation is generated. The query translation comprises selectively translated portions of the query based on a selective translation mechanism that includes accessing the machine translation service to translate selected portions of the query. The selected portions are selected based on the translated database schema. The query translation is executed on the NLPS components to identify query results.

Abstract: In various embodiments, methods and systems for language scaling a natural language processing system (NLPS) are provided. A database schema of a database is accessed. The database schema includes entities that are defined in a query natural language different from an NLPS natural language upon which NLPS components are built. The entities are communicated to a machine translation service and top translations. A translated database schema model is generated based on the entities and translations. When a query associated with the query natural language and the database schema is received, a query translation is generated. The query translation comprises selectively translated portions of the query based on a selective translation mechanism that includes accessing the machine translation service to translate selected portions of the query. The selected portions are selected based on the translated database schema. The query translation is executed on the NLPS components to identify query results.

Abstract: Automatically generating a glossary of terms for a given document or group of documents is provided. A single document or a group of documents associated with a given project or event are parsed for one or more unique terms (e.g., words, acronyms, phrases, etc.). Identified terms are passed to a local or external definition source, and definitions for the one or more identified terms are retrieved. Retrieved definitions are presented to a user of the documents, and approved definitions are stored in a project store for subsequent use in association with the documents.

Abstract: Automatically generating a glossary of terms for a given document or group of documents is provided. A single document or a group of documents associated with a given project or event are parsed for one or more unique terms (e.g., words, acronyms, phrases, etc.). Identified terms are passed to a local or external definition source, and definitions for the one or more identified terms are retrieved. Retrieved definitions are presented to a user of the documents, and approved definitions are stored in a project store for subsequent use in association with the documents.

Abstract: Automatically generating a glossary of terms for a given document or group of documents is provided. A single document or a group of documents associated with a given project or event are parsed for one or more unique terms (e.g., words, acronyms, phrases, etc.). Identified terms are passed to a local or external definition source, and definitions for the one or more identified terms are retrieved. Retrieved definitions are presented to a user of the documents, and approved definitions are stored in a project store for subsequent use in association with the documents.

Abstract: Automatically classifying content into a given project workspace is provided. New electronic mail items, documents, meeting requests, tasks, calendar items, and the like are automatically classified into a project workspace. Thus, a user is not required to engage in a time-consuming task of identifying, collecting, and associating such content with a given project workspace. In addition, feedback may be provided to the user on the quality of automatic assignments of content items to the desired workspace for editing content associated with the desired workspace and for improving the automatic classification process.

Abstract: An analysis module, when triggered by a synchronization framework when a new data item is added to a project data store, runs a series of analysis feature extractors on the new content. An analysis may be conducted, and features of interest may be extracted from the data item. The analysis utilizes natural language processing, as well as other technologies, to provide an automatic or semi-automatic extraction of information. The extracted features of interest are saved as metadata within the project data store, and are associated with the data item from which it was extracted. The analysis module may be utilized to discover additional information that may be gleaned from content that is already in the project data store.

Abstract: A space in which a user may organize data and collaborate with other users is provided. Project data and metadata may be saved into a reusable template and stored in a repository, wherein other users may discover and download the template for use as a resource for a related project type. A template may contain various document types that may expose a breadth of applications and application functionalities that may be utilized for a given task or project. Questions and answers, task templates, and terminology may also be provided. Project templates may allow for collaboration on projects, wherein business and/or social groups may collaborate quickly, easily, and more completely.

Abstract: Project-related data may be aggregated from various data sources, given context, and may be stored in a data repository or organizational knowledge base that may be available to and accessed by others. Documents, emails, contact information, calendar data, social networking data, and any other content that is related to a project may be brought together within a single user interface, irrespective of its data type. A user may organize and understand content, discover relevant information, and act on it without regard to where the information resides or how it was created.

Abstract: An automatic discovery of content to add to a data store for a project is disclosed. A data item may be parsed for data features that are contextually relevant to a given project or task. Discovered interesting data may be extracted and mapped to various search mechanisms. A search may be built and applied to various data sources to discover data items based on the contextually relevant data features. Search results from various search mechanisms may be displayed in a single user interface and may be presented to a user.