Jivespace : Document List - All Communities

DbDocumentManager documentManager = (DbDocumentManager) JiveApplication.getContext().getDocumentManager();
documentManager.getDocumentCache().remove(caseLink.getDocID());

DocumentManager is an interface and class DocumentManagerProxy implements it.

ExtendedDocumentManager is an interface and extends DocumentManager. The DbDocumentManager implements ExtendedDocumentManager interface.

About Cache, please refer to http://www.jivesoftware.com/jivespace/docs/DOC-4060

documentManager and documentManagerImpl

communities@jivesoftware.com — Thu, 12 Nov 2009 09:19:54 GMT

Today, I always got DocumentProxy from documentManager.getDocument(docID), the DbDocument should be returned.

DocumentManager is a interface, that is extened by ExtendedDocumentManager and implemented by DocumentManagerProxy
Document is a interface, that is implmented by both DbDocument DocumentProxy.In DocumentManagerProxy,
the getDocument(docID) returms Document. I don't know whether the Document is DbDocument or DocumentProxy. In my bean definition file,
the documentManager is referenced to documentManager, but in clearspace bean definition files, the documentManager is always refered to
documentManagerImpl. In the clearspace bean definition files, the documentManager is the name of DocumentManagerProxy, while
DbDocumentManager is the name of DbDocumentManager.

Then I found that the DbDocumentManager is implementation of ExtendedDocumentManager. Exactly ,the getDocument(docID) of DbDocumentManger
returns DbDocument. so im my bean definition file, the documentManager should reference to documentManagerImpl, not the docuementManager.

Clearspace community API about Document

communities@jivesoftware.com — Tue, 25 Aug 2009 05:45:48 GMT

1. How to get a document

2. How to create a document

3. How to publish a document

     /**
      * @throws UnauthorizedException 
      * @throws CommunityNotFoundException 
      * 
      */
     public com.landesk.miner.bean.Document createDocument(
               com.landesk.miner.bean.Document document) throws Exception {
 
          DocumentManager documentManager = JiveApplication.getContext().getDocumentManager();
          CommunityManager communityManager = JiveApplication.getContext().getCommunityManager();
          
          Community community = null;
 
         community = communityManager.getCommunity(document.getCommunityID());
     
          DocumentBean documentBean = new DocumentBean();
          documentBean.setUserID(document.getUserID());
          documentBean.setDocumentTypeID(1L);
          documentBean.setContainerID(document.getCommunityID());
          documentBean.setContainerType(JiveConstants.COMMUNITY);
          //Case title can be null
          documentBean.setTitle(document.getSubject()== null ? "Case:" + document.getIDInSource() + " Subject" : document.getSubject());
//          documentBean.setBodyText("abc");
          documentBean.setBodyText(document.getBody());
          
          Document communityDocument = documentProvider.getDocument(documentBean);
 
          Log.debug("documentManager:" + documentManager);
          Log.debug("documentProvider:" + documentProvider);
          Log.debug("community:" + community);
          Log.debug("communityDocument:" + communityDocument);
          Log.debug("Case:" + document.getIDInSource());
          
          documentManager.addDocument(community, communityDocument, Collections.emptyMap());
          
          communityDocument.setDocumentState(DocumentState.PUBLISHED);
          
          communityDocument.save();
          
          document.setIDInTarget(String.valueOf(communityDocument.getID()));
          
          Log.info("Case:" + document.getIDInSource() + " in Salesforce export successed." + "Document:" + document.getIDInTarget() + " creation  succeedeed.");
          
          return document;
     }

4. Plain Text to Community Document Body

            String myDocumentBody = "Hello\n\n";
            String doc = WikiContentHelper.wikiToEditorHtml(myDocumentBody);
            logger.info(doc);

When myDocumentBody="Hello\n\n" the Reuslt is <body>Hello </body>

When myDocumentBody = "<a href=\"abc\">Cause:</a>", the result is <body><a href="abc">Cause: </a></body>

When myDocumentBody ="<company>landesk</company>" the result is <body><company>landesk</company></body>

When myDocumentBody ="Cause:" + case.getCause() and the case.getCause() return null, the result is <body>Cause:null</body>

5. Wiki Text to Document

communityDocument.setBody(WikiContentHelper.unknownContentToJiveDoc(WikiContentHelper.wikiToEditorHtml(document.getBody())));

WikiContentHelper.wikiToJiveDocument(textBody);

Testing Links

russellstephens@gmail.com — Mon, 09 Nov 2009 03:27:43 GMT

http://www.google.com

Rules for Determining a User's Locale / Language (2.0.5 and later)

communities@jivesoftware.com — Wed, 10 Sep 2008 17:12:58 GMT

To clarify confusion, this is the official explanation of the rules used for determining a user's locale in Clearspace 2.0.5 and 2.5. (Bugs in previous releases meant that these rules were not consistently followed.)

Use the locale set in user's preference.
- If the user does not have a locale preference set, or if the user is an anonymous guest, then proceed to the next rule.
- If the user has selected a locale that is not supported by Clearspace, then the application global locale is used.
Use the locale preference from the user's browser.
- If no locale has been set, or if the locale selected is not supported by Clearspace, then proceed to the next rule.
Use the community specific locale.
- If no community specific locale has been set, or if one cannot be determined (there are some rare cases where this cannot be done, e.g. from AJAX requests), then proceed to the next rule.
Use the application global locale.

Reasoning

If a locale can be supported, then the user's preferences must be honored above all. It makes no sense to force a language setting on a user if they cannot understand and if their own language is available.
A user's Clearspace preference trumps all. Even though it's important to honor the locale set in the browser, allowing the user to customize their account is a good idea. The user might be surfing in an internet cafe in Thailand and might not want or be able to mess with the browser settings. Logging into Clearspace provides them with their own locale, just like they were back at home.
Providing a community specific locale is only useful for those cases when a supportable locale has not been selected by the user. In this case the application is trying to make the best choice for them. It should never trump the user's own desires (unless the locale is not supported). Implementing the community specific locale is also very tricky and does not always work. There are some requests where there is no context available and so it is not possible to determine what community space the user may have been browsing when they made their request. It can also be confusing to the user as the language may switch as they move from one page to another.

Languages Supported in Clearspace and Jive SBS by version number:

Version	Languages
2.5.0	English
2.5.1	Spanish
2.5.2	French Simplified Chinese German
2.5.3	Italian Japanese

3.0.0	English
3.0.1	Spanish French Simplified Chinese German Italian Japanese

FAQ

Q: The application lists a large number of different Locales, but only a few have translations.

A: This occurs by design, all the locales are listed because the application displays numbers / dates in those locales even if the language isn't supported. UPDATE: In 3.0/4.0, SBS only lists the languages that have been translated.

JW09 Session: Facebook for spies: Enabling social collaboration in a community trained not to collaborate

communities@jivesoftware.com — Tue, 17 Nov 2009 23:26:05 GMT