Abstract: Various technologies and techniques are disclosed for integrating structured accounting data with unstructured data. From an application that manages structured accounting data related to an entity, a user selection is received to create a document container for a collaboration tool. The document container is used for storing unstructured data related to the entity. In response to the selection of the create option, a site creation service is launched for automatically creating the document container using settings previously specified by an administrator on a configuration screen of the application. Once the document container is created, unstructured data related to the entity is stored in the document container. The user can view and navigate between the structured accounting data and unstructured data without having to leave the application. Unstructured data is automatically published to the document container for the entity as users interact with the application.

Abstract: A role based graphical user interface (UI) is used for receiving user input for entry/editing relating to projects/tasks using a limited display device. Functional components are grouped into logical hubs that may be displayed within the user interface. The groupings of the components are based on a role of a user (e.g. project manager, project participant, contractor, . . . ). For example, for one or more users, the role based graphical UI may group the following components together: expense entry and approval; time entry and approval; notification messages; collaboration of information (e.g. documents, project information, and the like); reporting; and settings. After selecting one of the components from the role based UI, a user may use a displayed component for interacting with the functionality (e.g. entering an expense, time entry, . . . ). The UI is configured to allow navigation between the different functions included within the logical hubs.

Abstract: A layered architecture for a web service is provided with a data tier, object representation, data transformation, and a service tier. Scalability is achieved by relying on relatively high degree of decoupling, lightweight data interaction, and reducing overhead of transaction demands. Custom web services can be built on top and leverage the capabilities of the flexible framework including lightweight transaction support, event-based business logic extensibility, and efficient data contract binding.

Abstract: A layered architecture for a web service is provided with a data tier, object representation, data transformation, and a service tier. Scalability is achieved by relying on relatively high degree of decoupling, lightweight data interaction, and reducing overhead of transaction demands. Custom web services can be built on top and leverage the capabilities of the flexible framework including lightweight transaction support, event-based business logic extensibility, and efficient data contract binding.

Abstract: Various technologies and techniques are disclosed for integrating structured accounting data with unstructured data. From an application that manages structured accounting data related to an entity, a user selection is received to create a document container for a collaboration tool. The document container is used for storing unstructured data related to the entity. In response to the selection of the create option, a site creation service is launched for automatically creating the document container using settings previously specified by an administrator on a configuration screen of the application. Once the document container is created, unstructured data related to the entity is stored in the document container. The user can view and navigate between the structured accounting data and unstructured data without having to leave the application. Unstructured data is automatically published to the document container for the entity as users interact with the application.

Abstract: A data model models a social network. The data model can be embodied as a person profile schema and a connector profile schema. The person profile schema defines properties of persons in the social network. The connector profile schema defines connectivity properties of persons that connect a searcher to the persons in social network that the searcher desires to find. Query languages can be based on the data model and can be used to express queries of social networks. Queries can be for persons, for connecting persons, or for both.

Abstract: A data model models a social network. The data model can be embodied as a person profile schema and a connector profile schema. The person profile schema defines properties of persons in the social network. The connector profile schema defines connectivity properties of persons that connect a searcher to the persons in social network that the searcher desires to find. Query languages can be based on the data model and can be used to express queries of social networks. Queries can be for persons, for connecting persons, or for both.