[MGNLDMS-137] Magnolia public instance does not contain versioned documents Created: 29/Sep/08 Updated: 04/Nov/15 Resolved: 04/Nov/15 |
|
| Status: | Closed |
| Project: | Document Management System (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Critical |
| Reporter: | Sunish Abraham | Assignee: | Philipp Bärfuss |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: | |
| Visible to: |
Giancarlo Berner, Naresh gangapur, sampath
|
| Description |
|
versions documents in source DMS activated does not carry the versioned information to the destination instance ; we have functionality in the Author environment of the destintation instance which requires the documents to be versioned |
| Comments |
| Comment by Jan Haderka [ 30/Sep/08 ] |
|
Sunish, Could you try to describe in more details what kind of feature are you looking for and why would it make sense for you to version documents at public instance as well? |
| Comment by Sunish Abraham [ 30/Sep/08 ] |
|
Hi Jan, We are using Magnolia Data and DMS modules to feed content to Java/Spring web application...accessing the content/data in Magnolia using JNDI module. Here is the scenario... 1) EMEA administrator creates an abstract/ event in Staging Author. The documents associated are version 1.0 Sunish |
| Comment by Sunish Abraham [ 30/Sep/08 ] |
|
When we use admin central of public instance, we are able to upload multiple versions of the document. So it is not the public instance that prohibits versioning, it is the subscriber that is not versioning the incoming content. Just thinking on these lines....
So if public instances are not meant for versioning, then why do we have the feature of enabling/ disabling versioning in public instance? |
| Comment by Olivier Marti [ 03/Oct/08 ] |
|
Hey Sunish Well, there is no difference from an author to a public instance, expect the fact that it is configured as a public instance. For your scenario it may be a better approach to upload the different document versions seperately (as 1.0, 1.1, ...). |
| Comment by Sunish Abraham [ 03/Oct/08 ] |
|
we are not activating 10 versions of a document at once...we just need the activation process to take the document (version) being activated and not just replace the document in the target. Since the Public instance supports versioned documents, the activation should be able to just save the document being activated and not replace. |
| Comment by Jan Haderka [ 03/Oct/08 ] |
|
Hi Sunish, |
| Comment by Sunish Abraham [ 03/Oct/08 ] |
|
Hi Jan, Yes I understand your previous statements on the current functionality (by design) of saving current version during activation of a DMS document. We need the functionality to be extended to save the version information of the document being activated and save new version not replace existing document. Yes we have found the class which is handling the saving during activation...does the class which is doing the activation send full information about the document (that is version information) so that the ReceiveFilter can process it? |
| Comment by Michael Mühlebach [ 04/Nov/15 ] |
|
Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes. |