{"id":36522,"date":"2009-02-14T05:07:24","date_gmt":"2009-02-14T12:07:24","guid":{"rendered":"http:\/\/localhost\/exoblog\/?p=1056"},"modified":"2009-02-14T05:07:24","modified_gmt":"2009-02-14T12:07:24","slug":"context-adaptation-of-exo-jcr-file-explorer","status":"publish","type":"post","link":"https:\/\/www.exoplatform.com\/blog\/context-adaptation-of-exo-jcr-file-explorer\/","title":{"rendered":"Context adaptation of eXo JCR File Explorer"},"content":{"rendered":"<p>In eXo DMS (<em>Document Management System<\/em>), users manage content through\u00a0an application called \u00a0&#8220;JCR File Explorer&#8221;. This one\u00a0allows to\u00a0create,\u00a0retrieve, update or delete content. Until now, it\u00a0forced users to\u00a0initially\u00a0select a drive. A drive\u00a0can be considered as a logical unit of storage (for example: live documents, user private documents, workgroup documents) :<\/p>\n<div id=\"attachment_1058\" style=\"width: 390px\" class=\"wp-caption aligncenter\"><img aria-describedby=\"caption-attachment-1058\" decoding=\"async\" loading=\"lazy\" class=\"size-full wp-image-1058 \" title=\"screenshot\" src=\"https:\/\/www.exoplatform.com\/blog\/\/wp-content\/uploads\/2009\/02\/screenshot.jpg\" alt=\"Choosing a dfrive in JCR File Explorer\" width=\"380\" height=\"215\" \/><p id=\"caption-attachment-1058\" class=\"wp-caption-text\">Choosing a drive in JCR File Explorer<\/p><\/div>\n<p>This selection step was not really convenient and we thought there was\u00a0matter to\u00a0improve productivity.<\/p>\n<p>So JCR File Explorer will\u00a0optionnally allow bypassing this drive selection and immediately\u00a0let\u00a0the users access\u00a0the drive\u00a0matching the context of\u00a0their work.<\/p>\n<ul>\n<li>in the &#8220;<strong>spaces<\/strong>&#8221; use case, the JCR File Explorer will directly access the drive\u00a0containing\u00a0content\u00a0shared by the community he&#8217;s connected to (this use case is compatible with the eXo Spaces module),<\/li>\n<li>in the &#8220;<strong>jailed<\/strong>&#8221; use case, the administrator will reference a unique drive or document from the application preferences. This can be considered as a Unix &#8220;chroot&#8221;,<\/li>\n<li>in the &#8220;<strong>parameterized<\/strong>&#8221; use case, the application fetches some location information\u00a0from the portal page URL. Then it will directly access that specified location in the storage\u00a0(can be a folder or a document). This use case is handy to allow linking the JCR File Explorer from external applications. A typical example is a Google gadget listing\u00a0the last 5\u00a0modified documents.\u00a0When clicking, the user is\u00a0redirected\u00a0to eXo Portal and directly accesses\u00a0the document\u00a0in\u00a0its context.<\/li>\n<\/ul>\n<p>Of couse, in all cases, security checks are performed to ensure the current user is\u00a0granted to access the target location.<\/p>\n<p>Developments should be\u00a0ready when\u00a0eXo DMS 2.3 is released (middle of march).<\/p>\n","protected":false},"excerpt":{"rendered":"In eXo DMS (Document Management System), users manage content through\u00a0an application called \u00a0&#8220;JCR File Explorer&#8221;. This one\u00a0allows to\u00a0create,\u00a0retrieve, update or delete content. Until now, it\u00a0forced users to\u00a0initially\u00a0select a drive. A drive\u00a0can be considered as a logical unit of storage (for example: live documents, user private documents, workgroup documents) : This selection step was not really [&hellip;]","protected":false},"author":7,"featured_media":12746,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[699],"tags":[],"lang":"en","translations":{"en":36522},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/posts\/36522"}],"collection":[{"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/comments?post=36522"}],"version-history":[{"count":0,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/posts\/36522\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/"}],"wp:attachment":[{"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/media?parent=36522"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/categories?post=36522"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.exoplatform.com\/blog\/wp-json\/wp\/v2\/tags?post=36522"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}