Watson Explorer Text Analysis and SPSS modeller - nlp

I have a project where we are required to go through a repository of letters and decide if the letter "passed" or "failed" a certain business rules. We will using Watson Explorer. For me personally, I believe WEX NLP can be used to extract and understand the content, but I am not sure if we need other tools like SPSS Modeller to then score the letters. Or can WEX do that by itself without further tools?
Thank you in advance.

Looking at your project use case i.e. "to go through a repository of letters and decide if the letter "passed" or "failed" a certain business rules"
Yes, it can be done by making use of Watson Explorer Advanced edition. The Watson Explorer Advanced Edition has 2 major components:
Watson Explorer Engine (Foundation Component) - It is the component responsible for Big Data Ingestion and it also hosts a UI component called Watson AppBuilder.
Watson Content Analytics - WCA (Advanced Component) - It is the component responsible for Text annotation, business rule definition and dictionary declaration, bsically text analytics on data.
So, there shouldn't be any need to use SPSS, given that it is an business rule type use case (which can be built in WCA). And can be integrated with the displayed on AppBuilder UI by making use Custom Converter on WEX Engine (where you ingest the data and add converters to make use of the WCA business rules to be applied on the data).
Also, if you are looking at creating your own UI and Backend using some other technology such as Node JS or JAVA (JSP), then you may want to use the WCA or the WEX API's for the same.
Hope this helps.

Related

What is the Recommended Approach for Hosting Transformations when creating a Custom Module?

In Kentico 11, in a custom module you are developing, when using a custom Page Template (portal mode) for the UI Element, where is the appropriate place to host Transformations used by web parts of that template? "Appropriate" meaning the transformations can be bundled with the module for import/export operations or at least grouped with it logically in Kentico admin?
The Kentico Custom Module app doesn't contain a Transformations tab for its Classes.
Repeater web parts used on the UI page template only list Custom Tables and Page Types when looking for transformations. Transformation doesn't seem to be supported for a Custom Class.
I could create a standalone container Page Type to host all transformations for the module, however this would be outside the module. These transformations would use data from Classes in the module (through repeater web parts and query data sources for example). It seems odd to put them outside so I am suspicious of doing this.
Up until now I've only used the out-of-box tab and listing web parts to create custom modules. Now I need to get into more customization, and prefer the portal mode to easily build templates using web parts. Transformations seem to be the missing consideration in this development flow.
Neither can I find Transformations mentioned in the Custom Module documentation. Kentico Documentation I'm referencing is:
Creating custom modules
Manually creating the interface for custom modules
Martin Hejtmanek's Module development articles like this one
I can find a place to put my transformations. I'm looking for thoughts about where to best put them and bundle them with my custom module work.
Your findings are a shortcoming in the module documentation. The documentation talks in great detail on how to build the module and display it within the Kentico UI but talks little to none on how to display that content outside of Kentico on the public facing website.
What you mentioned, using a custom Page Type as a container is a simple easy approach and I believe you can bundle this with your module. Yes it doesn't make sense but using this approach will allow you to have your custom queries to access the module data and display options (transformations).
You have another option to create custom webparts for this and package them with your module but I'd recommend against this because it takes away from the basic usage of Kentico and will require code maintenance and modifications for simple changes.
If you look at page types you will see that Kentico does the custom page types to hold transformations. They have ones like RSS Transformations, E-Commerce Transformations, etc.
That is the way I have always done it also.
I suggest you to take a look at the custom table module as example, i.e. user interface part of it: there is transformation menu item under edit custom table in the interface. Take a look on how it is done and try to clone/modify it for your own custom module. If you check the DB: cms_transformation table has TransformationClassID field. So transformation is attachable to a class - so you custom classes can have transformations attached. Honestly i've never done it, but this is the way how I would approach. I would keep apples with apples, oranges with oranges... yeah sure you can always create "container page type" and it will work, but i would play around with the custom module. You might need to create and extender in this case.
#John,
As per Brenden post, you can achieve this using custom web part with your custom logic.
Refer below URL:
https://docs.kentico.com/k10/developing-websites/defining-website-content-structure

Dynamic Cognos screen tip and description?

Is it possible to update the screen tips and descriptions of fields in Cognos Analytics 11.0.8 dynamically? We want to have a Data Definition Catalog and use it to update Cognos. The only methods I can find are fairly manual, including BPS Meta Manager.
Look at the steps to integrate InfoSphere Business Glossary into Cognos. I haven't done it, but I've heard people say that the configuration steps can be used for other catalogs, besides the InfoSphere product.
Since the configuration is just a URL, you could point this to a web server you control. Then use the web server logs to identify what Cognos appends to the URL or posts to the URL to identify the field.
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.ug_cra.doc/t_configure_business_glossary.html#Configure_Business_Glossary

Extending NetSuite's default business logic

I am new to NetSuite and am trying to get an understanding of how it works in the area of business rules. So sorry if these are questions with obvious answers.
I understand a user/consultant can extend/customize it to fit with my business needs.
My questions therefore are:
Presumably a default instance of NetSuite contains various business
rules that will fit some business needs. As a user/consultant can
you view this default business logic?
Can a consultant change the core business logic? Or is it more a case of adding code before and after the default logic fires?
Is the default business logic/rules written in SuiteScript, or is SuiteScript only used by 3rd parties when extending/overriding the default logic?
Thanks
We cannot view the code that governs the default NetSuite logic and business rules, but the NetSuite Help documentation has a ton of information about how vanilla NetSuite works. All users can view and study the Help files to become more familiar with NetSuite and its default processes.
We cannot change the default code, but we can absolutely add code before and after many different events.
The default business logic is written in SuiteScript, but again, we cannot view that code. Third parties utilize SuiteScript to extend the default NetSuite functionality.
SuiteScript is not the only option for customizing NetSuite. There is also SuiteFlow, which provides users with the capability of graphically building workflows to define business rules based on user actions. No code is required (though under the covers, workflows essentially build hidden SuiteScript). There are several things that can only be accomplished in workflows and not in SuiteScript, and vice versa.
Netsuite's ERP, CRM, eCommerce modules have predefined standard rules which are acccording to industry standard. But customers have sometimes different business needs. For that we can customize Netsuite. There are various customization tools available in Netsuite. It supports to extend standard functionality as well as implement our custom logic. It provides suite scripts,a java script based API which can be used in almost every where in Netsuite for customization. Along with that it provides UI based customization in the form of SuiteBuilder. We can fire script before any standard business logic, after standard business logic run. We can add client side validations, schedule our application to trigger at specific time and many more. The standard business logic is written by Netsuite, we cant alter them, we cant see the code. It is the way it works. If you are new to Netsuite, it is suggested to read netsuite help guide. There is no online help other than Netsuite available. So you must go through them. If you have other query, feel free to ask.

Using SSRS instead of Crystal reports to generate admin forms

I'm looking into upgrading a .net 2.0 app. The app is used by the public authorities of a certain city to keep track of expenses and generate reports and forms.
The reports and forms were generated in VS2005 using Crystal report. They follow a well defined layout, like official documents usually do.
I am looking at options to upgrade the application and the main problem I have is in determining how to deal with the crystal report files.
I have successfully upgraded to VS2008, but any version after that doesn't have CR anymore, so my company would have to pruchase CR separately and because the client and my company are both tight, I'm looking at alternatives...
The obvious one is using SSRS. I have never touched it before in my life, but after playing around with it for a bit, I get the impression that it is not very well suited to generating forms with lots of non-tabular content and lots of formatting. Or am I wrong?
It seems that every line has to be drawn separately. There is no (that I can see) accurate way of positioning lines for formatting...
But I'm just a beginner, so I might be getting this all wrong?
If that is the case, are there any other alternatives to CR and SSRS?
I was thinking of maybe having a separate MVC web site project in the solution. Have that generate the layout in html and css with data from my entity model, then view the result in a (built-in or not) web browser. Am I overcomplicating on this?
I really need advice from somebody who's done that kind of thing before.
What SSRS is good for:
Talking to SQL Server, much faster than other products as it in many cases retains the database better when in other programs IMHO they repeat query at times.
Designing collapsable grids and chart objects from datasets. You can have 'groups' that can nest aggregates of collapsed values and can be un collapsed or collapsed on demand based on expressions, parameters, or a recusive parent set.
A web service for deployment ease where you can deploy one or many objects. You can also write add ons for this service with C# and the ReportingService.asmx web service.
You can talk to the web service directly in a 'form' object in HTML and manipulate it's output.
You can schedule reports to send out via email and file saves automatically to clients or internal users.
What SSRS IS NOT GOOD FOR:
It is not event driven hardly at all except for parameters. You cannot click on many things and get other parts on the form itself to update. You may do an 'action' that goes to another location, report, or site. But in essence you are calling a seperate object, not the same instance again.
Multiple layers of reporting. Beyond tweaking tool tips you cannot do 'hover over' reporting without hacking SSRS. You can make javascript windows show other reports but it is not baked in to SSRS. So you are either clicking into new reports or tab stops in a report but not getting hover over quick objects beyond text and expressions that are in tool tips.
What do you want before considering what you need to impement?
I want to input and export things while talking to my database - ASP.NET with potentially HTML 5 or MVC4 if you want to be very new. ASP.NET is made for actively talking to a server and taking commands IN as well as OUT.
I want a form to auto update periodically on a page as a landing site and dashboard - AJAX and Javascript on top of HTML, Java or ASP.NET.
I want to create reports that exist on a Server and can be hosted on a wide variety of platforms in .NET via web service calls - SSRS.
SSRS's biggest selling point to me is it's reusability once you dial a report in. They are pretty easy to create, easy to configure, easy to deploy, and if you get a little advanced in calling the webservice you can get SSRS report objects in other technologies if you want.
There is Crystal reports for VS2010 and VS2012. It is just not shipped with them. You can download the installation from here: http://scn.sap.com/docs/DOC-7824
I am running through the same decision process at this time. There is a .NET product from a company called "Windward" that will allow you to design your reports in Microsoft Office. If you are in the MS ecosystem already or want your users to design reports instead of always calling on you, this might help.
Their template design tool is called AutoTag and you can deploy these template to their .NET based engine in a few lines of code.
I know the question is regarding SSRS vs. Crystal comparison but thought you should know there are other alternatives and some can make life easier
Ryan

Sharepoint Web Part Management

I have a rather large project developed on Sharepoint and Project Server, designed as a multi-tier application. I programmatically manage web parts on certain web part pages. According to the choices of the user in one of the web pages, appropriate web parts are added to the web part collection of another web part page. My problem is that I simply do no know where to manage the web parts, should I do it in the BLL and then have the assembly containing the business logic reference the UI assembly where the web parts are? (I need to instantiate the web parts when adding them to the collection, since I do not want to use hard coded strings representing the web part dwp.)
It really depends on what pattern you're using for your BLL and UI layers, and how strictly you want to follow it.
If you're doing a MVP pattern then I'd suggest that you have the Page implementing an interface which has one (or more) of the following options:
A stack which the Presenters to load are added to
A Load_WebPartName event for each web part which then should be called to indicate which webpart(s) need loading
To be strictly MVP you should not reference the following assemblies in your BLL project:
System.Web
Microsoft.SharePoint
Microsoft.SharePoint.*
(All SharePoint assemblies would be in either the Model or UI projects, the BLL is just connecting to the appropriate hocks)
Can you package the web parts as a feature or set of features and then simply manage the feature(s) activation/deactivation through the web part manager class?
Any programmatic massaging of the web part that needs to happen on the appropriate web part page can be handled in the feature receiver, so your manager doesn't need to be so aware of the web part UI.
HTH,
jt
Web parts are generally best managed using the feature/solution framework. You may treat the webpart classes you write as any other web control, and thus a part of the ui layer. I generally keep the information in the xml files (the .webpart or .aspx files) to a minimum. If you are managing them exclusively, you don't really need to use declarative code files at all.
The short answer: webparts are sharepoint specific ui, and should have no knowledge of the business layer.
The short answer is probably "no, you should not do this in the BLL." A purist might argue that while the BLL may rightfully determine what a user can or can't do, it is up to the UI tier to determine the appropriate web parts to be displayed as a result.
For example, the BLL might determine a user's capabilities and expose them as roles, or permissions or something else with domain-related meaning (e.g. timesheet approver role, approve timesheet permission, etc.). These might then be mapped to a set of web parts by the UI tier (e.g. timesheet approval web part). In this way, the BLL effectively determines the users capabilities and the UI tier determines the UI for those capabilities.

Resources