<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Best practice for public spaces]]></title><description><![CDATA[<p dir="auto">I've been hoping for some documentation about how to use the Public space(s) in version 4+. We still have the Public userlist- ok.</p>
<p dir="auto">I remember I created our one and only second-level public space (i.e. directly under _Public). At that point in time I also created and afterwards deleted another public space. So now</p>
<ul>
<li>What could be a good reason to have more than one public space, i.e. what would be a use case to have \_Public\_Level1 and \_Public\_LevelA?</li>
<li>What could be a good reason to have a subspace of a public space (\_Public\_Level1\_Level2), i.e. what would be a use case?</li>
<li>I think since version 4, when I multifile into our public space, my options are only to multifile into the space's root folder, or into the Template folder. Is that a bug or a feature? I always have to move the documents one folder level at a time afterwards</li>
</ul>
]]></description><link>https://community.ceo-vision.com/topic/739/best-practice-for-public-spaces</link><generator>RSS for Node</generator><lastBuildDate>Mon, 13 Jul 2026 21:43:39 GMT</lastBuildDate><atom:link href="https://community.ceo-vision.com/topic/739.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 20 Feb 2023 14:49:43 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Best practice for public spaces on Wed, 22 Feb 2023 06:17:22 GMT]]></title><description><![CDATA[<p dir="auto">Hello <a class="plugin-mentions-user plugin-mentions-a" href="/user/aclassen" aria-label="Profile: aclassen">@<bdi>aclassen</bdi></a>,</p>
<p dir="auto">Thank you for sharing your questions on our forums. Here are the answers to each of your questions:</p>
<ul>
<li>I've been hoping for some documentation about how to use the Public space(s) in version 4+. We still have the Public userlist- ok.</li>
</ul>
<p dir="auto"><em><strong>Answer: We will verify that the online documentation in English is up to date. If needed, we will complete as soon as possible.</strong></em></p>
<hr />
<ul>
<li>What could be a good reason to have more than one public space, i.e. what would be a use case to have _Public_Level1 and _Public_LevelA?</li>
</ul>
<p dir="auto">AND</p>
<ul>
<li>What could be a good reason to have a subspace of a public space (_Public_Level1_Level2), i.e. what would be a use case?</li>
</ul>
<p dir="auto"><em><strong>Answer: It is mainly a question of organizing the classification of documents and having a better understanding of this classification via email notifications (we see in which public space the documents are added/updated.</strong></em></p>
<p dir="auto"><em><strong>Also, to integrate GoFAST with an Intranet, it is a question of selecting the public space or spaces which are linked in order to automatically publish the documents which are deposited there on the Intranet. This is a use case implemented by some of the customers, such as the Department of Haute-Savoie and the University of Le Mans.</strong></em></p>
<hr />
<ul>
<li>I think since version 4, when I multifile into our public space, my options are only to multifile into the space's root folder, or into the Template folder. Is that a bug or a feature? I always have to move the documents one folder level at a time afterwards</li>
</ul>
<p dir="auto"><em><strong>Answer: Normally you can drop/multifile documents only in a subspace or folder that is in that subspace (eg _Public_Level1\folderA ) and not "at the root" of Public. Could you please open a ticket about this, for our team to check?</strong></em></p>
<p dir="auto">Thanks and have a great day.</p>
]]></description><link>https://community.ceo-vision.com/post/2361</link><guid isPermaLink="true">https://community.ceo-vision.com/post/2361</guid><dc:creator><![CDATA[odernovaya]]></dc:creator><pubDate>Wed, 22 Feb 2023 06:17:22 GMT</pubDate></item></channel></rss>