Hello Holger,
I am looking into BatchActions and only seemed to find a snippet in the
documentation where it says it is the similar to
dash:ModifyActions/dash:ExploreActions
(https://archive.topquadrant.com/doc/7.8/scripting/actions.html?highlight=batchaction).
I have a dash:ModifyActions ins
Hi Marie,
BatchActions are not linked to specific classes. Instead they are invoked on a
list of nodes as values of the variable focusNodes, and are called from the
batch actions drop down buttons that are found in various places. For example,
you can run them from the Asset List panel, the Ins
Thank you for the feedback. I found them in the Asset List panel. So if it
is not associated with a specific class, how would you go about making sure
you can't batch add the action to other classes by accident. So for
instance, I only want it to add to Concept. I tried this, but it isn't
worki
The jsCondition needs to return a boolean but the forEach doesn't return
anything. Maybe you mean
focusNodes.every(node => node.instanceOf(ex.Concept))
Holger
> On 19 Mar 2024, at 4:41 pm, Marie Valadez wrote:
>
> Thank you for the feedback. I found them in the Asset List panel. So i
Hi Marie,
thanks for those details. I believe I was able to reproduce the same scenario.
It happens when the sh:class of a parameter points at a class that isn't
covered by the ADS code generation. I have just made this code more resilient
for 8.0 but in the meantime I think the following work-
Hi Holger,
Thank you for the advice. I was able to use that workaround to get it to
add the blank node with the class dropdowns for the parameters in the
Ontology. It did take some time for it to register and recognize it.
I am now stuck on the dash:jsCondition. I am using your example from a
> On 22 Mar 2024, at 8:14 PM, Marie Valadez wrote:
>
> Hi Holger,
>
> Thank you for the advice. I was able to use that workaround to get it to add
> the blank node with the class dropdowns for the parameters in the Ontology.
> It did take some time for it to register and recognize it.
>
>
Thanks Holger! That worked for my use case. Appreciate the help.
Is there a way to use sh:class to only populate instances of the root class
instead of also populating ones that are a subclass? So for instance, if I
want to only retrieve instances of Concept but not instances of the
subClass sa
> On 25 Mar 2024, at 5:23 PM, Marie Valadez wrote:
>
> Thanks Holger! That worked for my use case. Appreciate the help.
> Is there a way to use sh:class to only populate instances of the root class
> instead of also populating ones that are a subclass? So for instance, if I
> want to only re
I tried the provided example but it still populates the subClasses even
after adding in the sh:node for the parameter. Any other thoughts on what I
need to add to prevent the subClasses from populating in the widget?
ex:Concept-map
a sh:Parameter ;
sh:path ex:conceptMap ;
sh:class ex:Conce
> On 26 Mar 2024, at 2:06 PM, Marie Valadez wrote:
>
> I tried the provided example but it still populates the subClasses even after
> adding in the sh:node for the parameter. Any other thoughts on what I need to
> add to prevent the subClasses from populating in the widget?
>
> ex:Concept-m
That provides me with no options in the drop down because there are no
direct instances of skos:Concept in my data graph. The one I am looking for
is ex:Concept.
On Tuesday, March 26, 2024 at 8:08:04 AM UTC-6 Holger Knublauch wrote:
>
> On 26 Mar 2024, at 2:06 PM, Marie Valadez wrote:
>
> I tr
Then I don't see what's wrong. I would need to get a minimal example that I can
run myself to reproduce this. Feel free to send me a file off-list.
Holger
> On 26 Mar 2024, at 2:49 PM, Marie Valadez wrote:
>
> That provides me with no options in the drop down because there are no direct
> in
Thanks for your patience and the sample file that you have sent me off-list,
Marie.
And I (publicly) admit that I made a mistake in my testing here. I was testing
the sh:node solution using the Form Panel, but the Parameters dialog does not
follow the exact same logic, even though it shares the
Thank you for submitting a development ticket. Hopefully, this can be
updated in the future.
On Tuesday, March 26, 2024 at 11:50:42 AM UTC-6 Holger Knublauch wrote:
> Thanks for your patience and the sample file that you have sent me
> off-list, Marie.
>
> And I (publicly) admit that I made a
BTW this is now addressed for the upcoming 8.0 release.
Holger
> On 26 Mar 2024, at 7:13 PM, Marie Valadez wrote:
>
> Thank you for submitting a development ticket. Hopefully, this can be updated
> in the future.
>
> On Tuesday, March 26, 2024 at 11:50:42 AM UTC-6 Holger Knublauch wrote:
>>
Thank you Holger! Appreciate the help!
On Wednesday, March 27, 2024 at 4:24:51 AM UTC-6 Holger Knublauch wrote:
> BTW this is now addressed for the upcoming 8.0 release.
>
> Holger
>
>
> On 26 Mar 2024, at 7:13 PM, Marie Valadez wrote:
>
> Thank you for submitting a development ticket. Hopefully
17 matches
Mail list logo
