How to add/edit already completed human annotations IBM Watson Knowledge Studio ?
Once the human annotations are completed, there is no option to import the annotated sets or to edit them.
Is there any way we can do it ?
Once accepted the document cannot be edited, however once marked as complete as an individual task before submitting to the model the status can be changed and documents edited.
Presently,There is no way to edit the annotated documents after submitting them.You can edit them only before submitting.
Related
The v2.1 preview of Azure Form Recognizer Labeling tool which is recently published has a feature to compose models, When do we need to use is? Can anyone explain me some usecase for that?
Currently it's recommended to build one model for each form type in custom form. Model compose allows you to compose up to 100 models, hence one analyze call can process many type of forms - form type classification will be done automatically for you.
Has anyone ever tried to use the model that has been generated by the Watson Knowledge studio outside of the Alchemy language API?
Or do I always need to upload the model to knowledge studio and from then on talk to the api?
Though I have always used my Knowledge Studio based models on Natural Language Understanding, I believe it's possible to deploy these models to Discovery and Watson Explorer as well for text extraction.
Check this documentation for details on how to deploy the model to different components.
I'd like to find out exact APEX language specification (with all that grammars, etc.) but I've spent half a day and ended with almost nothing.
I know that APEX is Java-based language, but compiling it's spec on my own from Java spec and exclusively APEX things will be a pain.
Is there any place where I can get APEX language specification?
For those not familiar with them - I'm looking for a such document http://docs.oracle.com/javase/specs/jls/se7/html/index.html for it.
Thanks in advance!
My understanding is that Salesforce haven't currently published such a document. Instead they want you to use the Tooling API to get the tokens etc...
See Grammar for creating an Apex parser
Depending on your scenario you might find the Apex Language Server a useful tool. It does the Apex parsing etc... behind the scenes for the current VSCode tooling.
Incidentally, the Salesforce StackExchange site linked above is a great place to ask Salesforce specific questions.
Actually, Salesforce does publish a detailed Apex developer guide.
The current 2017 document can be found here :
https://resources.docs.salesforce.com/208/latest/en-us/sfdc/pdf/salesforce_apex_language_reference.pdf
This document and it's location could be updated frequently, so you can also Google 'Apex Developer Guide' to get here :
https://developer.salesforce.com/docs/atlas.en-us.apexcode.meta/apexcode/apex_dev_guide.htm
Once here, click the PDF button to generate/view the latest PDF, or use the available content options to view online.
I posted a question on the Drupal forum about whether I should build my database in Drupal using content-types or the database abstraction layer and schema module: [here][1]
Any advice would be greatly appreciated.
[1]: https://drupal.stackexchange.com/questions/98020/should-i-use-content-types-or-database-abstraction-layer
I'd recommend using content types.
For a PHP coder, sometimes using the Drupal User Interface to build things feels non-intuitive, but in the long run you're going to benefit a lot from doing things "the drupal way.
Once you reverse engineer your need into a content type and all it's associated fields, install the modules that provide those field types and set things up, you'll start to see the benefits.
Validation on all the data-entry froms will already be done for you.
Multiple display modes are available for your data (email addresses can be shown with or without mailto: links, images can be shown using any of Drupal's image styles)
Integration with other Drupal modules already exists, and will be supported (almost anything built with fields is available to views)
By writing your own schema you'll need to handle all these things yourself (and more), and not just once, but you'll need to maintain all that custom code over time.
Learn to leverage the community and all the great work that's been done already, you'll save yourself time in the long run :)
What i see you are going to have shop site.
You may tray this:
https://drupal.org/project/commerce_kickstart
, i've found it usefull once. It's drupal distribution with nice themed shop rady to use straight forward.
And of course do it with content type + views + entity reference modules.
Here is a link to a comment that answers the question I asked. It backs up what arpitr outlined in their answer on the orignal post on the drupal forum, whose answer is also in agreement with jenlampton's suggestion above.
https://drupal.org/comment/7848011#comment-7848011
I will implement my system using node entities until the need arises to build a custom entity (if it ever does).
The top answer in this forum give a good way to evaluate whether to use nodes or custom build an entity:
https://drupal.stackexchange.com/questions/22586/when-is-it-appropriate-to-create-an-entity-versus-just-adding-a-new-content-type
Currently publishing articles in a custom VF page using the Knowledge Management Publishing Service Class, and publishing/archiving articles into the future. But I can't seem to find a way to display this future date to the user. It isn't stored it seems in any fields on the the article itself or in any apex jobs.
Does anyone know how SF displays this field on their own page? And if they allow access to this date somehow via apex?
If I understand your question correctly, the information you're looking for can be found in KnowledgeArticleVersion, probably under FirstPublishedDate. So you'll want to query for the latest row in KnowledgeArticleVersion for the article in question and then pull its FirstPublishedDate to get the date you're looking for.