Spanish Forum.
Don't forget to visit it. We'll be there to help you in everything we can to make your experience more succesful with document management tool.

Repository to Repository (R2R): This occurs when content repositories need to talk directly with each other.
- Managing records in other repositories that are stored centrally. This is called Federated Records Management, although it is different from the Land Use Case, to be discussed later.
- Publication of contents of a repository to another. A common scenario is the publication of content from a collaborative systema / ECM directly to a WCM system for publishing on an Intranet / Extranet.
Application to Repository (A2R): This occurs when an application that uses content is attached to a content repository to manage all content-related services.* Sharepoint as a front-end. If implemented, Sharepoint can become a front-end and any other repository can be used as back-end. In this way problems could be solved Sharepoint scalability without the user being affected.
* Collaborative systems. All Systems Enterprise 2.0, and current collaborative applications could use a robust backend to provide features such as the uniqueness of content and records management. This is the same as the previous example, but widespread.
* Business Software Applications. It could be a process manager (BPM), a manager of customer relations (CRM), or any type of application used by an organization, the content is fast becoming a large part of these systems. It is becoming critical to have a centralized place to manage the content and apply consistent rules.
* Vertical Applications that use Content (CEVASA). As discussed before, CMIS can make life easier for manufacturers of CEVA. Let the experts in each domain to build an application to the relevant industry and allow them to associate with a system to manage content. This frees the manufacturer from CEVA have to worry about the content or keep as many different interfaces. That means more money to invest in R & D in real functionality.
* Productivity applications. Why not link to Word, Excel, Open Office or any other type of application to a repository using CMIS? Seems like a good way to make a portable integration, similar to what was attempted with ODMA (provided by @ billtrippe via twitter on 8/17/09)Federated Repositories: This occurs when an application needs to talk to many different repositories using a single user interface.* Federated search. This basically means what you can see in the demo iECM. Someone could do a search in multiple repositories.
* Federation rather than migration. An application can interact with multiple repositories. Rather than migrate all content from an old repository immediately, you might have to interface with the old repository interaactuando until completely migrated or completely outdated. The application can store the new content in the new default repository.
Yerbabuena has published the fourth NTI version (Nuxeo Thinks Itself) of the Semantics For Nuxeo Proyect 2010.
In this fourth sprint have been implemented these new functionalities:
Possibility to add annotations about localizations through Google Maps API.
DBPedia and OpenCalais integration as additional semantic annotations engines over the documents.
Progressive learning in identifying the types of documents.
Automatic start of actions depending on the type of documents.
Automatic and preiodic background reasoning work.
First of all, Nuxeo has been integrated with Google Maps API so that locations can be added as annotations directly from the map view.
Furthermore, we have expanded the semantic annotation engine, allowing automatic annotation of documents. Such annotations are made through OpenCalais and DBpedia. Once you create a document, its content is sent by a thread, in background, to the OpenCalais and DBPedia services, returning a series of tags that are added as annotations to the document. Nuxeo is also integrated with the Google API translator, as both DBpedia and OpenCalais offer better services if the text is written in English. Once the thread has finished, it displays a message informing the user and throws an event that is picked up by Nuxeo and added to the history tab.
Learning the types of documents allows Nuxeo can automatically identify and classify all documents, for which it must have been trained previously. This way you can "teach" the semantic service to be able to identify any type of document.
Furthermore, we have developed an extension point that allows automatic startup of actions depending on the type of document. These actions could be a workflow or any other type of action runnable in Nuxeo. Defining and setting up the parameters for this action is done via an XML which is then parsed at deployment time.
Finally, we have implemented an additional thread within the semantic service that handles the task of reasoning automatically, periodically and in background, transparently to the user.
New flex interface with a new “list-mode” relationships view.
Better Organization and Tax Code detection during the reading of documents (contracts).
Organizations and Tax Code detection after editing a document with LiveEdit.
Anntations update through an “intelligent” popup window which search queries will only return results for the corresponding domaing/range of the annotated property.
Automatically detection of Organization - Tax Code relationship, so that if a new document detects a Tax Code which is already stored in database, will take the corresponding stored Organization name for that Tax Code, ignoring the new Organization name.
Tax Code validation when introducing its value in a “has Tax Code” annotation.
Translation of all new labels (spanish and english).
Improvement of the Semantic Annotation tab interface. The reasoning button dissappears during reasoning work, displaying an informative text (“reasoning...”). After all reasoning work, the button will appear disabled until new information must be reasoned.
Confirmation popup after clicking for deleting an annotation.
Improvement of the flex interface: When the user filters the relations by one or several properties, it automatically disables the “All Relations” option.
In this second sprint have been implemented these new functionalities:
Integrating Nuxeo Relations with Semantic Relations.
Possibility to add semantic annotations to File documents. Several of these annotations, like creator of the document, and also the relations among documents added at their creation or at Nuxeo Tab, are automatically added.
Possibility to navigate through icons in the Flex UI.
First of all, document semantic relations have been integrated with Nuxeo relations, so that they are diplayed as another Nuxeo relation more.
On the other hand, a new Tab has been created which allow user to add semantic annotations to a File document. As discussed above, certain relations are added automatically. However, the user may manually add any other annotations. This new Tab also includes a reasoning button, which will be enabled every time new semantic information is added, and disabled when all information is reasoned. The tab interface has two text fields (one for subject and one for object), and a menu with all semantic predicates. The text fields are implemented as suggestion boxes, so that posible values (already reasoned and stored) are suggested, according to selected predicate domain (for subject) and range (for object). Finally, a warning icon is displayed to notice which annotations are not reasoned yet.
As for the Flex interface, information has been added to the nodes of the relationships graph. This information includes the number of relationships that contains that node. Moreover, as mentioned above, it has been implemented the ability to navigate between the different nodes, both the current graph and the list of visited nodes displayed. It has also been developed the possibility of restricting the relations to show in the graph. Finally, it has been improved the visual appearance.
Yerbabuena has published the NTI (Nuxeo Thinks Itself) version for the project Semantics For Nuxeo.
We have developed a plug-in, based on OSGi model, which integrates a persistent reasoner over a relational DataBase with Nuxeo platform and with a friendly User Interface made with Flex tool.
Following functionalities have been implemented in this first version:
Integrate Nuxeo with a persistent reasoner for OWL implemented over a relational DataBase.
Chance to add relations among File Documents while creating them.
Flex UI and Nuxeo integration.
The persistent reasoner is an OWL Parser which is able to store any ontology into a relational DataBase. Previously, it connects with an extern reasoner (Pellet in this case) to get the Tbox ontology part reasoning. Our persistent reasoner has reasoning algorithms over Abox part, so that the ontology is reasoned on both Tbox and Abox parts, and remains persistent inside the relational DataBase. This implies that the query results time over the reasoned ontology will be lower than in most reasoners implemented nowadays, as these do all work over RAM memory.
On the other hand, we have changed the Nuxeo File Document schema and views to allow adding Documents (File) relations to the one being created.
Finally, we have implemented a friendly Flex UI, integrated with Nuxeo through Restlets, which allows to show semantic relations generated by the reasoner.