Zaphne – Content Automation News for 07-26-2018

PUSH Radio for Distributed Content Automation

Database Continuous Delivery

Continuous Integration, Continuous Delivery and Continuous Deployment are the common principles and practices to structurally handle the process of automation and set ground rules for the many participants in the development, build, test, and release of the software process. Continuous Integration, Delivery & Deployment As a set of principles and practices, Continuous Integration, Continuous Delivery and Continuous Deployment are not a case of ‘one size fits all. Checking in changes in development building the deploy package running unit tests then actually moving the changes to testing and later staging environment running acceptance tests. Continuous Deployment takes the next step of pushing changes automatically to production and runs the concluding set of tests there. Leveraging Continuous Deployment in a SAAS type of application or product makes a lot of sense, as a company can stream and throttle traffic to a new feature, do A/B testing to evaluate new changes, run the old release side by side with the new release and overall measure and manage changes with confident. 

Dealing with database deployments is tricky; unlike other software components such as code or compiled code, a database is not a collection of files. In order to promote database changes, a transition code needs to be developed – scripts to handle database schema structure, database code, and content used by the application. Achieving automation by scripting database objects change-scripts into traditional version control is limited, inflexible, disconnected from the database itself, and may be untrue and prone to miss updates of the target environment because of conflicting changes. With the build and deploy on demand approach, the database delta script to upgrade the database from current version to the next version is generated when needed, ensuring an up-to-date target state is being validated and taken into account. Automation interfaces are a must in order to create a harmonious process, dealing with database changes as part of the whole picture, tightly coupled with the delivery of Java or. 

A better solution needs to be implemented in the shape of Continuous Delivery and DevOps for database. Database Continuous Delivery should follow the proven best practices of change management, enforcing a single change process over the database, and enable dealing with deployment conflicts to eliminate the risk of code overrides, cross updates, and merges of code while plugging into the rest of the release process. 

Keywords: [“change”,”database”,”test”]

Content Management: CAPS

To enhance our investment company clients’ ability to manage the increasingly complex production of their prospectuses, registration statements, and other financial documents, Command developed the Command Automated Publishing System. The two main CAPS modules are SCAPS for annual, semi-annual and quarterly shareholder reports; and PCAPS for prospectus report content management. CAPS is used by more than 2500 funds from leading investment companies. Improved integrity of disclosure so there is a reduced risk of inaccurate, incomplete, or misleading statements in the documents. Reduced time to create a document and documentation related to new product launches. 

The CAPS prospectus and shareholder report modules may be purchased separately or jointly to provide an integrated solution. Documents are created and edited in Microsoft Word and Excel, which combine with an intuitive user interface that is being completely modernized in 2016 and a database driven virtual library. This allows you to manage and repurpose information required in investment company registration statements, prospectuses, summary prospectuses, Key Investor Information Documents, shareholder reports, and other documents. Development and ongoing support of our prospectus and shareholder report modules of CAPS are spearheaded by an experienced ’40 Act attorney and experienced mutual fund administrators, ensuring unparalleled ease of use and a feature-rich complement of capabilities designed from the end-users’ perspective. We continue to develop and release new CAPS functionality based upon our clients’ requests, one per quarter on average, and we develop optional modules to address evolving market needs. 

Some examples are our Summary Prospectus and Reprint Management modules that address the complexities of summary prospectus rules, and automation of the new money market reporting form N-MFP1. CAPS also has the power and flexibility to address the increased complexities in the proposed Investment Company Reporting Modernization rule, including new forms N-PORT and N-CEN. And many of our CAPS clients are taking advantage of our EDGAR Slayer module, an EDGAR conversion tool for CAPS documents that gives clients superior performance and control over EDGAR conversions. In 2016, we will be introducing an entirely new User Interface for CAPS that provides superior navigation and a more efficient user experience. 

Keywords: [“document”,”CAPS”,”report”]

Auto-Classification, Taxonomy Management, Metadata Generation

ConceptClassifier makes SharePoint content more findable, improving productivity and collaboration while underpinning information governance and mitigating risk. Automatic metadata generation and classification of content to term sets eliminates end user tagging and improves business-critical applications, such as search, collaboration, migration, records management, and security. ConceptClassifier for SharePoint Online makes SharePoint Online content more findable, improving productivity and collaboration while underpinning information governance and mitigating risk. Automatic metadata generation and classification of content to term sets eliminate end user tagging and improve business-critical applications, such as secure hybrid search, security, data privacy, migration, and collaboration. Rules can be created to automatically identify any content type, such as a document of record or eDiscovery matter, enabling management of content in place or optionally taking action on the content, like migrating it to a records management platform. 

The result is file share content becomes searchable, content exposure is mitigated, and successful content migration is a reality. ConceptClassifier for OneDrive for Business makes OneDrive for Business content more findable, and protects an organization from the risk of exposure of information loaded onto OneDrive sites. A rule base can be developed to automatically classify content, manage distribution controls, and take action on content identified as containing documents of record, privacy data or any other organizationally-defined, confidential information. ConceptClassifier for Box makes content in Box more findable, protects organizations from the risk of data breaches, and reduces costs associated with file storage. Content is classified as it is uploaded, enabling organizations to manage distribution controls and take action on content identified as containing documents of record, privacy data or any other organizationally-defined confidential information. 

ConceptClassifier for OpenText Content Suite makes content in Content Suite more searchable, improving compliance governance, eDiscovery, and records management. Automatic metadata generation and auto-classification of content to the file plan eliminate end user tagging and improve consistency, which enables effective management of critical content while mitigating risk. 

Keywords: [“content”,”ConceptClassifier”,”risk”]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.