How to Prepare Your Organization to Take Advantage of Reusable Component Authoring
Q: Does this solution support things like smart art, charts, complex graphics and maintain formatting?
A: Docuvera is designed to ingest images that are created outside of our system. As a result, an author will upload an image that was created with Photoshop or a similar tool or upload an image from a Digital Asset Management system.
We maintain the formatting from uploaded images except if the images are larger than the width of the exported document. In that case, Docuvera will resize the image to the width of the page.
Q: Do you have examples of use of bullet points as introductions and use of tables?
Q: Does this support adaptive content such as MOA videos?
A: Docuvera currently does not support video streaming within a project. The first iteration of video support will focus on supporting a video stream from a third-party site that would be linked to from within a project. Therefore, in this case, the video streaming provider would be responsible for selecting the correct video stream based on device resolution and bandwidth.
Longer term, we may consider hosing videos within our system, but we want to better understand the market need (versus integrating with existing digital asset management systems).
Q: Does this work with Microsoft EndNote?
A: Assuming this question refers to Clarivate Endnote (Endnotes in Microsoft Word are discussed below). Our evaluation of Endnote revealed that it did not support true SaaS capabilities where a company could leverage a common set of references and where additions/modifications to that database would be shared among all of the users. Rather, Endnote supports a personal library model with limited sharing capabilities. Users can share their own specific libraries of references, but any changes to those libraries are not automatically shared with other libraries.
To ensure a robust integration, we would want to make sure that we could consistently keep modifications to the reference databases in sync across Endnote and Docuvera. This was not possible at the time we evaluated Endnote’s product strategy.
We would consider a migration of references from Endnote to Docuvera if a customer would be interested in that option.
Q: Back to endnotes… does it work with combining multiple MS Word EndNotes?
A: Yes, Docuvera supports combining components containing citations into a single project. The following example illustrates how this is supported:
- Reuse component A from parent Project 1 in child Project C. Component A has a reference XYZ in it.
- Reuse component B from parent Project 2 in child Project C. Component B has the same reference XYZ in it.
So, the question is what happens when I export Project C? Is there 1 reference or 2 references?
In this use case, the references would be combined in the references section and only 1 reference would be listed. The citation would be the same in both component A and component B in Project C.
In the project below, this is the output of Project C where the references were combined:
Q: In the approval process, is there a way to have it automatically be approved across all projects or does each author have to approve it for each project?
A: In order to maintain compliance, a user needs to approve projects individually.
Currently, a user would need to approve each project where changes are applied. In the near future, a user will be able to quickly step through an approval process that automatically propagates changes to each project while maintaining compliance.
Q: Can you assign re-approval timelines for projects? Can this be a default with scope to change, or is it always manual?
A: Yes, re-approval timelines can be assigned to projects.
Expiration dates may be automatically defaulted based on the document template. For example, in a US medical letter template, you can configure the expiration to be 1 year from date of approval such that any US medical letter that uses that template will have the expiration set to one year.
Q: Does added/new/changes content get “tracked” like it does when in Word?
A: Content changes that are made within a project are tracked and can be compared from one approved version to the next. For example, changes that are made in version 2 of a project can be compared with version 1. Users can view these changes when reviewing parent content changes (i.e., when I reused a component, I can view the changes in a track changes view so I can decide if I should accept those changes in my child project). In addition, users can view track changes in the review process so reviewers can easily see what content has changed in a reviewed component and quickly decide if those changes are acceptable. Finally, users can also output those changes as a Word document if providing both clean and a track change version of Word documents are valuable for downstream consumption.